What is Run Time engine 5.1.1?

I came across on our network a Runtime engine 5.1.1 program for LabView??, Can anyone tell me what this does or can do?

The LabVIEW Run-time engine (RTE) is needed for compiled LabVIEW exes to run. So if you have any applications (exes) written in LabVIEW 5.1.1 then the RTE would need to be installed on the machine that uses those exes.
It basically consists of the shared primative functions in LabVIEW as well as the code needed to actually run the LabVIEW exes. The LabVIEW RTE is similiar in behavior as other languages RTEs.
Message Edited by Evan on 02-24-2006 10:18 AM

Similar Messages

What's the cost of Labwindows run time engine

Dear Sir,
I have some questions about CVI and hope you can help me figure it out as usual.
1st, what's the advantage of labwindows against Labview? I know one is C programing environment and the other graphical environment. But the Labview seems more user-friendly.
2nd, What is run-time engine according to your definition? I know Matlab has similar component and is free of charge. Does the run time engine in Labwindows charge? If so, how much?
3rd, Previously, I thought labwindows is used to convert Labview program into C source code which is faster (how fast, compared with labview) and very popular in the industries, so companies do not have to buy labview and run it for just simple application in the field. But if the run time engine costs a lot, I can find no reason to use labwindows.
Thank you very much!

1) LabVIEW is a graphical based programming environment and
LabWindows/CVI is a C based programming environment. Both can be used
for similar tasks. Users familiar with C may prefer CVI. LabVIEW is
typically easier to learn if you are unfamiliar with both.
2)
The Run-Time Engine is a separate component that can be installed to
execute LabWindows/CVI programs and LabVIEW programs. It is free of
charge for both LabVIEW and LabWindows/CVI.
3)
LabWindows/CVI does not convert any LabVIEW programs into C code.
LabVIEW programs are already compiled as you write them, so you won't
need to convert them to C to use them. You should see similar
performance in similar LabVIEW and CVI code.
Allen P.
NI

Distribute application without labview run-time engine

I read a lot of post saying if the target machine has the same run-time engine installed, then I don't need to distribute the application with labview run-time engine. Somehow this rules doesn't work for me. I have a PC installed labview 2010 development system and has run-time engine 2011 SP1. I also download the same version of run-time engine and installed it in a target PC. When I distribute my labview application, if I select to include the run-time engine in build properties, the application will be able to install and run properly in the target machine; If I don't include the run-time engine, then I wouldn't be able to run the application.
Does anyone help me on this? I don't want to always build the application with the run-time engine since it's quite big
Solved!
Go to Solution.

Could you take a look at my NI software list and let me know what labview run-time engine is really in use?
And in build properties, it actually list addition installer include labview run time engine SP1. If I includes this version of run-time engine and run the installer in target machine, it will still install the run-time engines just like there is no run-time engine installed in the target machine before.
Attachments:
NI software.jpg ‏98 KB
Installer.jpg ‏216 KB

When creating an application installer in LV, what run-time engine or driver must be installed to install the VISA interactive control?

I've created an application installer using LabVIEW's application builder and use it to install NI MAX. However, after running the installer, the VISA interactive control is disabled in NI MAX.
The installer installs the following NI components: NI LabVIEW Run-Time 2014 SP-1(64-bit), NI LabWindows/CVI Shared Run-Time Engine 2013 SP2, NI Measurement & Automation Explorer 14.5, NI-488.2 Application Development Support (includes run-time), NI-VISA Configuration Support 14.0.1, NI-VISA Runtime 14.0.1, NI-VISA Server 14.0, NI Systems Configuration Runtime 14.5.0, vision run-time, dc-power run-time.
If I download and run the 488.2 installer, the VISA interactive control is enabled in NI MAX. But, the installer created with the application builder does not seem to install the necessary components.
What needs to be added to the installer to enable the VISA interactive control (VISAIC)?
Thanks.
Solved!
Go to Solution.

From Pedro Munoz, Applications Engineer, National Instruments
Sorry for the confusion with the forum post that Jon sent you. I did some research on our internal database and I found out the component will not be installed by any of the components added from the additional installers section on the configuration of the installer. As you have already found out you need to install the full installer in order to enable this feature.
I know that this might be an inconvenient for you because you wanted to have one installer to run. On this case may I suggest using the NI Batch Installer Builder.
The NI Batch Installer Builder allows building installers that contain National Instruments software from several products. That way you can create an installer for you application in LabVIEW (and not include the drivers in the additional installer section), then use NI Batch Installer Builder to include the installer for your application and the full version of the drivers that you mentioned.
Here is the download link:
http://www.ni.com/download/ni-batch-installer-builder-14.5/5193/en/
And in here you can find instructions on how to get started with it:
http://zone.ni.com/reference/en-XX/help/374206A-01/
Let me know if you have any question.
Regards
Pedro Munoz
Applications Engineer
National Instruments
http://www.ni.com/support

What is "LabVIEW Run Time Engine"?

I'm trying to find the differences between two computers that I'm troubleshooting. One of them is my development system which has the whole Development Suite installed, and the other is a test station which has LabVIEW 8.0 Evaluation Version installed. When I was looking through the list of programs in my development system (in Add/Remove Programs), I found a program named "LabVIEW Run Time Engine" and the size is 0.11 MB that is not in my test station. I thought all the NI components are installed under "National Instruments Software" including the Run Time Engine...
Does anyone knows what this is?
See-Ming

The Run Time Engine is a library of routines that a compiled Labview program needs to run on a system that doesn't have the development environment. It is similar to Visual Basic's vbrun.dll, which compiled VB programs need to run.
As far as I know, the run time engine gets installed whenever you install any Labview development environment. This engine is usually only necessary when running a Labview program compiled to an exe format. Both the exe and the run time engine can be installed on another computer so that the program can run without having to buy another development package for that computer.
The runtime engine is called LVRT.DLL. Search for it. For version 7.1, the run time engine is in C:\Program Files\National Instruments\shared\LabVIEW Run-Time\7.1\lvrt.dll
- tbob
Inventor of the WORM Global

Unable to run vi with labview run time engine

Hi All,
I have a VI that controls and reads from an NI PXI Spectrum Analyser (5600). The VI works perfectly as expected, I can make a project of it and create a runtime application and installation with no problems, using Labview 8.6.
When I make a call to it from Test Stand 4.1 it works lovely.
When I change the VI adaptor in Test Stand 4.1 from development to use the LV Run Time engine 8.6 it fails to work, Test Stand gives the following dialogue (see attached).
I have uninstalled all older versions of Labview as I've had similair issues before, I've mass compiled everything I think is associated with this VI.
I don't really understand! And am tearing my hair out.
The only idea I have is that perhaps there is something in one of the 5 DLLs that is causing a problem or the NI_AALBase.lvlib, NIAALPro.lvlib or NI_PtbyPt.lvlib librarys that are password locked and I presume don't get mass compiled.
I have attached the problemVI.lvproj.
Thanks for any advice or help.
Matt
Attachments:
problem VI.lvproj ‏41 KB
teststand.JPG ‏43 KB

Matt,
it sounds like you are having older versions of toolkit/driver VIs in your application. In developement environment, this works since the dev-system is capable to recompile older VIs just during loading and therefor not having issues with older versions.
Running the VIs using the Runtime Engine, recompilation is not possible. Because every VI knows "its version", the VI will not be executable unless the RTE version matches the VI's. If the VI is older (or newer, doesn't matter), the observed error occurs.
Please make sure that you have current versions of drivers and toolkits installed in your LV environment instead of simply copy them from older versions of LV (this would be the common source for such issues).
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

VISA Write differs between TS Development System and LV Run-Time Engine

Hi all
I made an application on LabVIEW to test BERs (Bit Error Rates), and I used VISA Write between two COM ports to exchange data.
Everything works fine using just LabVIEW.
Afterwards, I used TestStand to call my application (VI). The LabVIEW adapters from TestStand were set to Development System by default, and everything works OK!!
Finally, I needed to disable the development system, and set the LabVIEW adapters from TestStand to LabVIEW Run-Time Engine and I notice that the speed of the data exchange between the two COM ports decreased dramatically.
The only difference was the speed...because all the data (changed slowly in this case) arrived correctly on the other COM port too.
The symptom was the same as decreasing the baud rate...but the baud rate and all the other configurations remained the same. The only difference was the change between Develpment System to Run-Time Engine to notice this decreased speed between the exchanged data using VISA Write.
Any solutions for this?
Thanks in advance
Joao
Solved!
Go to Solution.

Joao,
you state that using the LV Developement System as execution platform for your LV code modules result in faster datatransfer between the COM ports than using the LV Run-Time Engine.
So i am pondering: Does this refer to TS at all?
Please check the following:
Run you communication using a sole LV application in LV Developement System. This should be fast. Now build an executable of this application and run that one. Do you see the same behavior?
If there is no difference in a sole LV approach, there have to be some settings in the TS approach making this slow. So please let us know:
Are there different modules involved in that data transfer (which in fact points to the reply Christophe made)?
What about loading/unloading options of the modules?
How big is the hierarchy of the modules, e.g. is it necessary for the RTE to load stuff the Dev Env has already in memory due to loading a lvproj.......?
Could you provide a simple example sequence+modules showing this behavior?
What versions of LV and TS are you using?
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Executable not working - Looking for LabVIEW Run-Time Engine

This has been one of those days.
I'm trying to create my .exe file to place onto another computer. I've done this before with success. But that was then and this is now.
I believe I have all the files I need in my LLB, and I believe I did my application distribution correctly and I believe I built the DLL correctly. But when I took the resulting .exe file and placed it on another computer and attempted to run it, it gave me the error message: "Unable to locate LabVIEW Run-Time Engine. Program requires a version 7.1 (or compatible) LabVIEW Run-Time engine. You should have already realized this, you moron."
Anyone have any idea where I went wrong or what step I might have missed? This has been a crazy, non-stop, massive brain fart of a day and I can't seem to remember what I'm missing here.
Amateur programmer for over 10 years!

Hi.
Whenever you want to use executables or .dll's created with LabVIEW you must make sure that the LabVIEW runtime engine of the SAME version as the LabVIEW version used to create the files, is installed in the target computer.
There are basically 2 ways to get the run-time engine installed on a computer:
1. (the one I prefer): Download the correct version of the LabVIEW run-time engine installer from www.ni.com/downloads, or more specifically from
http://digital.ni.com/softlib.nsf/websearch/369618104E25B08E86256F54006A4E2F?opendocument&node=132050_US
for the latest one. Once you have the installer for the run-time engine, just install it in the target computer. I prefer this option because the run-time engine is installed independently, so if you then uninstall your program, the run-time engine remains.
2. Create an installer for your program that includes the run-time engine. To include the run-time engine, when you are creating your application, go to the "installer settings" tab, click on "Advanced" and make sure there is a checkmark on "include LabVIEW run-time engine". This way when you install your program in the target computer, the run-time engine will also be installed.
Just as a note, any computer with LabVIEW on it, will also have the run-time engine.
Good luck.
Alejandro

Unable to locate the LabVIEW Run-Time engine

Using LabVIEW 2011, I have built an executable and installer including the LabVIEW Run-Time engine. I built the app on a 32-bit system. I'm deploying it to a Windows7 64-bit system. When I ran the installer, rebooted, then tried to run the app, I got an error messsage stating "Unable to locate LabVIEW Run-Time Engine", stating that the LVRTE 2011 was needed to run the app, and asking if I want to download from NI. I have tried downloading the RTE and re-installing it, but when I try, I get an error message from the installer stating that there is a newer version of the RTE already installed, and the installer exits! I have tried un-installing the application, but have had no luck removing the RTE. Now I'm stuck. The re-installed executable application says it can't find the RTE, and the RTE installer says there's a later version already installed!
I can't go forward or backwards!
Prior to running the installer for this app, I had a working LVRTE for 2011, and was running some other executable LabVIEW programs on the target box. However, since this new application had additional components not included in the original install of the RTE, I built the new installer which included the additional components. Once I ran that installer, my problems began.
In my frustration, I've tried downloading from NI both the 32 and 64-bit versions of the RTE, and installing them. I realize that the app was built on a 32-bit system, so the 32-bit RTE SHOULD have run it fine, but didn't.
At this point I have removed the 64-bit RTE using the NIUninstaller. I believe I need to completely remove all 32-bit RTE components and start over, but I have not been able to. The 32-bit RTE does not show up in any un-install utilities I've found.
What could be causing this problem, and how do I get past it??
Thank you.

One thing I did discover in my struggles is that the RunTime engine on the target box needs to be based on the environment of the development box. So if you built the app on a 32-bit machine, you would need to install the 32-bit RTE, even on your 64-bit target box.
The RTE Uninstaller might not show up in the Windows Add/Remove Programs utility. In my case the 64-bit RTE uninstaller showed up, but the 32-bit did not. The NiUninstaller (C:\Program Files\National Instruments\Shared\NIUninstaller) did list both RTEs for uninstalling, but still didn't get me past the problem.
I was finally only able to get past the problem by doing a system restore to a point in time prior to my changing of the RTE.
Good luck.
Dan

Unable to locate labview run time engine (lab view 8.5)

Hello I have a problem whit the labview 8.5 installer. I have created I project with included a .vi file (a simple panel wich control a serial port, with parameters (baud rate, stop bits, ...)), then I have created an application for this file (.exe) and then the installer (I have included the labview run time engine 8.5). When I run the setup.exe I have the following error message:
Unable to locate labview run time engine, the application require a labview run time engine 8.5 or compatible...
What I'm missing??
Thanks
Maurizio

are there one other reasons why it would not work. I have asimilar problem.
I intsalled version 8 of run time engine and acrtivated software. Now I am trying to run compiled application provided to me by third party.
When I click on application it says
Unable to locate LV run time engine
Test server requires a version 6.0 or compatible LV engine.
How do I know if the engine I installed and activated is running and is it supposed to be able to execute a program which is expectin rev 6 of the rund engine?

Can't install LabVIEW Run-Time Engine 6.1 on Windows Terminal Server

With my system admin, we tried to install the LabVIEW Run-Time Engine 6.1 on our Windows Terminal Server NT4. And we get an error all the time:
-install using the plugin
-install using LVRTE.exe
-install after rebooting the server
But I remember that we could install the Run-Time Engine 6.0 on another Windows Terminal Server NT4.
Is there any compatibility issues with the new Run-Time Engine 6.1 ??
Thanks for your help
Cyrille

Cyrille,
What is the error that you get when trying to install the run-time engine?
Are you installing it from the LabVIEW CD, or did you download it from the web site?
To further troubleshoot this problem, it would be best if you send us an email to [email protected] and send the above information.
Also, try running the installer from the command prompt window, and use the following syntax:
setup.exe/l*v
This will save the error log to the file you specify. Send us also this file to help us troubleshoot.
Thanks
Zvezdana S.
National Instruments

LabVIEW VI with Report Generation Toolkit elements in a TestStand sequence does not run with a LabVIEW 8.5 Run-Time Engine

Hi all,
I am using LabVIEW 8.5.1 and TestStand 4.1. I have done a TestStand sequence with a VI in it, which uses Report Generation Toolkit elements. On my machine I am using LabVIEW and TestStand with a Development System license. On the other machine I am using TestStand with a Base Deployment license and I have chosen the LabVIEW 8.5 Run-Time Engine in the Adapter Configuration. Everything is running well except of this VI with Report Generation Toolkit elements. The error message is showing that the VI is not executable. It works well only after I have installed LabVIEW with an Evaluation license and chosen LabVIEW 8.5 Development System in the Adapter Configuration.
I have found other posts and a document in the KnowledgeBase with a similar problem: http://digital.ni.com/public.nsf/allkb/8A0E6274D9BD7B1986256F62006AD402?OpenDocument But I am not using EXE files in my sequence, so I don't know how to solve mine. Anybody has an idea?
Solved!
Go to Solution.

Hello guys,
thank you very much for your answers!
@Ruediger:
I tried to follow the instruction for Method 2 in the mentioned document: http://digital.ni.com/public.nsf/allkb/F3DC40A6E3F3B25B862570AD005D1D3D?OpenDocument, but the steps on my machine are different starting from step 4. After I click "Continue..." in step 3, I dont get a window, the system just makes a new folder with the same VI.
To be honest, I am new to LabVIEW and have some difficulties at this time. What I understood from your reply is, that I need to make a LLB-File, where the files from Report Generation Toolkit are in!?
@GovBob:
I was following the instruction in the document: http://digital.ni.com/public.nsf/allkb/9E00E7EFE0635E678625734600779EFE, but it wasnt working. Can you please tell me how I can check if the VI Server is installed and running on the machine?
I am using LabVIEW 8.5.1 and TestStand 4.1 on my machine, on the deploy machine there is TestStand 4.1.1. The version of my Report Generation Toolkit is 1.1.2.
Kind regards, Roman

NI LabVIEW Run-Time Engine + TCP/IP

Hello, Anybody knows how to activate TCP/IP service on PC with standard NI LabView Run-Time Engine installed. If I trying communicate with server from my PC (LVRTE) its works correctly. However, when I am trying interchange client and server applications it appears with error 1. Probably I need to add some settings to *.ini files on PC with LVRTE? --- Alex

<Alex> wrote:
Client/Server applications are communicate via standard TCP/IP VIs. I have tried to add 3 line as you wrote to server.ini, but it's didn't help
As I indicated, the lines are only applicable to using the VI Server. You had not indicated whether you were using the VI Server or just the TCP/IP VIs. At this point we need a better explanation of what you're doing. Specifically:
What does this: "If I trying communicate with server from my PC (LVRTE) its works correctly." mean? What is the "server"? What's it running? What do you mean by your "PC (LVRTE)"?
What does this: "However, when I am trying interchange client and server applications it appears with error 1" mean? What is the "interchange client" and the "server applications". Reading this implies you have more than one application running on the "server", whatever that is.
Seeing some code wouldn't hurt either.

NI-LabVIEW run-time engine interop 2010 failed to install

Hi,
While installing Labview 2010 (32 bit) I got an error message:
NI-LabVIEW run-time engine interop 2010 installation has failed with the following error:
Error 1935. .... (see the .ppt for screenshot if interested)... HRESULT 0x8002802F
I googled HRESULT 0x8002802F and found a page that said that this error is usually b/c of a missing/corrupt entry in the registry: file %windir%\system32\mscoree.dll, and that "repairing the highest version of the .NET Framework on the system will correct any problems resulting from this error."
I have verified that mscoree.dll is not present, and I don't have the .NET Framework installed on my system. SO, I have the following questions:
1) do you concur with the advice given on the page referenced re: the reason for the error;
2) If so, should I install .NET Framework, and what do I then need to do in LabVIEW to tell it that the .dll is now present?
3) If your opinion is other, what do you advise?
Cheers
Attachments:
Labview Installation error.ppt ‏227 KB

Hi Luke,
After doing some research, there are two possible solutions.
1) According to a KB, it could be your antivirus. You may want to try to turn off any spyware blocking software such as Ad-Aware, Norton, etc and try the installation again.
2) Another customer had the same error, and they got it working by installing .NET 3.5 from Microsoft's website and then installing LabVIEW again.
Hope one of those options work for you!

MAX giving error - Unable to locate Labview run-time engine

I have LV 7.1 and 8.5.1 installed on a WinXP pc. No problems until now.
I installed some support software for a LabJack interface, which required LV version 6.1 run-time, so I let it install that.
I now get the error whenever I run MAX:
"Unable to locate the Labview run-time engine. LVBrokerAux71 requires a version 7.1 (or compatible) Labview run-time engine...."
After closing the error boxes, MAX seems to work fine. Both versions of Labview also work. I uninstalled run-time engine 6.1 and re-installed version 8.5.1, but that made no difference. I tried to install run-time version 7.1 from the msi file but it would not let me because a later version of the run-time is installed.
What is LV Broker? Why does it not accept version 8.5.1 run-time engine? Is it possible to have 2 versions of the run-time engine installed, and if so, how?

Dear CDancer
Thank you for contacting NI. First of all, you can have as many versions of LabVIEW run time engines you want loaded on your computer without a problem. LV Broker is installed by all drivers that uses LabVIEW testpanels like DAQmx does. In your case it seems that the LV Broker installation is corrupted or has failed. This can be rectified by overwriting the files in the specified directory listed below:
C:\Program Files\National Instruments\Shared\LabVIEW Broker
Your directory should look like the screenshot I have attached; labelled LV Broker Directory View
I have attached a ZIP File that will replace the LV Broker directory. Please try replacing your files with these if different to the screenshot and let me know how you get on. Many thanks.
Many thanks for using the NI forums and I look forward to your reply.
Kind regards
David
Applications Engineer
National Instruments UK
Attachments:
LV Broker Directory View.JPG ‏57 KB
LV Broker.zip ‏413 KB

What is Run Time engine 5.1.1?

Similar Messages

Maybe you are looking for