Labview .exe as portable

Hi all,
is it possible to run a compiled Labview program like a "portable" ?
Means all necessary components (LV runtime, VISA etc) will be linked into one (big) *.exe during the application build and the programm is then running directly without any additional runtime/VISA installation.
I do not mean to build an installer with all components inside the installer and I do not mean a silent LV runtime installation from an installer. I would love to have everything in one *.exe , ready to run whatever PC I`m using...
Is something like this possible?
best regards
MArkus

Cameyo works. I just tested it at home, and I will try a few more computers at work tomorrow to see how well the compatibility goes. Check it out. It takes awhile to install. Cameyo works by taking a "snapshot" of your system pre-installation, a "snapshot" of the system post-installation and then compiles the differences into a single executable program (called a Cameyo "app").
The instrucitons on the web site are easy enough to follow... but here is a list of things to keep in mind when using it to make stand-alone LabVIEW applicaitons:
* You need to make an installer that will install you LabVIEW program and the minimum amount of NI software (Runtime+whatever).
* You will probably be most successful if you capture the Cameyo app on a Windows PC that does not have any NI software previously installed. To capture the installation properly, Cameyo needs to be able to track all of the changes that the installer makes. In order to get a clean capture the runtime that needs to be included in the Cameyo app needs to be installed.
My test application (a simple LVM plotter program I use to process data), works and I haven't found any bugs while using it. The initial launch was a Cameyo window that asked if I wanted to launch my .EXE or a National Instruments Bug Reporting executable that probably comes included with the runtime somewhere. There was a checkbox to always run my .EXE.
My LVM plotter application listens for "OS Open File" events. Once I associated the correct file type to the stand-alone .exe, funtionality works as expected: double-clicking on files opens them in my software.
Pretty awesome. I really hadn't thought of this before. My boss was just complaining about having to install the runtimes (especially since some of my applications spread across multiple versions of LabVIEW), and this may be a solution. I think there might even be a way to edit a Cameyo app. It may be that once a proper LabVIEW Runtime "wrapper" is created, switching out your own LabVIEW application executable is trivial. I'll have to play with it some more.

Similar Messages

How do I troubleshoot installation/distribution of a LabVIEW .exe which processes data using Matlab when it works on some computers but not others?

I've been given the unenviable task of troubleshooting and installing/distributing software written by a former co-worker. I've modified the LabVIEW code and built an .exe file. I've successfully installed the Labview .exe file on several computers, but it won't work on some others. What's more baffling is that I installed it successfully on one computer, uninstalled it, and tried reinstalling it with no success. In fact, it's a new error (Dr. Watson for Windows NT application error). It doesn't help that I have different versions of LabVIEW and Matlab on the target computers. Some have LabVIEW 5.1, some
have 5.0, and some don't have it at all. Some have Matlab 5.2, some have 5.3 (R11) and some have 6.0 (R12). It's also not clear to me where the Matlab m files should be located. I'm not sure if it's a LabVIEW Runtime Engine problem, or if it's a Matlab problem. I've also wondered how LabVIEW and Matlab talk to each other. When LabVIEW calls Matlab, it seems that Matlab is running in the background. In other words, clicking on the Matlab Command Window and typing "whos" or any other command/variable doesn't work.

Jay del Rosario wrote:
>
> How do I troubleshoot installation/distribution of a LabVIEW .exe
> which processes data using Matlab when it works on some computers but
> not others?
Poke around zone.ni.com and
http://digital.natinst.com/public.nsf/$$Search/ .
Good luck, Mark

How do I make a labview exe to run like a windows on-screen keyboard

Hi,
I am trying to run two labview exe simultaneously. Work of exe 1 is to control some hardware and work of exe 2 is to wait for user event, once user press a button in exe 2 it has to exit the exe 1 and restart it.
Problem here is exe 1 uses the whole screen to run(1024*768), when I click any button in exe 1 the exe 2 goes backwards so I am not able to use the exe 2.
Thanks,
Vignesh

Don't make them modal window...!!
Edited: hyperlink added to the text.
I am not allergic to Kudos, in fact I love Kudos.
Make your LabVIEW experience more CONVENIENT.

How To Use Exported Function "CallInstrument" of LabView.exe ?

Hello!
I want to use the function "CallInstrument" to dynamically call VIs with LabView. Did anyone has experiences with this function?
All I kow is following:
The function is used by LabView Internals and its Runtime Library. Its exported by LabView.Exe and lvrt.dll.
Its prototype is maybe:
int CallInstrument(CPStr* VIPath, int controlcount, int indicatorcount, int options, [ Variable List of Control/Indicator Parameters ]... );
( CPStr Type is a StringArray of PStr (Short PascalStrings) as it is used by LabView to store Path datatypes. )
I whould be glad, if anyone has information about this function.

Dear Rolf Kalbermatter,
Thirst, thanks a lot for your answer! -
You sure right, It whould be much much more comfortable to use the VI Server.
And you're also right... using a undocumented dll-function is absolutly no longtime solution.
Currently I am using VI Server for my problem, but it doesn't fit my interesst so much.
But I will explain, what I'm trying to do.
I want to call a VI dynamically from LabView, giving Parameters to its Controls and receive Results from its Indicators.
Realy no big job, but VI Server only let you do this that easy if you have a VI Typedef. otherwise... with untyped VIs, its not that simple. Ok.. its not impossible, you can use "GetAllControlValues" and "SetControlValue" (functions from VI server) and the call "RunVi". But this can get slow (>100ms per call :/ )
I'm looking for a alternative function, which let me call a VI dynamically with userdefined Parameters. Maybe you know the ActiveX Interface IVirtualInstrument and its Function "Call2" - it is a nice example, what kind of function i want.
But this function is not directly available by the VI Server--- i don't know for what reason.
Then i tried to make use of "Call2" from within LabView, and it took me some time to find out the right Parametersyntax but finnaly i got it and it worked fine ... but it was no long time until problems occur. I cannot tell what really went wrong, but sometimes labview simply crashed or hang into a loop reseting some VIs. And its also impossible to stop a running vi, with has made a call to "Call2", if the call doesn't return by itself.
Next step is/was trying to take advantage of CallInstrument. So, yesterday... after hours of analysing assemblercode, i finnally found out the correct use of LabView.exe->CallInstrument and i'm very impressed about its speed (0-15ms per call). The prototype seem to be the same as you explained in your reply int CallInstrument(Path path, Bool modal, int32 nInputs, int32 nOutputs, ...)
But It has the same problem as its ActiveX derivat "Call2".. if you call an endless looping VI, LabView cannot stop your caller-vi. The other bad thing is, that this function is using dynamic paramterlist, which are placed directly onto the stack!
That means that the paramter count on the stack is NOT FIXED (printf makes it the same). LabVIews DLL InvokeNode doesn't support this.
At my current position, it looks like i have three possiblities but no one fits into my interesst.
(continued with next answer)

How to send a command from a vc++.exe to LABVIEW.exe in order to control the button on the LABVIEW.exe

Hello, everyone. Using VC++, I have gotten the handle of a *.exe(built by Labview), but I cannot get the button handle. I want to get the button handle and post the message to control the button. How can I do that? When I use the SPY++, the *.exe(built by Labview) have not any child windows which is very different from the *.exe(built by VC++). In SPY++, what is the LVDChild class? How can I send the message to control the button on *.exe(built by Labview)???
That is to send a command from a vc++.exe to LABVIEW.exe in order to control the button on the LABVIEW.exe. How can I get it ?
Thank you!

hummingbird wrote:
Thank you! But I dont kown how to use vi server to raise a value signalling event. Can we put vi server into the vc program? Can you give me some more information or some examples, hehe!
hummingbird
Checkout the LabVIEW ActiveX server interface in the User Manual in Chapter 20, Windows Connectivity and the VI Server Reference in Chapter 17, Programmatically Controlling VIs.
There is a sample for Visual Basic under examples/comm/VBtoLV.frm, which should be quite simple to translate to Visual C as long as you can figure out the basics of ActiveX programming in VC (I have never done anything with ActiveX in VC). For those basics I would recommend some text book or MSDN.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Application Builder Error "Browse to LabVIEW.exe"

LabVIEW gurus...
I am currently building a standalone app from my project. When I run the application (which builds successfully), LabVIEW prompts me to browse to the LabVIEW.exe file. However, I want this app to run on a computer that will not have LabVIEW installed, and so browsing to this file isn't an option.
I know that the reason for this problem is that I'm using 2 call library functions named StrLen and MoveBlock within the LabVIEW.exe library (to access data from a pointer to a pointer).
LabVIEW.exe shows up as one of the dependencies in my project, but I can't figure out how to add it to my build specifications. I tried to build an installer and include the LabVIEW runtime environment, but this doesn't seem to work either.
Any suggestions would be greatly appreciated!
I'm using LabVIEW 8.6.
Thanks,
Jason
Solved!
Go to Solution.

In the dll call simply type LabVIEW without any path. This should work (I used it on 7.1)to automagicallylink it.
The functions are also located in the lvrt.dll which is the main part of the runtime engine.
Felix
www.aescusoft.de
My latest community nugget on producer/consumer design
My current blog: A journey through uml

Is there a way I can save switch settings so when I reopen a Labview exe it remembers how I set my switches?

We are using Labview to create a exe file. However when a user reopens the exe all the user settings in the labview exe are lost. These settings are mostly switches either turned on or off. I would like to find a way so that once the switches are set each time you reopen the exe file the switches are as you left them set.
I am very new to Labview so any help would be very much appreciated.

I think your best bet is go to the File I/O>Configuration File VIs and create an .ini file. When you program starts, it would read the file and set the controls using local variables. Then, prior to exiting, get the control values and write them to the file. You could even read and write different files - allowing for a whole lot of different configurations to be saved. In the shipping examples, go to Fundamentals>File Input and Output>Read Configuration Settings File.vi and Write Configuration Settings File.vi to get a basic idea of how the functions are used.

Embedded Labview exe in a LabView program

Is it possible to integrate an exisiting LabView *.exe file in another LabView vi or LabView project?
The existing LabView *.exe does output some measurement data on the front panel, but I would need this data written e.g. to an Excel sheet. So I thought it must be possible to embed the LabView *.exe file into another LabView vi, that reads data from the *.exe file and writes the data into a data file.
I don't have access to the original LabView program, before it was converted to an *.exe file and I don't know the settings used to built the *.exe.
Toodles,
Optimike

Without testing I'm not sure if it is working.
Maybe you should be able to open an application reference to the application. You should add the entries for VI Server in the configuration file to listen on a specific port. In LV 8.6.1 you can open the application with this port. With this reference you can try to open a VI reference for the VI from which you want the data. Use Get CTRL Value to read the data from the control.
The application must be running before you can do this. For the final solution you must make any error handling on errors by the Open Application Reference primitive.
The thing I'm not sure about is if this will work across different versions of LV.
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

How to run the LabVIEW exe as background process?

Dear All,
               I want to run my LabVIEW exe as background process, which wont show as the process in the task bar as shown in the .jpeg file.
                I want to run it as a background services as like runs in the windows processes.
                Please suggest me something.
Thanks,
Nishant

Dear Smercurio,
           Thanks for the good one, but it still requires the windows XP or later OS, when i extract the software, it gives me this error.
           Even Fire Daemon software (same one provided by Alessio in this post) is also running the same, and we even dont have to make it Automatic to start at boot up time, it automatically creates the automatic service which also runs at boot time, so not to worry about anything.
Thanks,
Nishant
Message Edited by Nishant on 12-05-2006 10:12 PM
Message Edited by Nishant on 12-05-2006 10:16 PM
Attachments:
rktools error.jpg ‏12 KB
rktools error.jpg ‏12 KB
rktools error.jpg ‏12 KB

Error in LabView.exe after each start

I installed LabView 7.0 in an older computer (Pentium III, 500 MHz, 512M RAM, Windows 2k sp4) along with GPIB and E-series PCI cards. Each time I open LabView it crashes and says "LabView.exe has generated errors and will be closed by Windows. An error log is being generated." The error log is attached, but means nothing to me. It crashes with regularity within 30 sec of opening LabView but I seem to be able to run .vi's during that time. I've tried:
1) Reinstalling
2) updating video card driver and ActiveX
3) installing on a different drive
none of these help.
Any help you may have would be appreciated.
Attachments:
LabVIEWlog.txt ‏1 KB

Hello,
The file you attached is a LabVIEW.ini file, where the configuration settings are stored. Please find the error log file, and this should give you a better idea what might have caused the error.
There are two types of log files. There are those created by LabVIEW and those created by Windows.
The log file created after internal LabVIEW errors is called LabVIEW_Failure_Log.txt and it is stored in your temporary LabVIEW directory. By default, this directory is located at C:\Documents and Settings\(User Name)\Local Settings\Temp (Windows 2000).
NOTE: By default, the Local Settings folder is a hidden folder. In order to view hidden files and folders in Windows Explorer, select Tools » Folder Options » View. In the Advanced Settings field, select Show
hidden files and folders.
If you have modified the location of you temporary directory, the log file will be located there. To view or change LabVIEW's temporary directory path, go to Tools » Options » Paths » Temporary Directory. For more information on the error information contained in the LabVIEW_Failure_Log.txt file, visit the LabVIEW Internal Error Support Page linked below.
If you receive an error message saying that LabVIEW has generated errors and will be closed by Windows, there will be a different log file created. This is a log file created by Windows, and by default it is a Dr. Watson's error log file. These log files are saved as .log file under ...\WINNT folder for NT based systems, and as .wlg under ...\Windows\Drwatson folder for Windows 9.x systems.
If you open just LabVIEW, without trying to open a VI, will you still receive the crash? If so, can you create a new simple VI similar to the VIs that crash LabVIEW and run it? Do you call any hardware driver or o
ther dlls with the VIs that cause LabVIEW to crash?
Zvezdana S.
National Instruments

Labview.exe error is generating

It is giving me labview.exe has generated error message, when I am trying to generate, data log file with time stamp, to find last run of my program. I have attached the vi here.
Message Edited by Support on 04-13-2006 10:46 AM
Attachments:
get_last_run.vi ‏69 KB

I'm assuming that the VI you posted is running as a subVI in your main and that you are getting the path somewhere else. If that's the case, then you should know that the path to a folder is different when you build a executable. For example, if you use something like Current VI's Path, in the development environment, it might be something like c:\folder\example.vi. In an executable, the path would be c:\folder\application.exe\example.vi. You need to do an extra strip path in an executable. You can use the Application property called Application.Type to determine whether or not you are working with an exe or development system to decide whether or not to do an extra strip path. There have been numerous postings on this exact same topic and if you need example code, you can search the forum.
p.s. It's not a good idea to post your phone number and email address in a public forum unless you enjoy spam and unsolicited phone calls. It's also a bit unreasonable to expect the users of this forum (most of whom do not work for NI) to respond directly to you.
Message Edited by Dennis Knutson on 04-13-2006 09:22 AM

Labview exe in web browser

hi
i want to open or run labview exe or vi on web browser by calling html page link . i created the html page of vi which is statup vi of my application but this required application already in running condition, and i want to open and run vi by calling url ,so please help me if any solution for this..........

A url always require a running webserver/webservice.
Check the webservice example on how to deploy it to answer to url calls.
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

How to run labview exe with command line

I would like to launch a labview exe with a command line.
I would like to get advice how to launch the Labview exe with giving values to the control parameters?
You can view the example where x,y are the controls
Solved!
Go to Solution.
Attachments:
exe.png ‏65 KB

There is a much more detailed guide here, which I reference below:
1. First you will enable it in the settings:
1. Open the properties for the application's build specification
2. Navigate to the Advanced category
3. Check the Pass all command line arguments to application box
To pass the command line arguments to the application and access them in your code follow the same steps as for LabVIEW 7.x.
2. Then you will use two hypens (--) to pass command line arguments to the VI.
When you launch LabVIEW or a stand-alone executable from the command line, you can pass user-defined arguments to the application. User-defined arguments start after two hyphens (– –) surrounded by spaces in the command line. For example, the following command line entry will launch LabVIEW 7.1 and open test.vi from the root of C:\ and pass 2 arguments, 1000 and sine:
"C:\Program Files\National Instruments\LabVIEW 7.1\LabVIEW.exe" "C:\test.vi" –– 1000 sine
You can also pass a command line argument directly to an EXE without launching LabVIEW, as long as the machine has the appropriate Run-Time Engine and necessary drivers. For example, if test.vi was built into an executable, it could be called as follows:
"<build directory>\test.exe" –– 1000 sine
3. Lastly, you will use a property node to wire them to your controls:
LabVIEW passes the arguments from the command line to the block diagram of the VI or EXE you launch. You can reference the arguments in the block diagram by using the Application:Command Line Arguments selection in a property node, as shown below.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If someone helped you out, please select their post as the solution and/or give them Kudos!

I have Labview 5.0 and I can't run a program it gives me a runrime error C++ relating to the Labview exe file. Do you know where to start to fix this?

I've had this version for quite a long time and haven't had any problems with it. When I start Labview normally it seems to work fine I can look at individual Vi's and such but when I go to start a Vi program or even the tutorial it gives me a "Runtime error message C++
C:\Program File\National Instruments\LabView\LabView.exe abnmormal program termination." I'm not sure if it is a computer problem DAQ card (PCI 6023E) problem or a software glich. If you have any ideas of where to start tracking this down please let me know ASAP. It is a work stoppage situation.
Thanks for your consideration
Maurice Massey
UES,Inc

Have you tried doing a repair or reinstalling?

Open Independent Mulitple sessions with oracle in a LabVIEW exe

Is it possible to maintain different sessions to same database from within a labVIEW exe. I need to have a server to which multiple clients connect. Server starts handler for each client and each handler needs to connect to the database and transact on its own and get some data for the client. This is basically to achieve concurrency. But the operations are happening only sequentially. Please help.

Your two other postings:
"Parsing an SQL statement coming in the way of reentrancy."
"NEW!! Parsing an SQL statement coming in the way of reentrancy."
I put a link to all your postings here to help others on the discussion forum to follow your questions.
The problem may be that your server has a single CPU and that it can only do one thing at a time. Another limitation may be the abstraction layer for your database. What version of the Oracle d
b are you using? Do you have this problem across computers or just on a single machine?

Labview .exe as portable

Similar Messages

Maybe you are looking for