What is runtime engine?

What is a runtime engine for CVI or TestStand? What is the structure of a runtime engine?

See the following link to the answer to this post:
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=137&HOID=50650000000500000015760100&HIsQuestionPoster=No&HTHREAD=000095765&UCATEGORY_0=_8_&UCATEGORY_S=0

Similar Messages

What is needed to run a .llb file using a runtime engine?

I would like to run a .llb file on a computer that doesn't have LabVIEW installed. Is that possible? If so, what is needed to do that? I have tried to install a runtime engine, but can't get it to work. The .llb file is currently running on LabVIEW version 6.0 on another computer, but I don't know with what version of LabVIEW the .llb file was created. The computer on which I would like to run the .llb file has Windows XP.
Thank you for any help!

Mathan wrote:
You have to create an executable with the help of project explorer.
The user has LabVIEW 6 (as he noted in the original message). LabVIEW 6 has no project explorer.
To OP: I am assuming the LLB contains a top-level VI that can be run. Otherwise, this is a moot question. If you want to open the VI and view it, then you need the development version on the target machine. If you want to run the top-level VI in the LLB then you must create an application that you can copy over to the other computer. The other computer requires the LabVIEW Runtime Engine in order to run the executable. To build the application you need the Application Builder. This is a separate product from LabVIEW, but was included with certain LabVIEW editions.. If you do not see a menu option for building the application then you do not have the Application Builder. You would need to contact your local NI sales office to see if you can still buy a copy. I doubt you will be able to, but it's worth a try.
EDIT: Sorry for the duplicate info. I got sidetracked while composing the message, and did not see the additional responses from Dennis.
Message Edited by smercurio_fc on 08-18-2009 09:51 AM

Computer with labview runtime engine (v8.2) cannot find sub-VI NI_AALBase.lvlib:Mean.vi. What do I have to do?

I am trying to run an exectutable on a computer that has the labview v8.2 runtime engine. The error I am getting is: Cannot find sub-VI NI_AALBase.lvlib:Mean.vi. What is the easiest solution?

the matrix,
I would try reinstalling the LabVIEW 8.2 Run-Time Engine. You may also want to try creating a very simple project in your development environment that has a VI with just the Mean.vi, try building an executable and then running it on the machine that just has the 8.2 RTE.
Doug M
Applications Engineer
National Instruments
For those unfamiliar with NBC's The Office, my icon is NOT a picture of me

What does the RunTime engine support?

Hello,
Does anyone know what functions the RunTime engine supports? Or is there a
NI link I can follow. Some goodies like the VI server don't seem to be
supported in RTE 5.1.
6i any different?
Thanks
Martin

I know about the paths, but I had problems with getting the username with
the Open application reference, an error came up 'function not supported'
and a pointer to the VI that caused it.
It's my mistake to say the VI server was not included. But are the
Application properties (web etc) included ?
Thanks
Martin
"Dennis Knutson" wrote in message
news:[email protected]..
>
> I use VI server with the run time engine all the time. When you build an
app,
> you have to specify which vi's are called dynamically so that they are
included.
> Paths parse out a little differently too when you've got a built app.
Sometimes,
> all it takes is an extra Strip Path.
>
> "Martin E" wrote:
> >Hello,>>Does
anyone know what functions the RunTime engine supports? Or
> is there a>NI link I can follow. Some goodies like the VI server don't
> seem to be>supported in RTE 5.1.>6i any different?>>>Thanks>Martin>>

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!

Runtime engine 8.6.1 on Labview 11

Hello,
I have upgraded labview 10 to Lv 11. A program that used to work on Lv 10 is giving problems now. It asks for runtime engine 8.6 ( usually gets stucked preparing the installation ). Once i cancel this process, it loads all the vi's, and it seems to work, but I can't be sure until all the devices are connected, and it can't be done until september. My question is, do i really need to install runtime engine 8.6 to make it work properly, or it can work without it?
And if I downgrade to Labview 10, will i solve this issue??
Thanks in advance!!

This is actually strange behavior because the runtime engine 8.6.1, if it is installed on the computer, should be accesible both from LV2011 and from LV2010.
What do you mean by "downgrade to LabVIEW 2010? You may have multiple version of LabVIEW on the same computer. Did you uninstall LV2010 first? If you did, then it may happened that you uninstalled the runtime engine 8.6 at the same time.
Do you really need or don't need the engine depends of your application. In any case, it should not be a problem to download the runtime engine from ni.com and install it. http://joule.ni.com/nidu/cds/view/p/id/1244/lang/en
Sergey Kolbunov
CLA, CTD

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

How do CVI7.0 runtime engine and TestStand3.0 runtime engine work in a test system?

I developed code modules from CVI 7.0, and test sequence from TestStand 3.0. Now I want to deploy all to a test system. Should I create distribution kits for CVI and TestStand, and install to a target PC? Do each kit include the RTE? How do the runtime engine work in a system?

hp7550,
I saw your post earlier entitled "what is a run-time engine?". It looks like this post is addressing the same issue.
To answer your questions, it is not necessary to create a distribution kit for your CVI code modules. You can simply install the CVI Run-time Engine, which you can find if you go to www.ni.com and click on the Drivers and Updates link on the left-hand side.
Then you will need to deploy your TestStand system using Tools >> Deploy TestStand System in the Sequence Editor. That tool will go out and gather all the CVI code modules your sequence calls - unless you are calling a DLL or something dynamically inside of a code module; in which case, you need to add that dynamically called DLL (or code module) to your TestStand workspace.
To install the TestStand Run-time Engine, make sure the Install TestStand Engine option is checked on the Installer Options tab of the deployment utility. You can customize what gets installed with the engine by clicking on the Engine Options.
For more information on deployment, see Chapter 14 of the TestStand Reference manual (Help >> Search the TestStand Bookshelf...).
To answer your last question a run-time engine simply gives you access to the compiled code that corresponds to the functions you used from the CVI or TestStand libraries during development.
I hope that helps.
Best Regards,
Matt P.
Applications Engineer
National Instruments

How to Detect LV runtime engine prior to showing Remote panel in browser?

I work on a web server that delivers remote panels embedded in browser windows. On new machines, the labview runtime engine needs to be downloaded and installed.
Currently, when a new user 'hits' the remote panel, the user is prompted and then downloads the component. However, the user experiences some errors that can be confusing. The first time, the remote panel is not embedded properly and the user must go 'BACK' then reload the page.
We would like to check and detect whether the LVRT engine is installed prior to posting a webpage that contains a remote panel.
What is the best way to detect whether the LVRT engine is installed on a remote computer?
Jim West

Jim West wrote:
My brain is swimming... I haven't had enough coffee this morning... There is a chicken and egg issue. As soon as I post the page, the client knows it needs to install the Labview runtime engine. However, my Labview process has already attempted to place the remote panel in the page. I get an error. I'll admit that I haven't delved into my software since there are two spawned processes involved. One process responds to the request and another lingers in memory running the remote panel until the user finishes.
From my perspective my lingering process should be sufficient to get the remote panel displayed when the RTE in finished installing but here is the catch. Installing the RTE requires a reboot, therefore the server process would need to linger in memory a long time and then would need to recoginize that a user from the same computer and login is looking for the page. Not really the way to go. I can't have a process on the server lingering waiting for a user to reboot his computer and then do something when they start running again. That process needs to die right away if the RTE is not available.
Jim
Would it be possible for this lingering process to check to see if the web server read has timed out? The default is 60 seconds, and you can change it by going to Tools>>Options>>Web Server: Configuration.
Trey B
Applications Engineering
National Instruments

Runtime engine files 8.2

Hi,
Since most users of my written program are users with "restricted right" acounts under Windows XP I copied the Runtime engine files of LV7.11 manualy by copying the
"Program Files\National Instruments\LabVIEW 7.1\Shared\LabVIEW Run-Time\7.1" files to the harddisk and run a build executable from that directory. Since this application looks in its own directory for support-files this worked fine for LV7.1.
Last week I converted my program to the LV8.2 version. When I tried to copy the RTE8.2 file in the same way as I did before, the program would start-up. It asks for a NIINI32.DLL file. When I include this file it does not return any errors, but the program doesn't start. Can anyone tell me whether their is a different way to run a exe-file build by LV-application builder by copying files manual in stead of running the RTE-installer?
Thanks in advance,

I know that NI did the run time engine to minimize space when installing multiple application. But i'm agree with you, we should have another way to build executable without the runtime engine. Some people dont know what it the runtime engine and uninstall it. afther that they just cant use the program anymore. The other reason, it that a VI use just some Kbyte and the run time engine that include almost everything, need some Mbyte.
If somebody know, please tell us......
Benoit Séguin
Software Designer

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

Make the installer for my executable run the DAqcarddriver and runtime engine installer automatically

*Hi
I would like to know how to make the installer for my executable run the DAqcarddriver and runtime engine installer automatically
I would like to include run time engine and the drivers of my daqcard(AI16XE50),( and maybe Ni daq or anything else needed?) in order to make my application portable for other computers on OS win98 and winXP .
How can I do that
thank you in advance
Olivier

Olivier,
What version of LabVIEW are you using to build your application? On a remote computer you should only need the drivers you are using and the Run-Time Engine. You can attach installers to LabVIEW 8 installers, but for previous versions you will have to add it by opening the installer configuration page, configuring your installer and then configure the Advanced properties. This will allow you to attach a EXE to the installer which you can run. Also depending on the version of LabVIEW will affect the OS version that you will be able to install the RTE on. LabVIEW 7.0 is the last version that can be installed on Windows 98.
Please let me know if you have any further questions and please include the version of LabVIEW you are using. Thanks!
Andy F.
National Instruments

App won't install with the prerequisite SAP Crystal Reports Runtime Engine

On installing with the following prerequisite checked:
SAP Crystal Reports Runtime Engine for .NET Framework 4.0
.. received this error:
Crystal Reports for .NET Framework 4.0\CRRuntime_32bit_13_0.msi
has changed since it was initially published.
Should I NOT use the prerequisite, and instead, use a merge module?

I ran a program with the exact same name, 2 weeks ago, on my VS 2010 Dev machine:
CRforVS_13_0.exe. (284 Meg)
Today, I followed your link, and downloaded the file with the same name, but different size: (1.5 Meg). I mean, a really major difference in size!
Because creating and testing installation packages is very time consuming, I want to verify what you have stated so that I completely understand before I change what currently works, which is for the client machine to separately install the CR runtime, to what you're proposing in including a prerequisite to my install package.
-> I should run this latest exe. It will add a prerequisite to the prerequisite list in Visual Studio 2010. The installation of this prerequisite will work, as the earlier one did not. And it will work for both 32- and 64-bit client machines.
Therefore, I can eliminate the need for the client machine to install the CR run time separately.
Please confirm, and then I will make the necessary changes, and do the install tests on client machines.
(Also, FYI the merge module did not work for me on a 32-bit client machine. So I removed it.)
Thanks, Peg

Can I extract the orginal VI's from an executable created by Runtime Engine?

I have an executable program created using the Labview Runtime engine and need to edit the subVI's contained within. Unfortunately, I don't have the original VI's the program was created with.
Is there any way I can extract those VI's?
Thanks,
Mike C.

First, LabVIEW 7.2 never existed.
Second, if you can't rename an exe into *.llb and open it in LabVIEW 7.1.1 (the latest official LabVIEW version before 8.0) and see a list of VIs then it's not a LabVIEW 7.1 or earlier executable file. What it may or may not be is another question!
But even if you can do that, all you can determine from this are the original VI names. Theoretically you can also copy the VIs out with the Librarian VIs, but those VIs lack all source code, front panel, and even icon resources so if you place them on a diagram, you see a simple block with a question mark, can't double click it to open the front panel and definitely can't view the diagram because they are all gone! And it even only works if the LabVIEW version that was used to create the executable is the same than the version you try to open those stripped VIs in, since the compiled (binary) code is about the only thing left in the VI and has to match the version of LabVIEW in order for LabVIEW to consider it valid. Anything else would certainly cause crashes as the compiled code would attempt to call into LabVIEW functions that have been added later on or got changed between versions.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Installer build wants wrong runtime engine

LabVIEW 8.6
Windows XP Pro
When I build the installer for my application, it wants me to have available the install disk from November 2007.
Expanding the list for that disk, I find that it wants the runtime engine for version 7.1.1.
If I remove NI-DMM 2.9 from the 'National Instruments Installers to Include' list in the Installer Properties, the error goes away. The description for that installer indicates it comes from the August 2008 device drivers disk.
At one time I had other versions of LV on the computer. I have removed all other versions, including the directories in c:\Program Files.
My application uses the DMM device driver, so I assume that I need to check the box for the additional installer. I've looked for more documentation on when and why I should select different items in the list, but couldn't find anything useful. Would it be possible for the installer to automatically select those items required and perhaps let me direct it otherwise by choosing fewer or more items?
Bottom line, do I need to select the DMM driver to ensure that my application will run on a computer that doesn't have LV installed?
- les

Hello all,
I couldn't really understand what was doing on in the above questions and answers but from the forum topic I believe I am in right place. I have an issue similar to those desscribed above. I have LabView 8.6.0 installed on my computer but when I run LabView it starts asking for 'NI LabView Runtime 7.1.1'. I tried feeding in the labview 8.6.0 but it doesn't accept it and keeps asking for 7.1.1.
The program used to run fine couple of months back and I then didn't use it for a while and I had other prgrams installed durig this time. And when this month I tried to use LabView it started giving me this trouble. I don't know what went wrong. I installed some ftdi chip drivers also. So, I am thinking if that kind of messed things up.
Also, I have this windows installer message come up sometimes which is not when I open LabView but some other programs. I don't know if this windows installer has to do anything with it.
Whatever the case it is could someone please help me figure out how I can get the right runtime work for my LabView 8.6 and if also possible how i can get rid of this windows installer message. I don't remember the error code right now because it comes up randomly. Next time I see it I am going to save that number. But in the meantime if anyone can help me with LabView 8.6. runtime engine problem.
Thanks,
Lovepreet

What is runtime engine?

Similar Messages

Maybe you are looking for