Running A LabVIEW executable in Windows 7

Can I run a Labview executable created with Labview 8.6(32-bit) in windows 7 or Vista. If this can be done then how to do it? I've tried copy the lvrt.dll(run-time engine) into the system 32 folder, but it doesn't solved my problem. For info, My Labview exe file also consist the fuzzy logic toolkit.
Hope someone will help me. Thanks.
Lojius.
Solved!
Go to Solution.

hi lojius,
For that you need to install labview 8.6 run time engine which is freely downloadable....Please find it at the link
http://joule.ni.com/nidu/cds/view/p/id/1101/lang/en
thanks and regards,
srikrishnaNF
Message Edited by srikrishnaNF on 03-23-2010 05:46 AM

Similar Messages

Running 2012 LabVIEW executable on Windows 7

I have a LabVIEW executable that I created under LabVIEW 2012, using Runtime Environment 2012 f3. All the software was created, and runs on Windows XP, 32-bit. The LabVIEW executable works without a problem on this system.
Now when I take that executable and run it on a laptop that has Windows 7 64-bit, and the LabVEIW RTE 2009, I get:
The version of this file is not compatible with the version of Windows you’re running. Check your computer’s system information to see whether you need an x86 (32-bit) or x64(64-bit) version of the program, and then contact the software publisher.
Any ideas? Thanks.

Create an installer for your EXE. By default the RTE is part of the installer. Run the installer on the computer you want to run your program.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

LabView executable on Windows Embedded Standard 7

I will like to know if LabView executable with IMAQdx Vision code can be run on Windows Embedded Standard 7. Thanks.

Greetings,
Most certainly, you should be able to use LabVIEW Executables on Windows Embedded Standard 7 that contain Vision VIs. The cRIO 9082 is a great example, for it uses WES7 and brings in GigE Camera support.
Cordially;
Simon P.
National Instruments
Applications Engineer

How can I run a labview executable file inside a VI

How can i add and run a labview executable file inside the vi and grab the output of the executable file to be used in the vi?
mytestautomation.com
...unleashed the power, explore and share ideas on power supply testing
nissanskyline.org
...your alternative nissan skyline information site

Hi cmdrb,
to run an executable you use SystemExec function.
To get the output of your (LabVIEW-made) executable you need to program some data transfer means: you may use network functions or file functions. In both cases your "LabVIEW executable" needs to provide that options…
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Is it possible to run a Labview executable on a Windows 8 Phone?

If I create an executable from Labview,will it be possible to run it on a Windows 8 phone?
Solved!
Go to Solution.

No, as Mike already said.
The reason being that a LabVIEW executable contains binary code that is compiled for the x86 CPU architecture and accesses the Win32 API. Windows Phone typically runs on ARM or RISC CPUs and did only provide a very limited Win32 subset in the past. With the new Windows RT technology it actually moved even further away from Win32 compatibility as it's entire architecture is based on the .Net technology.
So even if you happen to get an Intel Atom based Windows Phone device which would be x86 compatible it couldn't work, since a LabVIEW executable is a Win32 portable executable format not a .Net bytecode image.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

How do I run a labview executable from C++

I have an application written in C++ that runs some VIs in the Labview Development Environment. I'm using Labview 6.02 and VisualC++ and the runtime engine is installed. What I want to do is not use the LDE and just call the LV executable from C++. I found some documentation but what I tried is not working for me. What I am looking for is a good example of C++ code that runs a LV executable.
The help would be appreciated.

> I have an application written in C++ that runs some VIs in the Labview
> Development Environment. I'm using Labview 6.02 and VisualC++ and the
> runtime engine is installed. What I want to do is not use the LDE and
> just call the LV executable from C++. I found some documentation but
> what I tried is not working for me. What I am looking for is a good
> example of C++ code that runs a LV executable.
> The help would be appreciated.
>
One possibility is to think of the LV executable the same as an
executable built with any other development tool. Invoke it using the
command function that launches via the command line or a fork command.
Another possibility is to make a DLL instead of an EXE.
Finally, you have the option of using the VI Server through a
ctiveX.
This will work better if you have only one of the executables or the LV
editing environment on a particular PC.
Greg McKaskle

Is it possible to run my Labview software in Windows 7

Hi there,
I currently use Labview 8.2.1 and Labview DSC 8.2.1.
But within a short time I want to switch from Windows XP to Windows 7.
My question now is:
Is it possible to switch to Windows 7 without any problems?
Will the Labview software still run under Windows 7 without problems, or do I have to download new drivers or other software?
I hope to get a reaction soon.
Greets
Message Edited by Cheese11 on 03-22-2010 02:37 AM

Hi Cheese,
Official LabVIEW support/compatibility with Windows 7 is explained under the following articles.
National Instruments Product Compatibility for Microsoft Windows 7
Windows Version Compatibility with LabVIEW
LabVIEW Module and Toolkit Compatibility Information
On the forums, people seemed to have mixed reviews about older versions of LabVIEW with newer versions of Windows 7. Another piece of food for thought is Windows 7 (some versions) contain a "Windows XP Mode", which MAY allow you to run this version of LabVIEW in 7 however as the above articles show this is not the supported version. Essentially the XP mode allows virtualisation of XP OS on Windows 7. I've not personally tried it with this version of LabVIEW, but it's just an idea!
Windows Virtual PC
Upgrading to the latest version of LabVIEW will work and is fully supported.
Hope this may help
Ashish Naik
Field Sales Engineer
National Instruments UK

Files directory for a Labview executable in Windows 7

I'd like to hear some opinions on this and ask what other people do. Most of my programs save data files that need to be accessible to the user, and some of them read text files that have been created by the user, e.g. a file containing a sequence of moves for a robot.
Where's a good place to put those files? In XP you could just stick them in a sub-directory in the application's directory in Program Files. Deprecated I'm sure, but simple. I think Windows 7 gets stroppy if you try to access files in an application's directory, and Windows 8, who knows? I'm pleased to say I've managed to avoid it so far.
Is there a "proper" place to put files that should be accessible to both the application and users? It must be accessible to all users, not just the one who's logged on. I've searched online and found remarkably little information about this.
For the sake of simplicity I'm tempted to just create a directory on the C: drive like C:\My Company\Program Name\. is there anything wrong with that?

Yeah it is a bit more complicated now, but Microsoft tells us it is for the best.
It is pretty common to have a Application.INI in the same directory as your Application.EXE and in the past I'd use that file to hold basic config for my application. You can still do this with LabVIEW but you need to add an extra step in the installer creation which tells Windows that the INI file should be able to be read and written by all users. Just check the Unblock for that file when making an installer.
http://zone.ni.com/reference/en-XX/help/371361K-01/lvdialog/file_set_install_page/
It's non-standard technically, but it is handy to copy the EXE and config together and move them around and have everything still work, instead of now needing to copy config files to various user app data folders.
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.

Best way to create a Windows service from a LabVIEW executable?

What would be the best way to run a LabVIEW executable as a service? I needed this recently and I think I have set up such a service using srvany.exe from the Windows 2003 Resource Kit, but that seems like a bit of a hack. The Kit is not offically supported in Server 2008, but seems to work. I don't know about Server 2012 or beyond.
So what would be the "proper" way of going about creating a Windows service from a headless LabVIEW application?

The proper way is to interface to the according Windows service control API. That is however not a trivial task to do. We used to sell a LabVIEW toolkit which supported a full interface to this, but it's not currently actively marketed.
srvany.exe is sort of a hack but works reasonably well for most use cases, as long as you do not need any further interaction with the service manager interface in Windows than to start and stop your service.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Run labview executable without installing

Hi
We need t run a LabVIEW executable without the need to install the runtime engine first.
In fact we use a LabVIEW program to distribute LabVIEW within our company.
We add our own library and a special license request form and make it possible to install a LabVIEW development environment
with only the push of one button.
In LV8.2 however this no longer works. First the runtime environment has to be installed before we can run our LabVIEW application.
Previous LabVIEW versions worked OK.
Are we missing an option in the installer somewhere or can somebody show the way to make this work again otherwise we have to keep 8.01 until infinity....
greetings from the Netherlands

Hi Albert,
Long time no see... Perhaps at the user group meting okt. 5?
We (Andre) did some experiments with this just last week. He copied everything from the normal installation directory (program files) runtime directory to a new directory on a clean PC. In the same directory he put an executable, and it did run properly (although I think he also copied the models directory to get proper control images).
Only thing is that at the startup of the exe, we get a dialog "Installing...". Still working on that. This might even work from a CD...
He made a big effort to remove all previous LabVIEW stuff, but to be honest, we didn't try it on a completelly "clean" system.
Regards,
Wiebe.
"Albert Geven" <[email protected]> wrote in message news:[email protected]..
Hi We need t run a LabVIEW executable without the need to install the runtime engine first.In fact we use a LabVIEW program to distribute LabVIEW within our company.We add our own library and a special license request form and make it possible to install a LabVIEW development environmentwith only the push of one button.In LV8.2 however this no longer works. First the runtime environment has to be installed before we can run our LabVIEW application.Previous LabVIEW versions worked OK.Are we missing an option in the installer somewhere or can somebody show the way to make this work again otherwise we have to keep 8.01 until infinity....

LabView executable

A LabView programm that runs fine in the development system crashes
always on the same position when it is an executable. I get no errors when
compiling it. Everything looks fine, but it dosen't work.
I hope that somebody can help me?
Ulrich

Greetings,
Most certainly, you should be able to use LabVIEW Executables on Windows Embedded Standard 7 that contain Vision VIs. The cRIO 9082 is a great example, for it uses WES7 and brings in GigE Camera support.
Cordially;
Simon P.
National Instruments
Applications Engineer

Distributed LabVIEW executable won't work!

Hi,
I have two computers, computer A has the LabVIEW 7.0 Express for program development, computer B doesn't has the LabVIEW program installed and only used to run the LabVIEW executable. I have a PCI-6036E daq card and sc-2345 with several SCC modules. NI-DAQ 7.3 driver is installed on both computers. I first install the hardware on computer A and developed a simple LabVIEW program using NI-DAQmx, compile it to an executable and runs fine on computer A. Now I transfer the hardware to computer B, create the DAQmx "tasks" using MAX and make sure they work fine on the test panel. Then I install the executable to computer B using the installer compiled on computer A, which installed all the resource files and run-time, etc. The executable starts fine on computer B, the problem is it doesn't seem to communicate with the daq card. The relay is not close or open, no data is acquired, etc. I also tried to include the hardware configuration option in the compilation, where the exact NI-DAQmx tasks were cloned from computer A to B. Still, the executable can not comunicate with the daq card. Any suggestions?
Thanks,
Xiaofei Jiang

Hello Xiaofei Jiang,
It sounds like you are doing everything correct, but for something things still are not working out. I have four suggestions for you.
1) Confirm that you are correctly using error handling in your VI. You need to make sure that if an error would happen to occur when runnning on the application machine that it would be appropriately notified.
2) Take a look through your code and confirm that no where in there are you hardcoding a path or a number that might not be the same on a development machine as a deployment machine. This might include paths to files or device numbers or additional information.
3) Instead of building an executable out of your code, open the example finder and open up Cont Acq&Graph Voltage-Int Clk.vi (assuming that you are doing some type of AI). Build this into an executable and see if this works out for you.
4) Try to run the deployment application on a different machine other than the one you are currently using, and one that has the same version of the LabVIEW RTE and NI-DAQ installed.
Post back if you have some additional information. Good luck.
Jared A

Problem to run executable in windows 7 64.

I developed an application using labview 8.5. Created an executable from it.
In windows XP i installed the labview runtime engine 8.5 and visa runtime and my EXE worked fine.
Tried the same on windows 7 64 and my application hangs the PC, tried the latest visa runtime with no success.
I basically uses a serial port (com 1) to comunicate witha device.
Tried to run it as windows xp compatible, same problem.
Any ideas?

Thanks for the reply.
Here is my setup:
the runtime for labview - LabVIEW85RuntimeEngineFull.exe
the visa runtime - visa501runtime.exe
and windows 7 64
The application was developed on labview 8.5
According to this URL (http://zone.ni.com/devzone/cda/tut/p/id/10383), the minimum versios of VISA is 4.6.
And checking your FAQ link i got this:
Q. Can I run an executable built with LabVIEW 32-bit on a 64-bit PC?
A. Windows can run 32-bit executables on a 64-bit PC. Therefore, the LabVIEW 32-bit Development System, Run-Time Engine, and executables can be run on Windows 64-bit.
I can send the file, its a stand alone executable, just click and run, no installation required.

My LabVIEW exe starts to run and then stops in Windows 7

I have built an executable in LabVIEW 2010 on a Windows XP machine and set the properties to be built for Windows 7 or later but when I try to run the exe on the Windows 7 machine the application starts up briefly and then stops running with no error message. Has anyone seen this? I have disabled the firewall on the Windows 7 machine.

Hi Wassa,
It's very strange that your application window opens and then slowly fades away while "LabVIEW shuts down." Can you first verify that the VI itself runs properly on the development machine? Can you then build a .EXE and ensure that it too runs properly on the development machine? If we can get the .EXE working on the development machine you have two deployment methods:
1. If you are deploying to a computer that already has the LabVIEW Run-Time Engine and any additional drivers required for your application, then you simply need to copy the .EXE to the deployment machine
2. If you are deploying to a fresh computer that has no NI software, you'll need to create an installer. When creating the installer, you will need to look through the 'Additional Installers' sections and select any of the additional drivers etc. that are required for your application. By default, LabVIEW only includes the Run-Time Engine. If you are missing any of the 'Additional Installers,' the application will not run properly.
Sanjay C.
Embedded Software Product Manager| National Instruments

How to include LabVIEW Run-Time in executable file ?

Hello folks,
I have an application that need the user to simply calling executable file without setting up LabVIEW run-time because my executable file will be posted in LAN and anyone can run it remotely. What should I do? Any help very appreciate...
Thanks so much

You have to have labVIEW run-time installed on your computer in order to run a LabVIEW programs (vi or exe). What you can do when you distribute an exe file is to create an installer which lets you install LabVIEW run-time and create a menu item (in Windows) in the Start>>Programs menus. Then you can distribute the whole package and after running the installer, LabVIEW run time as well as the exe is installed.
You can do this in the installer settings of the Application builder (when you create the .exe file). Go to the "Advanced" section. There you can add the LabVIEW run-time Engine to the installer.
One other possibility you can do if several people want to use the programm over Lan is to use the LabVIEW webserver. You can run a programm somewhere on the
network and other people can open the front panel in their Webbrowser. But maybe that's not exactly what you want. ??

Running A LabVIEW executable in Windows 7

Similar Messages

Maybe you are looking for