Several question s about runtime Engine, application builder and labview player

I am a little confused by all the options to distribute a program.
Please help bij answering (one of) the following questions:
1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
3. What is the advantage of the labview player above the runtime Engine?
All questions refer to the latest software versions of NI software
Thanks in advance,
Regards,
Ferry

ferry1979 wrote:
1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
Yes, the runtime engine contains all the stuff that is common to all LabVIEW applications. This is not any different than e.g. the Visual basic runtime (VBrun...) or dforrt.dll for Fortran.
If you built the application, you can strip it a little bit by including the runtime with the installer and leaving out unneeded modules (see image from the 7.1 builder).
The advantage of a seperate runtime engine is that applications are very small. The runtime needs to be installed only once. On any broadband connection, 33MB is peanuts. I distribute everything without runtine, but tell people to download and install the runtime directly from NI.
(In LabVIEW 4, no runtime was needed, with the disadvantage that even the simplest program was multiple megabytes. Not an efficient solution).
(Maybe in a few years LabVIEW will be so prevalent that the LabVIEW runtime will be part of a standard OS install ;
2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
No. See above.
3. What is the advantage of the labview player above the runtime Engine?
The two are quite different. The labview player is more a simple educational tool, because it lets users inspect the diagram. It is not designed for any serious application deployment.
Message Edited by altenbach on 08-21-2005 10:05 AM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
runtime.png ‏24 KB

Similar Messages

Labview 8 Application Builder and VISA Runtime Engine

Hi,
I am using Labview 8 Application Builder and everything is working fine except for 1 small thing. My program makes use of some of the VISA functions and when I build the application I'm having to include the VISA Runtime Engine Installer as a separate item on the CD to make the .exe file work.
What I would ideally like is for people who want to use the application to run the installer and that all necessary components (including the VISA Runtime Engine) are also installed in the one installation. At the moment they're having to do 2 installations and I would like to streamline this.
Is this possible?
Ken

Hi,
this How-To explains about making those selections and including the different drivers :
http://zone.ni.com/reference/en-XX/help/371361A-01/lvhowto/add_installers_to_build/
and this tutorial covers the screenshots a little more step by step.
http://zone.ni.com/devzone/conceptd.nsf/webmain/5ADBC06AC32E508A8625706E0062EBD1
Hope that helps
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

I have a application build in labview 8.5 for Windows XP using NI Visa functions to interact with hardware , how to make is work in Windows 7 32 bit and Win 7 64 bit

I have a application build in Labview 8.5 which wroks fine with Windows XP , this program uses basic read /write functions of NI Visa to communicate with Hardware . This application doesnt work with Windows 7 32 bit/64 and Vista . What changes i need to do to make it work for the said operating system

srinivas wrote:
Sorry for confusion ,
My question is what changes i need to do in code or while making the installer to make the existing program work with other Windows operating system
You need to make sure the machine have the corresponding NI-VISA installed. Check in the NI software pages for the right version.
Also make sure that the com port's can be selected when you first start the application. Eg. if you refer to VISA "COM1" on the XP machine It might be "COM2" on the Win7 machine.
Br,
/Roger

Application Builder and Demostration App 4600

Besides poking around in the f4600.sql file for pages 1-30'ish AND looking at some of the source code provided at the bottom of each page, is there any better way to (using the Application Builder) to learn how these demonstrations were developed? I'd actually prefer to open in the Application builder and see the properties along with the SQL and PL/SQL.

tx100118 wrote:
Besides poking around in the f4600.sql file for pages 1-30'ish AND looking at some of the source code provided at the bottom of each page, is there any better way to (using the Application Builder) to learn how these demonstrations were developed? I'd actually prefer to open in the Application builder and see the properties along with the SQL and PL/SQL.Just import the <tt>f4600.sql</tt> file and install the app in your workspace. It won't run because it's missing the supporting db objects (obviously installed from elsewhere during the APEX install process), but you can explore how it is constructed.

Application Build problem Labview 8.5.1

Having a problem creating an Installer with 8.5.1. When being built a menu appears asking for
"NI Labview 8.2.1" distribution. Needs to copy a component installed or updated by the distribution to continue building the installer.
Despite trying all of the Disks I have, First quarter DVD, and all of the second quarter CD's it does not recognise any of them. When the CD's or DVD is inserted it shows a nidist.id file which I select (because it says that's what it requires) but them it gives a message stating that
"You cannot choose this folder name; a file of that name exists"
I have tried this build on 2 different machines and get the same response, anyone got any ideas on this or is it a no brainer in 8.5.1?
One last thing if this lot cannot be got to work, the additional files required are:-
Ni Labview Runtime Engine 8.5.1
NI Measurement & Automation Explorer 4.5
NI PXI Config Support for Windows
NI DAQmx 8.7 (unsure if this is included in MAX?)
NI Visa Runtime 4.4
Does anyone know if I just downloaded these from NI website and installed on the computer that will run the final .EXE file it will work?
Labview Version 8.5
Labview Version 8.6
Labview Version 2013

Hello Jack1,
I have been looking into your posts. There are two immediate actions you could try to help. I have identified that you are having issues with the computer recognizing that you have inserted the CD it has requested. Also, you are having trouble with repeatedly being asked to change back and forth through disks, at every attempt to build the installer. As you may need to try this more than once, it may be helpful to you to create a folder for each CD or DVD, and copy and paste the contents of the individiual disks. This software will be recognized, even if copied on to your hard disk.
When you click 'Build', to begin building your installer with your necessary additional resources, you will be asked to insert the last set of CDs or DVDs you have used. However, at the prompt you can click on the 'Folder' icon and browse the folder where you have saved the individual disk contents. The error you were receiving in your first post, "You cannot choose this folder name; a file of that name exists", implies that you were most like click on the *.id file and selecting ok. I have avoided this on my machine by opening the folder with the disk contents, not selecting any files, and the click the 'Current Folder' button. After you have selected it, ensure that you have ticked the box next to 'Cache components from this distribution.' Whether you use the CD, or folders containing the disk contents, this options creates a local copy of the requested files to a cache directory, therefore no requiring the user to input disks, or point to file locations in the future. If you have a repeated patter of building applications and installers, this will quicked your process, and eventually allow to delete the disk contents you have copied to your hard disk.
The disks from your previous installations are requested primarily because of your selection to include NI-DAQmx as an Additional Resource. As this is the main driver, shared components are recognized by the Application Builder. I, therefore, can recommend that you try building the installer with the above steps on your laptop, which your mentioned is a fresh installation.
When you have had a moment to try this, please post back to see if I can answer any further questions on this topic, or know that it has worked.
Regards,
Message Edited by gt3000 on 11-03-2008 03:26 PM
George T.
Applications Engineering Specialist
National Instruments UK and Ireland

Application Builder for labVIEW 7 Doesn't support any report generation function

I'm Using LabVIEW 7.0 to build an application My Application is exporting data to an excel report. the vis were working great until i tried to creat an .EXE file. The application is working fine but when i try to generate the report nothing happens.
So, I decided to test the report generation functions alone (New Report.vi, Append report text.vi and Dispose Report.vi). The Problem Still there, the .EXE file takes no action when i attend to generate a report. any suggetions please.

Shady Yehia wrote:
> I'm Using LabVIEW 7.0 to build an application My Application is
> exporting data to an excel report. the vis were working great until i
> tried to creat an .EXE file. The application is working fine but when
> i try to generate the report nothing happens.
>
> So, I decided to test the report generation functions alone (New
> Report.vi, Append report text.vi and Dispose Report.vi). The Problem
> Still there, the .EXE file takes no action when i attend to generate a
> report. any suggetions please.
Another possible reason besides of possible path problems: Are you
running that application on the same computer? If not you need not only
to install the Runtime-Engine (automatic when you create an installer)
but also the Report Active X support.
To include that into the installer
you go into the Installer Settings Tab, then press the Advanced button
and make sure that you check the NI Reports Support checkbox before
creating an application build.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Application Builder and Corrupt VIs

Howdy All,
I'm developing a Medium-sized application in LabVIEW 7.0 used for instrument control. This application has grown over-time, and currently contains approximately 400 VIs. The basic structure of hte appliation is one main VI that has an instrument status display on the bottom, and a sub-panel on the top, into which all dialogs are loaded for user interaction. Each major task has it's own VI that is loaded into the subpanel as appropriate.
I've read a few stories on the developer exchange about VIs becoming corrupt. I thought these were freak occurences, because by and large, it appears that LabVIEW is fairly stable. However last week I had a VERY scary experience.
I was demonstrating to a collegue the properties of an XY graph control. We changed the colour of one of the plots, then hit cancel. LabVIEW complained of an internal error involving undo.cpp and proceeded to crash. I figured the crash was caused by some strange sequence of events, didn't think much of it, and reloaded my application. After making some changes, I went to the Application Builder to build the application. However the application Builder was complaining about a "missing board" in the DEFAULT build file. I knew immediately that something was VERY wrong. (When I say default build script, I'm referring the default script that is loaded when you press the "Build application or shared library..." button in the tools menu).
(As a side note, does anyone know why the LabVIEW application builder gives such terrible error messages? I always get that "missing board" error when either: one of my support files cannot be found, or one of my dynamic VIs is not executable. Since the error doesn't pinpoint a file, I neeed to go through the files one by one - which is a pain because I have a lot. Another question, why does the application builder ALWAYs ask if you want to save changes to build script, even if you haven't made any changes?)
After loading my build script for the application (which I've used HUNDREDS of times), I got the "missing board" error. I didn't think there was a problem with any of my paths or VIs, but I went throgh each included support file and dynamic VI in the build script to make sure it was there. Though there seemed to be no problems with any of the files, LabVIEW continued to complain.
I figured the problem was specific to the computer I was working on, so I copied the source to another development machine to complete the build. I was VERY scared to find that I got the SAME error on the DEFAULT build script! Also, my actual build script refused to load properly.
This was late at the end of a long day, so I decided to turn of my machines and go home. The next morning, everything worked fine - I was able to build the application, and I haven't had a problem since. (Maybe it was a bad dream, but I have clumps of hair on my desk from the night before...)
I found this experience to be UTTERLY TERRIFYING. Once I had to revert to an archived copy of one of my main VIs, because the current version refused to open, claiming it was corrupt. Since I don't know what's going on behind the scenes in LabVIEW, I'm afraid that tiny internal LabVIEW errors might be adding up. I back-up the source very regularily, since it is such a large project, however I have *real* way of inspecting the integrity of the source.
Does anyone know (A) why this might have happened - especially when the problem reproduced itself on multiple machines (B) has anyone had similar experience with internal LabVIEW errors or corrupt source (C) what sort of internal errors might be piling up that might cause a VI to claim it is "corrupt".
All input is appreciated.
WG

Hi Robert,
For the undo.cpp error, I got a couple different line numbers but didn't write them down. If I get them again, I'll be sure to get the specifics for you.
As for the "missing board", I also got that description a little wrong - the error I'm talking about is:
"Error 7 occured at Inovke Node in Dist read linkages.vi->Dist Cmp Settings to Disk Hier.vi->Build Application.vi
Possible reason(s):
LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for hte operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Unix.
NI-488: Non-existent board."
As you can see, I meant "non-existent board". This error is very easy to reproduce - m
ake a build script and include some extra files. Save and close the build script. Move or rename some of the extra files included in the build. Reload the script. You should get that not very helpful error.
Now that I think about it though, maybe that NI-488 error refers to GPIB control, which I think I have installed, but don't have a GPIB card installed... hmmm... no reason that error should be popping up *there* though...
I could have *sworn* I would also get that error when one of the dynamic VIs in the build is not executable, but I can't seem to reproduce that right now.
Tying back to the original thread - what makes a VI corrupt? I imagine if you cracked the binary file open yourself and messed around with some bits you would probably make the VI corrupt, but I'm assuming that editing a VI normally (ie through LabVIEW) should NOT cause the VIs to become corrupted. Any information on VIs becoming corrupt? Is it somehow related to the undo.cpp errors?(when trying t
o undo some last change that wasn't recorded properly, the VI is modified improperly - after you save and close, it won't reopen?)
Victrick

Problems with Application Builder and NI-DAQmx drivers in Labview 8.2 Professional

Hello everyone,
I am trying to use the application builder to create an executable so that someone without labview is capable of a remote panel connection to connect to our test laboratory. our test laboratory uses the USB Compact DAQ 9172. I did find some other forums that ran into a similar problem where a computer that didnt have labview installed on it looked for a particular driver (nilvaiu.dll). The common solution appeared to be when building the installer, include the current NI-DAQmx (8.3 in our case) option and then the clients worked fine. My question is when i use the application builder to create an installation file for this application, i get a prompt to:
Locate the "National Instruments Device Drivers - February 2006 Disk 1" distribution. LabVIEW needs to copy a component installed or updated by the distribution to continue building the installer.
What is confusing is that the installation cd's in our laboratory are from August 2006 (501165N-03). It didnt make sense to me that i would need to downgrade the drivers from a few months ago, but i've been wrong before. We just upgraded from the full development to the professional version about 2 weeks ago to utilize the application builder function. Has anyone else ran into this problem and could this be a limitation because we purchased the software with the academic discount?
thanks in advance
Chris

Chris,
My "fix" is brute force. Backup everything. Removing all the NI software takes a while. Be sure to remove leftover directories and files.
Altering the windows registry takes seconds and is not hard if you know what you are looking for. I've attached a screen shot with the NI entry selected. This is what I deleted on by machine. The thing to remember is that the registry controls all the software on your pc. Delete/alter the wrong entry and you have problems. Worst case scenario is that you could end up formating the hard drive and starting over from scratch. I'm not trying to scare you, but I want to make sure you understand the potential for harm.
One thing you might try first. NI-DAQmx 8.5 is now available for download from NI. You might try unloading 8.3 and installing 8.5.
Attachments:
regedit pic.JPG ‏102 KB

Application builder and CWGraph3D

Hello all,
I am trying to build a self-executable 3D plotter for a fellow worker using the CWgraph3d. When I go to build the application with application builder I have no issues. When I install the application of the host computer and try to change the 3D plot properties, I am not given the options as when I ran the program inside of LV....Any ideas on what I am doing wrong?
Thanks,
Jay Poret
AOT, Inc.
[email protected]

Travis,
I am still a little confused....All I am trying to do is to make a self-executable 3D plotter that allows me to change things like the scale, titles, etc. I did find a way to use property nodes to bypass this but I am still interested in why the example didn't work. Here are the steps I followed:
In application builder
1) insert the cw3Dgraph.ocx as a source file
2) Use the advanced tab and have the program insert the file in the c:\windows\ssystem32 folder (I confirmed the installer did this)
Outside application builder
3) I registered the .ocx file externally using start>>run>>reg32 c:\windows\system32\cw3dgraph.ocx (when hitting enter the system confirmed that the .ocx file was registered on the computer).
Run executable....I could make 3D graphs, rotate the plot but I could not change the x,y,z scales or anything like that.
Am I missing something here?
Thanks for your help.....
Radman
Travs H. wrote:
Hi Radman!
Maybe Robert will have more to add, but I'll throw in my 2 cents worth :-)
When creating an executable/installer, setting Top-level VIs is what designates what VIs actually open and run when you double-click your exe file. By adding both the DS 3D Graph Reader & Writer as Top-Level VIs, you are indicating that when running the executable you want both of those VIs to automatically open and run.
Now about your concern for the batch file. This document was originally created before the release of Windows XP. With that being said the following:
"Then, set the Installation Destination to be Windows System Directory. This will put the ocx into the System32 directory on NT, ME, and 2000, and the System directory on 9x."
should read:
"Then, set the Installation Destination to be Windows System Directory. This will put the ocx into the System32 directory on XP, NT, ME, and 2000, and the System directory on 9x."
Also, if you need to have the ocx file in different directories depending on the operating system (XP or 2000), you will just need to make two versions of the exe. A WinXP version and a Win2000 version.
Hope this helps!
Travis H.
National Instruments

Application builder and Installation

Elijah Kerry did a real nice power point presentation on Application Builder ( Risk Associated w Source Distribution) back in 2012. I can't remeber what forum/group, etc I found it under. Does anyone know if there is a similar presentation for creating an Installer??
ie:
How do I make sure I get all the files needed to port my code to a target machine?
Do I need to create the exe file 1st?? or does Installer do that for me?? What about MAX?? What about DAQ?? etc, etc.???
Thanks.

Jeff·Þ·Bohrer wrote:
Yes. Tasks Scales and chanels need to be defined somewhere. That *.xml file with a *.lvproj extension is a nice convinient place that DAQmx will look for.
Excuse my ignorance on the subject because I've never used it. But is this useful for deploying DAQmx scales/Channels/Aliases? When I build an EXE and then an installer is the DAQmx scales and channels information inside the .lvproj imported? Or is this just useful for development?
EDIT: It looks like it only has scales/tasks/channels not aliases. So never mind.
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.

Application builder and dynamic class VIs name collision

I'm, using LabView 8.6 and I'm trying to make executable file.
The application builder returns warning:
"LabVIEW prevented a file name collision during the build. Duplicate file names cannot be copied to the same destination. You can rename files as part of the build process to avoid name conflicts."
...and no executable is created.
I'm pretty sure the warning comes from the fact that I use dynamic class member VIs, that are by definition have to have same names in both parent and children.
The following link (http://zone.ni.com/reference/en-XX/help/371361E-01/lvhowto/caveats_apps_dlls/) says " If you don't rename the files, Application Builder moves the files to different folders for you to avoid a filename collision.", but no folders are created.
Any help here?

Hi,
If you have a parent class and one or more child classes, during the build LV will create a folder for each class with a conflicting VI. The offending VIs will be dumped in their respective folders, resolving the conflict. For what it's worth, I've used dynamic dispatch VIs several times in executables in LV 8.6 without seeing the issue you're reporting.
My only advice would be to:
1) make sure that you haven't somehow put two VIs of the same name in the same class (not even sure that's possible).
2) make sure you aren't renaming a VI during the build and creating a conflict
JasonP - CLD

Application Builder and Closing

Hi
Already, another problem has arisen. I have developed a simple VI with no big thing inside. I am using an event structure for handling button presses. To quit my application, I have one button, labeled Quit (who would've guessed) which quits the application. I simply wired that button to the quit terminal of the event structure (ok, to the quit terminal of the while structure around the event structure).
I have also built this application with the Application Builder into a .exe file. I managed to get that Run/Pause buttons away. by checking the appropriate checkboxes inside AppBuilder. But now, what happens is as follows:
* I quit my application by using the red X of the window - everything closes down fine, the window disappears *perfect*
* I quit my application by using the button - the program stops, but the run button appears.
How can I avoid that behaviour?
Thanks for your advice

There's a function in Application Control which is used to close LV once everything's done executing. Be careful when using it while developing, as it will close all open vi's. Granted you get the option to save them, but it's annoying nonetheless.
See the attached image
Message Edited by Novatron on 07-10-2006 11:17 AM
Attachments:
Quit.jpg ‏4 KB

LV 6.0 runtime engine not found with labview 6.1

I recently upgraded to LabView 6.1.
Now when I try to run an exe built under 6.02, I get an error that the 6.0 (or compatable) runtime engine could not be found.
I have the developers version of labview 6.1 installed, and the labview runtime engine 6.1 installed.
Do I need to install 6.0 runtime too? (in that case do I need 5.1 ruintime instaled too for exe's built a log time ago)?
Shouldnt the 6.1 RTE be able to run older exe's?
I could find no solution searching this web site.
Thanks
Larry Junek, Certified LabVIEW Developer

Did you install 6.1 wheer 6.0 was?
You may have lost the 6.0 RTE you did not realize you where using.
Yes you need the version of RTE that matches the app.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Where are Application Builder and SQL/Data Workshops?

I have installed HTML DB (or Application Express) 10.1.0.2 (using the relevant DB server; but without companion tools - but - I hope that I am not loosing anything important from HTML DB, am I?) - installation and automatic configurationi was successfull and at the and I have been advised to use localhost:7779 to access web page - and it worked indeed - but the bad thing is - that I can't found where application developer and SQL, Data workshop can be accessed... seem that they are web browser based solutions - but - there aren't any documents inside Oracle apache web folder that could be perceived as these applications....
In first steps guide there was mentiond to use:
.../pls/application secutiry desciptior/dbhtml
to make first login... - but it does not work for me and seems that in reality address should be different...
Pleas - give some advice - what to do next to access HTML DB developmetn applacations?
Thanx in advance!

The iPhone settings and 3rd party application settings and data created and stored by a 3rd party app are included with the iPhone's backup, which is updated by iTunes as the first step during the iTunes sync process.
This link provides the data included with the iPhone's backup.
http://support.apple.com/kb/HT1766
With XP, the iPhone's backup is located at \Documents and Settings\(username)\Application Data\Apple Computer\MobileSync\Backup\
The iTunes application does not store any data. All data accessed by iTunes is stored elsewhere. Deleting/re-installing or just re-installing iTunes does not delete or affect your iTunes library, and does not delete or affect your iPhone's backup. Deleting iTunes does not delete your iTunes library and it does not delete your iPhone's backup.

Problem with Vision Builder and LabView: Error -1074395995, File not found

I have created an inspection with Vision Builder AI 2009 SP1. In it I load some pictures from the HDD and run some checks over it. It works fine. Then I have migrated it to LabView 2010, I get a message that the migration is successfull, but when I run the VI on LabView I get a fail status. I have been checking my program and I have found and error when I try to load the picture from file: Error -1074395995 occurred at IMAQ ReadImageAndVisionInfo
Possible reason(s): IMAQ Vision: File not found.
But I am not sure which file it refers to. At first I thought it was the picture I wanted to load, but I have checked the path and it is correct, so maybe it refers to another thing. What puzzles me most is that it works perfectly on Vision Builder and I have changed nothing in LabView, maybe it is a problem with the migration. Any clues?

Here's a screenshot of what I'm talking about. Put a break point here and see what the path is and compare that with what Vision Builder AI is using (described where to find this in the previous post). You could find where this global is used to make debugging easier.
Hope this helps,
Brad
Attachments:
Generated Code.png ‏43 KB

Several question s about runtime Engine, application builder and labview player

Similar Messages

Maybe you are looking for