Can visa runtime engine be included in application build?

I just installed my program on a new machine and it wouldn't work. Turned
out I needed to also install the visa runtime engine. Is there any way to
automatically include that in the application build?

I've seen that you can tick of under the "additional installers" that Visa runtime is included, however, this will look for the installer files on the CD's. Is there a way to update this ? (I have 4.0 on the disc, and would like to included 4.2 in my build for installation/deployment.
The file I download from NI is a .exe, but the linking to the build configurator is some strange windows code (see attached screenshot)
/Brian
Attachments:
screenshot 13-08-2007 17.57.JPG ‏95 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

NI VISA Runtime engine

When "Building" a LabVIEW program containing NI-VISA sub VI's (e.g. to communicate with USB), I have had problems getting the "Built code" to find my NI VISA devices, even though the NI VISA USB Drivers are correctly installed on the "target machine".
(The "built" code WILL run if the target machine has a LabVIEW installation on it, including NI VISA)
So - will the NI VISA runtime engine be automatically included in the "Build" (Because of the NI VISA sub VI's), or do I have to specify this myself - And how?
Thanks. Peter.
Solved!
Go to Solution.

You specify installing the NI VISA Runtime Engine when you build and installer for your built executable. Look on the Additional Installers tab of the Installer Properties Dialog Box. The NI VISA Runtime Engine should be selected automatically but if it's not you can uncheck the Automatically select recomended installers checkbox and select any other installers you want to include in your install.
If you're not using an installer then no runtime engines are installed and you'll have to do that manually on each machine you copy the executable to.
This all assumes LabVIEW 2013. The selection process is slightly different in earlier versions but all the options are still available.
Kelly Bersch
Certified LabVIEW Developer
Kudos are always welcome

Runtime Engine 8 & Application deployment

Can anyone direct me to a kbase article on the correct way to deploy applications using the latest runtime engine?
My first application said it was missing one of the libraries used to create the VI - why wouldn't the build include any VI's in the program etc?
I could use a good tutorial or article explaining the correct steps etc.
thanks!'
m

Found solution to my own problem
Best practices:
http://zone.ni.com/devzone/conceptd.nsf/webmain/BBE67528EBCA22B7862570700077EBB9#9
Using application builder:
http://zone.ni.com/devzone/conceptd.nsf/webmain/5ADBC06AC32E508A8625706E0062EBD1

Can't remove Front Panels in Application Builder

I have had a few issues using Application Builder (v7.1) in regards to it removing or not removing front panels for my subvi's when I was trying to compile. Here are the conclusions I came to if anyone else runs into the problems I had.
Problem 1) Some of the front panels were being removed for dynamically loaded VI's, which were not set as dynamic VI's in the Application Builder, but which were static-linked VI's in the program (so they were loaded in memory as linked subvi's but called dynamically). When the Application Builder decided to remove the front panel for those VI's, there was an error when loading them dynamically.
Problem 2) Some of the front panels were NOT being removed for subvi's that I didn't want to have their front panel built into the compiled program. Loading front panels that are not needed uses extra memory, but there was no way to change the option to not load the front panel for certain particular subvi's in Application Builder--the option was grayed out.
For problem 1, I decided not to worry about linking the files dynamically in the Application Builder, but to just make sure the Application Builder would include their front panels. For problem 2, I had to figure out what was making Application Builder force the front panels to be included when I deemed it unnecessary, so that I could fix them not to be included. Basically then, going through my VI's that were forcibly included, I came up with a list of stuff I began checking for each time I would run into one where I didn't want to include the front panel. I have attached my list to this post.
My solution for problem 1 was then to use a customized appearance for my static-linked / dynamically loaded VI's, and disable the menu bar (forces the front panel to be included by Application Builder without changing appearance, since I never actually see the FP). My solution for problem 2 was often to remove property nodes referencing text on the front panel controls. Sometimes I was able to perform a numeric->text or enum->text conversion instead of referencing the text of the control itself, and sometimes I realized I didn't want anything to change and that it was ok to include the front panel so I could (for example) get a list of strings for my enum control.
I have attached the reference list I came up with of things to check for to make sure your VI properties are set correctly if you are trying to get Application Builder NOT to include the front panel of your subvi. The list might not be complete, but it's helped me to narrow down things very quickly and find the problems I was having.
Attachments:
ThingsToCheck.doc ‏61 KB

m3nth wrote:
Problem 1) Some of the front panels were being removed for dynamically loaded VI's, which were not set as dynamic VI's in the Application Builder, but which were static-linked VI's in the program (so they were loaded in memory as linked subvi's but called dynamically). When the Application Builder decided to remove the front panel for those VI's, there was an error when loading them dynamically.
This is expected behaviour. The application has no way of knowing that these VIs will at some time be called dynamically. That would require analysing and understanding the entire program and in cases where you calculate the dynamic VI to be called at runtime it still wouldn't be feasable to do so.
m3nth wrote:
Problem 2) Some of the front panels were NOT being removed for subvi's that I didn't want to have their front panel built into the compiled program. Loading front panels that are not needed uses extra memory, but there was no way to change the option to not load the front panel for certain particular subvi's in Application Builder--the option was grayed out.
There are several reasons why a front panel is needed. One of them is when the VI is called dynamically, even if the FP is never displayed and AppBuilder will account for that for VIs which have been added as dynamic VI to the project.
The other is when a VI uses some Property Nodes or Attribute Nodes as they are called now.
So to solve your problem 1) you could also just drop some property node in the diagram of such VIs and be done with it.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Runtime Error building Installer with NI-VISA Runtime

Greetings, I'm getting this error whenever I check the "NI-VISA Runtime" option in the installer app builder.
Everything builds fine when I check only the Runtime Engine. Shown below is what causes the RUNTIME ERROR and closes Labview Unexpectedly.
Any help you could provide would be very much appreciated.
Regards,
JD

Hi JD,
This is a relatively common error with the Application Builder that can happen for several different reasons, namely registry keys pointing to installations that no longer exist. The easiest way to identify the problem is to get detailed information about the installer build. Here are directions:
LabVIEW has the
ability to create a very detailed log of the events that occur when
building an application or installer. To enable this feature, open up
the LabVIEW.ini file and copy "CDK.EnableLog=true" to the bottom
of the file. Save the changes and close the ini file. The LabVIEW.ini
file is usually located in C:\Program Files\National
Instruments\LabVIEW X.X
Enabling this feature will create a log file in the %temp% directory of your computer (%...% means a computer variable) .
To
find out where this temp directory is located, go to Start>>Run.
Type in "cmd". Then type "set". This will return all of your computer's
variable names.
Look for TEMP in the list of variable names. You should see something like "TEMP=C:\DOCUME~1\user\LOCALS~1\Temp".
Navigate to this directory using Windows Explorer.
You
should see a file named "Name.log" where "name" is the name of your
build specification. For example, you might see "My Installer.log" if
the name of your build specification is "My Installer".
This will give you a more detailed log of the attempted build and, if I'm correct about why this particular build failed, show you which installer is expected at that registry. If the registry points to a directory without the necessary installer (i.e. VISA), simply delete the registry and allow the App Builder to prompt you to to point to the correct location.
Michael K.
| Michael K | Project Manager | LabVIEW R&D | National Instruments |

How to add visa usb support to the application builder?

Is it possible to add VISA USB drivers to the application installer?
www.xinstruments.com
Custom Software for Industrial Automation
www.hdrconverter.com
Picture processing made easy

I'm afraid you can't do that. The LabVIEW 7.0 application builder only supports adding the VISA serial port driver to the application builder installer.
You will have to install the VISA support for USB separately by using the VISA 3.0 runtime installer.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

What is minimum runtime engine size when installed on XP embedded OS

I hope to build move an existing Labview 8.6 application to a Windows XP embedded machine and would like to know if their are any tools available to help minimize the hard disk memory requirement, specifically can the runtime engine installation be micro managed so that absolutely nothing that is not required by the application is installed?
If not, is their some way to install the runtime engine and then remove unused items, for instance one .dll file at a time?
I would appreciate any guidance.
Thanks,
Bernie

I believe NI does not officially support running LV apps on XPe, but if you search, you should find some references to it. In any case, I doubt you will find anything relating to the size of the RTE. You can probably safely remove some of the support files (e.g. language files, which take up some space), but I've never done it and it isn't necessarily safe.
In older versions, you could simply use all the files from the RTE folder if you didn't require any drivers, but I believe that doesn't work since ~8.0.
Try to take over the world!

Linux VI with Runtime Engine Only

Hi,
We're trying to start a VI on a Linux system, with only the runtime engine installed. But we're having a few problems...
First, if the runtime engine installed without errors ("rpm --install labview71-rte......i386.rpm" and "rpm --install labview-rte-aal......i386.rpm") how can I know for sure that it's working? I can't find any file that indicates that it is installed...
Is it possible (just like under windows) to start a VI with only the runtime engine? What should I call on the shell to start a VI?
Is it possible to run a windows VI under Linux, with only the runtime engine? I read somewhere on www.ni.com that to run a VI a rte of the LabVIEW version used to build the VI is needed. But is LV7.1 for Linux the same version as LV7.1 for windows? Is the Linux runtime engine capable of running the windows VI?
In short, what we like to do is: Use windows to develop some VI's with serial communication. Copy the VI's to a Linux system. Start the VI's.
Any ideas are greatly appreciated.
Wiebe.

"shoneill" <[email protected]> wrote in message news:[email protected]...
Wiebe,I wrote that the binary code is OS dependent, not independent.  Please re-check my post (and your reference to my post to rule out cheeky editing.... )Regarding running a linux VI on linux without the development
You're right. Let's blame it on the language barier (on my side), and today being fryday. Still I don't see why assembler code can't be the same on two exactly the same i386 processors. The OS stuff should be handled in the runtime engine, and the add's mul's, call's etc. are the same. But I haven't given in much thought, and never tried anything like that. I'm sure their will be some problems.
environment, I wouldn't know since I've never used LV on linux (yet).  I thought the original duscussion was about running a VI from one platform on another without requiring the development environment to re-compile. 
It was about running a VI on Linux with only the rte. And what's needed to make this happen.
Can't you just build a wrapper VI to call the VI from a built application (provide path and hey presto, it can be called dynamincally.....no?)I also agree that a bit more multi-platform support would ultimately help NI, but I can understand
Yes, if we had an application builder for Linux, we could make a wrapper. It would solve the licensing problem. Perhaps someone can make a Linux application wrapper/vi starter for LV8.2 (we'd be happy with any version though)?
About the support.. Somehow someone forget to put all the Linux documentation on ni.com.
the thinking behind it.  Not that I agree, I just understand Further, I believe the run-time is required to prevent each and every LV application being huge.  But sometimes I wish we could distribute without theis run-time Stigma (or better - have the choice).You've raised an interesting point by questioning the existance of the run-time engine......Shane.Message Edited by shoneill on 02-09-2007 04:01 PM
Someone ought to make a virtual machine that can execute LabVIEW's executable code inside a vi, and simulate the runtime engine at the same time : ) It will take some time though...
Regards, Wiebe.

Looking for a VISA Runtime Merge Module

I am building an installer with install shield. I have been able to find a LabVIEW Runtime Merge Module and that seems to work great. But, I need one for the VISA RunTime.

You can download the VISA RunTime Engine from NI's website ( click here ) and have your installer also install the RunTime engine. This link will take you to an NI Knowledge Base which describes how to do this.
J.R. Allen

Where do I find the VISA installation drivers to add to my application builder for my LabVIEW app?

I need to add the VISA installation drivers to my LabVIEW application builder, but I don't know where to locate them. (I found the instructions on adding the drivers, but it didn't tell how to find them: http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/e09ba0e2f31d304f86256a640070058e?OpenDoc ument)

The following webpage contains the NI VISA drivers that you can download:
http://digital.ni.com/softlib.nsf/display?ReadForm&lookup=NI-VISA&view=current&node=132060_US
Chris_Mitchell
Product Development Engineer
Certified LabVIEW Architect

NI-VISA Runtime 4.3 Additional Installer problem

Hello,
I am using Project Explorer and I'm trying to include NI-VISA Runtime 4.3, but during the build I get a message that says:
Locate the "Activate" distribution. LabVIEW needs to copy a component installed or updated by the distribution to continue building the installer.
I don't know what the "Activate" distribution is or where to find it! Please help.
See attachments.
Message Edited by Sidd on 10-09-2008 02:02 PM
Solved!
Go to Solution.
Attachments:
additional_installers.JPG ‏87 KB
activate.jpg ‏25 KB

Thanks for the suggestion but I solved the problem a different way. I downloaded NI-VISA Run-time 4.3 from http://joule.ni.com/nidu/cds/view/p/id/989/lang/en then extracted it to a folder. I pointed Project Explorer to this folder and it found it properly.
I was then able to build the project successfully.
Sidd

Can't find Application Builder after installing AB 7.0 in a LabView 7.1 system

Hello, I just installed applivcation Builder 7.0 on my windows desktop (XP, SP2) that has already installed a Labview 7.1. But nothing happens...I just can't find it. Not on "Werkzeuge" (Tools) or anywhere else in the application.
Only in the explorerI can find Labview7.0\Applibs...
I reinstalled it 3 times now...what else can I do ?
or does the Application Builder 7.0 not work with LV 7.1 ?
any help would be appreciated
regards
fluxgate

No, it does not work. You need the 7.1 app builder. If you had purchased the 7.0 app builder separately (and not as part of the profession version), when you did the upgrade to 7.1, you should have requested the 7.1 app builder. Since 7.1 is no longer sold by NI, I'm not sure how you can get the correct app builder. You should contact NI directly or your local field engineer.

Creating Folder stucture Application Builder

Dear Friends,
I was intending to populate a specific folder structure inside the BUILD folder as shown in figure. But after a lots of combination unable to find what I was looking for.
Please refer the figure and do suggest me if, there is any methods / tricks to achieve my goal.
Assumptions:
All Vis Should be Always Included into the Build Specification.
All Vis contains SubVIs and Vilib Vis.
Thanks
Sri

I don't understand what you are trying to do. I think you are trying to build an Executable from a LabVIEW Project that is organized as a set of Folders inside a Top Level Folder.
If that is correct, then you should not try to replicate your folder structure in the Build! The structure of a Build is a single folder that holds the Application (the .exe file that results from compiling and linking together all of the LabVIEW VIs and support VIs referenced by your Project) and giving you a single file (My Application.exe). It also provides a few Configuration files (My Application.ini and My Application.aliases) in the same Folder, and might have a Data sub-folder where files that "need to be available", but might not be directly linked by the Builder, are located. Most of my Executables just have the three .exe, .ini, and .aliases files present.
When you build the executable on your own PC, it links to the LabVIEW library routines whose locations it already knows (they're usually in Program Files\National Instrument\LabVIEW 20xx or similarly-named folders). If you want to run this code on another PC that does not have the LabVIEW Run Time Library installed, you can create an "Installer" that will package up the additional files and create something that, when you run it, will "install" the Run Time Libraries and the Application.
I've only rarely done this (and, I confess, not recently) -- it can be a little messy. I'm not delivering to Customers, but rather providing routines to Students, so it's a little more "hands on". What I've done is to provide the Build (meaning the folder containing My Application and its supporting files), which they can copy to their PCs or just run directly from a Share, and also pointed them to an Executable that will install the appropriate LabVIEW Run Time Engine on their PC. We've "standardized" on LabVIEW 2014 (for now), so everyone has the RTE installed, and only needs to pick up the latest Executable.
Hmm, are you trying to do a Source Distribution? If I've gone off on an irrelevant tangent here, I apologize. Yes, if you are trying to distribute the Source, then you may want to keep track of the existing file structure. [How embarrassing if I've been ranting away on the wrong issue ... I'll go away, now ...]
Bob Schor

"Find Resources" does not work after Application Builder Installer

I use Lv Full 6.1 / Appl.Builder 6.1
VISA:"Find Resources" acts properly as long as a built application is installed on a PC that has LV installed.
as soon as only the runtime eng. is installed no resources are found.
Who helps?

Thank you Dennis for your reply. I tried to install the VISA runtime engine via the "Run executable after installation" but it appears to run the Visa-runtime-engine-installer before ending the application installation. So I had to run that installer manually. Nevertheless you pushed me in the right direction.
THANKS

Can visa runtime engine be included in application build?

Similar Messages

Maybe you are looking for