LabView Executable files

I had a question about LabView executables files- (one of the main differences between LabView Full and LabView Professional). If I am able to create LabView executables (LabView Pro), then I would be able to run LabView programs (executable files) on PCs that do not have LabView installed? If I use LabView Full (no executables created), then I can only run LabView files from PCs that have LabView installed?
Thanks,
Alex

Charles_CLD wrote:
As a long time user of LabVIEW and someone who is not in any financial way affiliated with National Instruments, I would highly recommend the Developer Suite over the Pro version. I believe the cost to benefit ratio to be VERY high.
Charles
I agree completely. Besides, once you add one or two of the essential toolkits to the pro version you are at about the same price as the developer suite.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Similar Messages

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

Labview executable file

I created an executable file but find it a bit strang that every time I double click on the *.exe file it will ask me to open a main labview file? I'm not really sure is this how labview executable file works...

Ok, all you need to do is create a wrapper around your existing code that only starts the execution of your main function when the operator presses a button. This wrapper could be as simple as a while loop with a case structure in it. The FALSE case would contain nothing but a short wait. The TRUE case (which is selected when the operator clicks the button) would call your existing VI.
A second "Cancel" button would probibly also be useful to allow you to break out of the loop without running anything.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

How to compare LabVIEW executable file?

I have a labview executable file that I build 2 years ago, and with the same source code, I build a new executable file. Does anybody know how to compare the 2 executables?

Well if you built from the same source the functionality should be the same. But if you build the same source with different versions of LabVIEW then you never know. Maybe the new version exposes a hidden bug in your code or fixes one that you depended on.
There is no way to do what you want by examining the bytes in the exe. You have to just do testing. You could either do this manually or automate it using the Unit Test Framework. There is also VI Tester by JKI.
=====================
LabVIEW 2012

Can an Labview Executable file run automatically upon the boot up of a CPU?

I wanted to use a PC/104 to run a LABView.exe file. So I have two quetions can a Labview .exe program be written so that it dosent need the start buttn pressed to activate it, it just runs upon execution. And the second is that once the PC is booted can it be configured so that the .exe automatically starts?

Hi,
Here is a KnowledgeBase article that I think will be helpful to you as well. Have a great day!
Amanda Howard
Americas Services and Support Recruiting Manager
National Instruments

Control where a LabVIEW executable write it's Settings Configuration file

Is there any way to control which directory a LabVIEW executable writes it's configuration settings file to? I am using version 7.1.

I believe the INI file must be in the same directory as the executable. You can use the keys found in the LabVIEW.ini file and they will apply to your executable without any special programming on your part. That being said, you can always create a custom settings file or files anywhere you like to store configuration information specific to your application.
If we could specify some other path for the executable settings file, it would probably hurt more than help in the long run. The same directory as the executable is the only one whose existance you can be sure of..... or of whose existance you can be sure.
Dan Press
PrimeTest Corp.
www.primetest.com

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. ??

I get an error 1 when I'm building an executable file in Labview 6.0

I'm trying to create an executable file in labview 6.0 but I get an error 1 (see attachment) with a GSim file (control and simulation toolkit). I didn´t install the toolkit (on the computer i´m trying to create the executable) because we lost the CD and we had the toolkit installed on another computer so I copy the files I needed.
Attachments:
error1labview.doc ‏56 KB

You probably have a linkage issue.
Open the top level VI on the machine that has the toolkit installed, and make sure that it opens without an error (the run arraow should be white). Press : ctrl + shift + run arrow. This forces a recompile of the code, and will update the internal links to all the sub-VIs. Then, save the top level VI, and close it. Open a new VI, so that there is only one VI in memeory, and it is a new (blank) VI, and try to build the applictaion again.
J

How to make executable file in labview.

HI All,
I have labview student edition V14 (2014),
I want my vi to be an executable file.
i searched in google but in my vi project its showing only build specefication->new->source distrubtion.
i dont have Application , now how to make an executable file.
Regards
Punith

You need the Professional version to make an executable. You could also buy the App Builder seperately. I don't remember the price at the top of my head.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

How to create executable file in labview 6.0

i have a labview VI file in 6.0 and now i need to create an executable file for that VI.

The Application Builder is an add-on package to LabVIEW and is available from National Instruments. You can use the LabVIEW Application Builder to create stand-alone executable programs, so that you do not need a copy of the LabVIEW development environment to run them. The Application Builder ships with the LabVIEW Professional Development System, but it may be purchased separately if you own the LabVIEW Base Package or the LabVIEW Full Development System.
This URL will help you determine if you have App Builder:
http://www.ni.com/support/labview/toolkits/appbuild/
This URL will step you through creating an executable:
http://zone.ni.com/devzone/conceptd.nsf/webmain/4EF810EE05BEF63C86256BF30062EC31?opendocument
Let me know if you need more help.

Calling executable file generated from labview in C++

Hi,
I am new to LabVIEW. I have to call an executable file from C++ in a system where LabVIEW is not installed and Run Time Engine is installed. Can anyone please guide me with it. Thanks in advance.

If it's just an executable (.exe) and you have the Runtime Engine installed, why not just launch the executable from your C++ application? I think it's something like CreateProcess() (You'll have to look up the details as I'm a LabVIEW not a C++ programmer!).
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets

Improving load times in Linux LabVIEW executable

I'm looking for (simple) ways to improve the loading times in a Linux LabVIEW executable. We're using a low performance, low cost CPU board, and loading times are terrible. The CPU is capable of doing everything after the application is loaded, but takes forever to get there.
One of the problems is the size of the executable, that grows everytime you just look at it. Are there ways to create smaller executables? It runs from a Compact Flash card, which is ofcourse much slower than hard disk.
Another problem is a dynamic vi, that is started for every TCP connection that connects to the application. It takes a long time to load, and connecting too fast can even effectively hang up the system. Starting a handler task takes about half a second, up to a few seconds for the first task.
We're using the LabVIEW 7.1 runtime, system is a 300 MHz cyrix SBC, running from a Compact Flash.

Dennisvr wrote:
I'm looking for
(simple) ways to improve the loading times in a Linux LabVIEW
executable. We're using a low performance, low cost CPU board, and
loading times are terrible. The CPU is capable of doing everything
after the application is loaded, but takes forever to get there. One
of the problems is the size of the executable, that grows everytime you
just look at it. Are there ways to create smaller executables? It runs
from a Compact Flash card, which is ofcourse much slower than hard disk. Another
problem is a dynamic vi, that is started for every TCP connection that
connects to the application. It takes a long time to load, and
connecting too fast can even effectively hang up the system. Starting a
handler task takes about half a second, up to a few seconds for the
first task. We're using the LabVIEW 7.1 runtime, system is a 300 MHz cyrix SBC, running from a Compact Flash.
I'm
not sure about the first part of your question. LabVIEW is highly
binary and does a lot of memory allocations before even one VI is ready
to be started. So maybe the memory manager is a problem. Another issue
is that the Macintosh like resource file format that is used by LabVIEW to store its VIs etc. results in
lots and lots of individual disk accesses with a rther random like
character inside a single file. So if you can configure the read
caching of your disk to use more memory this may significantly increase
the speed of loading LabVIEW VIs or applications.
And finally spawning VIs through VI server is a rather costly operation
especially on low resoruce systems. A VI is more like an executable in
many ways as far as resource consumption is concerned rather than a
thread. A much better way would be to avoid spawning subVIs altogether
and implement a queued TCP/IP server similar to the Date Time Server
example. It is a little extra work to work with this shift register
architecture but it will not have the issues of long load times for
every new TCP/IP connection coming in.
Rolf Kalbermatter
Message Edited by rolfk on 03-07-2006 06:33 PM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

My excel report is not working in executable file ,however,it works well in vi

Hi all ,
Could any one please help me in getting the reason behind the executable file not working for excel report generation,however I can get the same function without any problem in main vi.
I am attaching my code and executable file also ,please have a look into it and let me know where I am wrong.
Thanks & Regards !
sarita
Message Edited by MindPower on 10-24-2007 01:40 AM
Message Edited by MindPower on 10-24-2007 01:43 AM
Attachments:
test datalog.vi ‏264 KB
test datalog-NEW.zip ‏1020 KB

I can't open the vi in the moment. But by your description I think that I know the solution.
When you build the executable you've to add dinammically the vi's from report generator that aren't in your main vi hierarchy. So, you've to open the vi's and find those that are open trough "open vi reference" and add them dinamicaly.
And don't know if these tips are enough.
From NI Zvezdana S.
"When you use the Report Generation Toolkit to build a stand-alone application with the Application Builder, you must add _Word Dynamic VIs.vi from _wordsub.llb and _Excel Dynamic VIs.vi from _exclsub.llb as dynamic VIs. These two VIs contain subVIs that are called dynamically by the high-level Report Generation VIs. I believe that if you grab these VIs from the (desired office version part of the) installation CD instead of from the development machine, then everything should work. "
Software developer
www.mcm-electronics.com
PS: Don't forget to rate a good anwser ; )
Currently using Labview 2011
PORTUGAL

Open VI Reference to a LabVIEW executable.

Hello,
I haven't done this for a while and it's not working like expected. I'm trying to "Open VI Reference" from executable A.exe to B.exe. I'm trying to get a control value from B.exe in A.exe. Can someone send me an example?
Right now I'm at this stage: I have A.exe running as a LabVIEW executable. I'm trying to "Open VI Reference" to A.exe from LabVIEW development without success. Not sure what I'm doing wrong.
Don't hesitate to ask more info if you need some.
LabVIEW 2012, Windows 8.1.
Thanks,
Michel
Solved!
Go to Solution.

Bob_Schor wrote:
Once you have an Executable, does it matter that the underlying Development system is LabVIEW, rather than (say) Visual Studio, or Matlab? I suppose you could write an application that "knows" to, for example, listen to a TCP/IP port and interpret/execute commands, but that doesn't sound like the question being asked.
BS
LabVIEW-built executables still run as VI's in the RTE, though. Their identities have not been abstracted away into one single object or anything, and they still have name-based VI server access.
You can configure a build specification to include almost nothing, and require the VI files to be present in expected locations (i.e build specification's data or support directories). By default, all items in an executable application build specification are set to be put in the same location as their caller, which results in most things going into the .exe file, internally referenced in a directory-esque form like crossrulz mentioned, "MyExecutable.exe\MySubVI.vi".

Is it possible to call a VI that is inside a LabVIEW executable from a TestStand sequence?

I have created a custom TestStand operator interface and have modified the default sequential process model to display a UUT information dialog that prompts for more information than just the UUT serial number. This UUT information dialog is a LabVIEW VI. To distribute the operator interface, I build it into an executable. As part of the build process, I make a copy of the UUT information dialog VI (which is part of my operator interface project) and place it in the same folder as the executable. I have then configured the sequential process model to call the dialog VI from this location. It would be really nice if I could embed the UUT information dialog VI inside the operator interface executable so that I could distribute just an executable instead of an executable and separate VIs. Is this possible? In other words, is it possible to call a VI that is inside a LabVIEW executable from a TestStand sequence just like a standard LabVIEW VI call?

Ryan,
The dialog that you've created isn't being directly called by the OI at all and shouldn't need to be included in the same directory as the OI for distribution. Since you are modifying the PreUUT of the default process model, you will give the path to the VI in that step, create a deployment and then manually copy the VI to the directory referenced in the step. The VI is considered a support file for the process model and is not related to the OI at all.
Test Engineer - CTA

LabView Executable files

Similar Messages

Maybe you are looking for