Labview on windows c 6.00

i am working on Labview 2014. i need to confirm that does the exe created in labview2014, RUN properly on windows based HMI.??
if yes then is there any specific tool kit required for that??? in that exe i am going to work on serial data transfer.
currently its working on Windows XP/7 properly.

**bleep**design wrote:
i am working on Labview 2014. i need to confirm that does the exe created in labview2014, RUN properly on windows based HMI.??
if yes then is there any specific tool kit required for that??? in that exe i am going to work on serial data transfer.
currently its working on Windows XP/7 properly.
One caveat though. When you say Windwos HMI do you mean a Windows x86/64 based machine (aka Windows 7, 8, 8.1) or any Windows platform such as Windows Phone and Windows RT?
For standard PCs it will indeed run on Windows machines, if the executable was also created with LabVIEW for Windows. On those other platforms it will definitely not run since they are Windows by name but completely different beasts in reality.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Similar Messages

LabVIEW on Windows XP Embedded

Hello ng,
has anyone experience using LabVIEW on Windows XP Embedded? Does it
work, are there limitations, ...
Thanks in advance,
Marko

Hi Marko,
Please visit the following link for answer to your question.
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=506500000008000000ECC60000&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0
Please feel free to respond with your comments should you have more questions.
Regards,
Ankita A.
National Instruments

LabVIEW: Null window error in an application?

Hi there,
I just built an application from a vi and I am encountering an error:
LabVIEW: Null window.
The top-level VI "name1.vi"
was stopped at unknown on the block diagram of "name2.vi".
The application runs smoothly until the user selects some hotkeys to open a simple subvi briefly during execution in order to check on a file path. This hot key combination works perfectly when the normal vi is running and the subvi displays the information and then closes and the vi execution continues. Why would it not work when it has been built as an application??
Thank-you for any help you can provide!
Solved!
Go to Solution.

Solved my own problem - should have dug a bit deeper before posting - sorry!
http://digital.ni.com/public.nsf/allkb/D95BDEB7A7E211AE86256EDA005517F4?OpenDocument

Can you run labview on Windows Tablet PC Edition?

Can you run labview on Windows Tablet PC Edition?...or does LabVIEW executable and Run-time engine operate with this OS?

LabVIEW 7.x will run without any problems on a Windows Tablet PC with SP1. There have been documented issues with Windows XP SP2 and LabVIEW subsequently not exiting properly--LabVIEW's window closes but somehow it is still present in the task manager.
Hope this helps.

Compatibilité Labview 2009 Windows / Labview 8.5 Linux

Bonjour à tous
J'ai une petite question à laquelle je suis certain bon nombre d'entre vous avez une réponse
J'utilise deux PC avec Labview 2009 WIndows sur chacun qui communique avec la fonction UDP.
Seulement voilà, la trame qui va d'un PC à un autres, je souhaiterais la faire passer par une passerelle, un troisième PC, toujours en UDP mais lui équipé de Labview 8.5 sous Linux.
Le truc c'est que cela fonctionne pendant une minute ou deux et après la communication s'arrête au niveau du PC Linux Labview 8.5
J'aimerais donc savoir si la communication UDP entre Labview 8.5 Linux et Labview 2009 Windows est bien possible
Je vous remercie énormément pour vos réponses....
A très bientôt.
Vincent

Bonjour,
Si vous voulez vérifier la compatibilité entre Linux et Windows, le mieux serait d'utiliser les exemples LabVIEW. Ces exemples se trouvent dans Aide>Recherche d'exemples...>Réseau>TCP & UDP. Vous pourrez ouvrir "Client de données simple" (ou "Simple Data Client") sur votre LabVIEW Linux et "Serveur de données simple" (ou "Simple Data Server") sur votre LabVIEW Windows.
Après l'avoir configuré selon votre configuration, exécutez en premier le Serveur de données simple sur Windows puis le Client de données simple sur Linux.
D'après l'aide de la fonction UDP Open de LabVIEW 2011 une mention a été ajoutée par rapport à l'aide des version 8.5 et 2009. Il semblerait qu'il y ait un comportement particulier aux version non Windows de LabVIEW lorsque vous cablez l'entrée "net address". Dans le cas où les exemples ne fonctionneraient pas, je vous conseil d'essayer en supprimant cette entrée et de ne vous baser que sur le port de communication.
Cordialement,
Mathieu P. | Certified LabVIEW Associate Developer
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Journées techniques : des fondamentaux aux dernières technologies pour la mesure et le contrôle/comm...

Are there any issues regarding running Labview on Windows Vista

I am a cognitive psychology graduate student, and I am considering switching to LabView to display stimuli and gather RT data. I have previously used E-Prime for this task, but E-Prime doesn't seem to run well with Windows Vista. Are there any known issues regarding running LabView with Windows Vista?
Thanks
Chris

I've had no problems on Vista*. Only issue I've had was concerning how Vista uses fonts, but if you start on Vista and don't switch between XP and Vista, etc., then you'll be OK.
*no problems with LabVIEW's compatibility with Vista. Now, Vista in general, that's another story and not for this thread/forum.
Richard

LabVIEW application window

I heard some time ago that there is a way to eliminate/hide the LabVIEW Application Window in the development environment, does anyone know how to do that?? It's causing me serious problems with my TestStand modal dialogs...
This is the one...
Thanx...
Attachments:
lvwindow.PNG ‏47 KB

Were you not able to get the modal dialog working using the method that we spoke of on this thread: http://forums.ni.com/ni/board/message?board.id=330&message.id=14315&view=by_date_ascending&page=3
If not, did you try the example that ships with TestStand for using modal dialogs? As I said on the post, I was able to successfully call your VI as a modal VI from TestStand. Please follow those suggestions and let us know if you are not able to get that working.
Thanks,
Andy McRorie
NI R&D

Labview: Null Window ... stopped at unknown on the block diagram

Hi,
I have a fairly large program that was written in Labview 6.0. Recently we upgraded to Labview 9.0 and this program was exported to an executable with the new version.
When running the executable I sometimes get the following error as seemingly random places. I have not been able to make it crash when not using the executable. Labview: Null Window. The top-level VI ".vi" stopped at unknown on the block diagram of ".vi"
I apologise for having to blank out the vi names but i cannot give vi names, say what the software is used for or give over code. I can say that it uses NI USB 6212 IO cards, interfaces with Rhode and Swartz instruments and uses alot of file IO.
I was hoping that someone could give me a hint on how to debug such an error. I have noticed that When this error occurs, the memory use almost doubles.
Thankyou
James
Solved!
Go to Solution.

I think you open the front panel of a VI that has it's front panel removed during the build. Try to adjust the built settings of that specific VI to include the front panel.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

How to call a Linux exe from LabVIEW for Windows

Hello,
I need to call a non-LabVIEW Linux executable using LabVIEW for Windows. Any suggestions, aside from buying LabVIEW for Linux?
Thank you,
Chris White

Okay, I'll throw out a few ideas and I'll let you pick which one you may think is easiest.
1. Use the internet toolkit ($$$) or build a simple telnet client yourself in LabVIEW (use the TCP VIs in labview). This would allow you to connect to the telnet port of your linux box, login, password, and execute a command. (You'll probably want to use nohup, do a man on nohup to find out more).
2. Install SSH daemon on your linux box, and an ssh client on your windows machine. You can't get SSH for windows from cygwin. This would be more secure, and you wouldn't need to use the TCP VIs, you could simply use the "system exec" vi to call SSH.
3. On your linux box, install your app in inetd. Then, whenever someone connected to a certai
n port # on the linux box, it would execute your command. A little dangerous because someone might try to connect 50 million times (or a port scan) and kill your box. You also wouldn't be able to send a dynamic command line argument.
4. Write a small TCP application on your linux box to wait for connections (listen for command line options) and execute your command.
You'll probably find one of these options ideal depending on your administration and programming background.

Problems with Labview and Windows XP with error -2147217865

Hello. Im a new beginner in Labview and am having a problem with a error message
I dont understand. Im running Labview on a pc-logger with windows XP.
The program is written by a guy on my university, and logs voltage from
a solar cell panel. He doesnt have the time to check in to it, so Im supposed to
find out what's wrong.
The error message is as follows :
Error -2147217865 occured at Cmd Execute.vi->DB Tools Insert
Data.vi->Solcelle.vi
Possible reasons :
Exception occured in Microsoft OLE DB Provider for ODBC Drivers,
[MySQL][ODBC 3.51 Driver][mysqld-3.23.38-log]Can't open file :
'solcelledata.MYD'. (errno: 145). in Rec Create - Command.vi-
>Cmd Execute.vi->DB Tools Insert Data.vi->Solcelle.vi
I really hope someone can tell me what's wrong and specifically what to do
with it, or possibly guide me to someone who could suggest a solution to this
problem.
Reguards
chrisdee

Hi Chrisdee,
(.. not to discount what TimoS has suggested, however...)
Embedded in the error information you provided:
... Can't open file : 'solcelledata.MYD'.
Sounds like the program needs this file? Has the program been moved to a new location?
just a wild guess!
Cheers
Message Edited by Dynamik on 10-06-2005 04:53 AM
When they give imbeciles handicap-parking, I won't have so far to walk!

Install LabVIEW on Windows 7 X64

I'm trying to install LabVIEW from NI Developer Suite Third Quarter 2009 on Windows 7 X64 machine. The install program terminates with an unexpected error. I can install LabWindows/CVI from the same DVDs onto this machine.
Solved!
Go to Solution.

I'm adding my own experience in installing LabVIEW 2009 onto Windows 7 (64 bit) in case it helps anyone else, but in fact there's no magic bullet for the problems I had, I did it the hard way.
I saw no error messages at all, just that when the installer wanted DVD no.2, the DVD drive seemed to disappear. Cursor remained as Windows 7 "timer donut", could do very little with PC except "master reset".
I tried:
A different DVD drive
Upgrading to Windows 7 sp1
Compatibility mode for Vista (as suggested above)
In the end I just copied the contents of the 3 install DVDs onto my hard disk. I named the directories as the DVD labels, and was impressed that the installer found all the parts automatically. Until it got to the Device Drivers DVD, which I had forgotten to copy, but mercifully at that stage I could browse to the DVD drive. No special compatibility settings used, but I did run setup.exe "as administrator".
I'll put this down as a Windows 7 bug (and maybe specific to my hardware ?) rather than an NI problem.
Along the way, as part of the sp1 upgrade, I got MS IE9, another great way to drop one's productivity (certainly made posting to this forum impossible, this done on a different machine).

How do I Install LabVIEW on Windows 8 without destroying my Start screen?

I recently upgrdaded my computer and am running Windows 8 now. I know lots of people will tell me that this was a terrible idea, but it is what it is. I am actually liking the new start screen once I spent some time getting used to it. It works well once you customize it to your needs. Anyway, the problem that I am having, is that when you install NI software (LabVIEW, TestStand, Toolkits, and drivers), about 100 things are added to your start screen. See "Screenshot 1.png" to see what I am talking about.
My immediate fix was to edit the start menu folder and put everything that I don't need in folder in "My Documents" - called "National Instruments Shortcuts". Then I just put a shortcut to this folder in my start menu directory. This gives me the result shown in "Screenshot 2.png". But my worry is that when NI sends you an update every 6 months and you install, it is going to put everything back.
I am guessing that I am at the mercy of NI to become more Windows 8 friendly. But maybe somebody here has a better idea?
Attachments:
Screenshot 1.png ‏160 KB
Screenshot 2.png ‏70 KB

ScottTron wrote:
If a LabVIEW bug is exposed to my customers, I can't just blame it on NI - I have to implement some sort of workaround to hide the bug from my customers so that they don't know its there.
For me that depends on many factors, like the severity of the issue and the relationship with the customer. Plenty of times I do inform the customer of a LabVIEW bug. If DAQmx craps out after running for a long time (and NI agrees) I'll do what I can to avoid it, but having a customer think it is my fault when it isn't, is no solution.
Back to the original post I'd highly recommend what others probably already have and that's Classic Shell. I combine this with DisplayFusion and my Windows 8.1 box works just like Windows 7. I've only ever seen the new start once, and that was right after the install, right before installing those two tools.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Dual-boot LabVIEW RT/Windows 2000 on PXI

Is it possible to configure a PXI-based embedded PC (NI 8176) to run both LabVIEW RT and Windows 2000 in a dual-boot setup? I would like to use the same PXI system to do both real-time system prototyping as well as finished product testing - though not at the same time, of course.

Hi André,
Just to clarify, all dual-boot systems use the same hard drive for both operating systems. The floppy drive is used only for configuration. If you do not have a floppy drive, you can use a USB CD-ROM drive to load the recovery CD that ships with the controller. Please note that using the recovery CD may result in the loss of data from the previous Windows-only configuration. All of the important files should be backed-up prior to any recovery. For a better idea of what specific steps are involved, you can check out the following link:
http://digital.ni.com/public.nsf/websearch/227CF36870DB7BDB86256F790057F20F?OpenDocument
In particular, the section at the bottom goes through the process of converting to a dual-boot controller.
David H.
Applications Engineer
National Instruments
David H.
Systems Engineer
National Instruments

Error 1935 when installing LabVIEW on Windows 7

Hello, everyone.
I'm new to Windows 7 and I need to install LabVIEW 8.5.1 and 2010.
The problem is that the installation process (for both versions) gives me a lot of errors related to Microsoft Visual C (code 1935), like the popups attached.
What could be happening?
Kind regards,
Daniel R.
Attachments:
Clipboard01.png ‏11 KB
Clipboard04.png ‏11 KB
Clipboard03.png ‏9 KB

Hi Daniel,
LabVIEW 8.5.1 is not supported on windows 7. To LabVIEW 2010 you have turn off, during installation, firewall, antivirus and spyware blockers.
http://digital.ni.com/public.nsf/allkb/98DFF2B564902B9886256FB1004E448F?OpenDocument
Regards,
Abel
NI Brazil
Abel Souza
Engenheiro de Aplicações
National Instruments Brasil

Compatibility of windows xp with labview and windows 2000 with labview

I have a very weird situation that I am not sure even I can decribe it clearly. The thing is we have two set of equipments. One: windows 2000 with DAQ card, PCI card, the other is windows xp with same DAQ card and PCI card. All the labview software are the same version. All the program are the same. But the program on windows xp has a really weird problem. Sometimes, the signal is wiped out when I run the program and sometimes it doesn't. I am curious whether the two windows system have different order sequency. Is it clear? I am really sorry about the description since the problem is really strange. Thank you very much!

With more research, I think I probably find the problem but I don't know how to fix it. Here is how the program work. In Calibrate LC.vi, there are four buttons of "set". When you hit set button, the program will aquire 10 data points which will form the signal we need. But the problem is when I hit set button, no signal at all.So I am thinking the program didn't aquire any data in. I uploaded the Calibrate LC vi and also the Aquire Data vi. Does anyone can give a suggestion how on to fix the problem? Also, I double checked the PCI card. The interrupt request for PCI 6036E in windows2000 computer is 19, that in windows xp computer is 21. Will this be a problem too? Thanks!
Attachments:
Acquire LC Calibration Data.vi ‏34 KB
Calibrate LC.vi ‏108 KB

Labview on windows c 6.00

Similar Messages

Maybe you are looking for