Why Runtime Engine is required?

Hi,
I want to know what is LabVIEW runtime engine exactly? Whay is it required? What exactly is it's role?
Where can I find the answers of these questions? I searched on this site but couldn't able to locate a single document .
Thanks!
Solved!
Go to Solution.

LabVIEW is not different to many other programming tools in that is it modular. Look at your computer, I am sure you have e g flash player installed. Would you really prefer if the entire player code would need to be included and downloaded with every tiny web flash application? How about the visual basic runtime? How about Java runtime? Having a runtime is the standard way to do things.
Sure you could place everything inside each executable, and that's how it was actually done in the good old LabVIEW 4.0 days, where the simplest LabVIEW executable (e.g. to add two numbers) was several Megabytes in size (old discussion). Now, since we have the runtime, a LabVIEW executable can be very small.
It makes perfect sense to include all common code into a few DLLs that can be installed once and shared by all LabVIEW executables. Do you really think it would make sense if all 20 LabVIEW programs installed on a computer had their own copy of the core FFT algorithm? One shared copy is enough!  As soon as you have more than one LabVIEW application installed, the savings are gigantic. What if a bug is discovered. Would you rather patch 20 different program or simply update the runtime engine?
Long ago, the same discussion came up and I have writteen a more detailed reply here
LabVIEW Champion . Do more with less code and in less time .

Similar Messages

  • 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

  • Labview runtime engine

    Hello Guys,
    i am in a bit of confusion when it comes to utilisation of runtime engines.
    I have several programs which requires older runtime engines, i.e. 6.1. on my computer runtime 7.1 is installed, and seems to be incompatible with the program.
    Do i need to install a runtime for every version dependant on the shipped program? where do i find old runtime engines (i need now 6.1).
    Why cant i keep only the latest runtime?
    related question: i received vis from a 7.1 version, while i run on this machine 8.0 (yes, the buggy one ). however there is an error opening the files, LV claims that the vi could not be converted since it has no diagram! what does that mean?
    Thanks!
    ... And here's where I keep assorted lengths of wires...

    Gabi1 wrote:
    [...] however there is an error opening the files, LV claims that the vi could not be converted since it has no diagram! what does that mean? [...]
    Since you have to recompile the VI for the "new" version, you need the sourcecode. And in LV, the BD is the uncompiled sourcecode. So, if you have no BD or it is blocked by any means, you cannot recompile this VI.
    And regarding the RTEs:
    LV is not the only environment which needs a RTE. In fact, all programms need a RTE. It is only common, that many programming languages compile their applications in a way, the components of the OS work as RTE (this is true for e.g. ANSI C).
    Other languages have their own RTEs, the most known example would be .NET where the .NET framework is the RTE. And just like LV, there are different versions of the .NET framework (1.0, 1.1, 2.0). And not all .NET assemblies can be executed with all framework-versions. So version-dependend applications are not as uncommon as some people might think.....
    Norbert
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • Runtime Engine Distribution Licensing (Legal) Issues?

    Hi Everyone,
    I need an official word from National Instruments on this one.
    I've written a program using LabVIEW that I would like to distribute to the public.  It runs in conjunction with a C#-based executable and is installed using the C# program's installer.  Is there any legal/licensing problem with including the LabVIEW Runtime Engine installer with the C# program's installer?
    Thanks!
    -Yohan
    Solved!
    Go to Solution.

    Hi Yohan,
    Thanks for your post and I hope your well.
    You can distribute LabVIEW executables freely. There is no need of a license to run executables that only require the Runtime Engine. Other modules such as Real Time do require a Run-Time License. Please see this link for more details: Which Software Requires a Run-Time License?
     Can I ask more about your application - why do you require to distrubte these together?
    Hope this helps,
    Kind Regards
    James Hillman
    Applications Engineer 2008 to 2009 National Instruments UK & Ireland
    Loughborough University UK - 2006 to 2011
    Remember Kudos those who help!

  • 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.&nbsp; 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).&nbsp; I thought the original duscussion was about running a VI from one platform on another without requiring the development environment to re-compile.&nbsp;
    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.&nbsp; Not that I agree, I just understand Further, I believe the run-time is required to prevent each and every LV application being huge.&nbsp; 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.

  • Small runtime engine for newer labview versions?

    A few times in the past I have created simple LabVIEW standalone executibles.  I did this in 8.6 and used the runtime engine minimal installer instead of the full version.  This resulted in an installation package size of 30-35 Meg.  
    I agin need to create a simple executible but have not seen a minimum runtime installer for any LabVIEW version since 8.6 
    Are there any minimal runtimes for other versions? 
    The default 2014 runtime is 264 Meg!!!  It is hard to explain to a customer why a simple "Hello World" program requires a 200+ Meg download.
    Solved!
    Go to Solution.

    Jack Dunaway has documented a way of segmenting the run time engine, basically only including the pieces of it you need.
    https://connect.wirebirdlabs.com/knowledgebase/articles/172999-segmenting-the-run-time-engine
    And here is an idea exchange item on it.
    http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Segment-the-LabVIEW-Run-Time-Engine-RTE-to-ONLY-Necess...
    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.

  • LabVIEW Runtime Engine 2010 NI_AALPro Error

    Hi All,
    I have an problem with the executable version of my LabVIEW program. I just created an LabVIEW program in LabVIEW Professional 2010 version to acquire some FFT spectrums so it also use some function palettes of Sound and Vibrations toolkit like Power Spectrum, Peak Search, Power in Band etc.
    Then I just created an executable version of the program to run on a different system (Tools>>Build Executable Verion(EXE)). But when I tried to run the executable verion on a different system is showed some errors. I am attaching a printscreen of all errors showed.
    So, the executable version of the program is working fine in the develoment system but showed some errors when we try to run it on a different system. We have already installed the LabVIEW runtime engine 2010 as well in the second system.
    My one more question is when we build an executable version of a LabVIEW program then it should run on all PC without any other software (Runtime engine) because it got an extension of .exe 
    so is there any chance or way to build a totally standalone executable version of the program without using any runtime engine as well.
    Thanks
    Attachments:
    error.JPG ‏28 KB
    dll & lvlib.JPG ‏41 KB

    Hi PSBRRR,
    It seems like you didn't include all the dependencies of your VI or project to your build specification. Can you send a screenshot of  the Source Files Setting page of the Application Properties dialog box ? You have to add all the VIs and DLLs that are used in the Sound & Vibration toolkit and any others you are using to your executable file or support directory.
    For the last question : no you can't. Since LabVIEW 2010, the Run-Time Engine is like the "Java Virtual Machine". The compiled code inside your EXE is interpreted by the "LabVIEW Virtual Machine" included in the LabVIEW Run-Time Engine. That's why it requires the Run-Time Engine to be executed or at least the development environment (previous versions of LabVIEW didn't use this principle but it was also required to have the Run-Time Engine installed).
    Regards,
    Da Helmut

  • Unable to install LV Runtime Engine 7.1.1 with LabVIEW Professional 8.5.1

    I installed LabVIEW Professional Sys. for Windows (XP) 8.5 and then the 8.5.1 update. Somewhere in the original installation, LV Run-time Engine 7.1 was installed. But I need LV RTE 7.1.1. So I attempted to install RTE 7.1.1. Problem: The LV RTE installer aborts with the following message:
    "Installation aborted. Newer version already installed." 
    Why do I need 7.1.1? I must run some commercial LV executables that were compiled with LV 7.1.1 and will not run under 7.1.

    Well, I have to correct myself. MAX indicated that LV RTE 7.1 (not 7.1.1) was installed. My complied LV app indicated that 7.1.1 was not installed. I checked Windows Add New Programs and selected "National Instruments Software" I found that LV RTE 7.1.1 was, in fact, installed. So I selected LabVIEW Runtime Engine 7.1.1 and clicked Repair. After rebooting, My app works correctly. Again, MAX incorrectly displays LV RTE 7.1 (not 7.1.1). My app works, so I don't care.

  • 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

  • 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

  • Call a sequence of VIs (not .exe)) in VB. only LV runtime engine Installed

    I am try to reuse my labview vis in VB enviroment. I would like to call a sequecne of vi from VB just like in LV with Call By Reference. This is a production enviroment, only Labview runtime engine installed in the computer. I realize that I can call labview exe file from VB, but then I have to compile every vis (more than hundreds) and have to reference every vis servers in VB.

    Actually, the runtime engine can run any VI--not just ones built into an application. The problem will be getting data in and out of the functions.
    If you have much of the code already written in LV why are you messing around with VB? Wouldn't the easiest solution be to write the entire application in LV? Just wondering.
    Mike...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • VISA runtime min system requirements

    I have a Windows application written in LabView that includes comms.  I have bundled the VISA and Labview runtime engines with the installer which works.  I'm now trying to write the user manual and need to define the minimum system requirements.
    I've found the LV RT system requirements but can't find the VISA ones.  Can anyone point me in the right direction?
    Thanks

    The system requirements for the LabVIEW Runtime would be the relevant requirements here. If you want to see the supported platforms, then the VISA Readme contains that information. If you cannot find it on disk, then you can go to the download page for your version of VISA and the ReadMe will be available there.

  • 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!

  • Unable to determine the install root path for the LabVIEW Runtime Engine

    Hi,
    i have an issue with using a LabVIEW interop assembly in a .NET application. I get an exception "Unable to determine the install root path for the LabVIEW Runtime Engine" when calling the assembly.
    The little test program is attached below. It's called dotNETHost.exe. If you excecute the programm a dialog with an button appears. Clicking the button shall open another dialog (the LabVIEW Interop component). But the only thing I get is the exception message. The ZIP folder also contains the complete exception meassage (ExceptionMessange.jpg & ExceptionDetails.txt).
    The Interop Assembly was built with LabVIEW 2011. We use Visual Studio 2010 and .NET 4.0.. The dotNETHost.exe.config file is prepared as mentioned in Knowledge base - Loading .NET 4.0 assemblies.
    The Interop assembly contains only one simple dialog (loop is finished by clicking OK) without calling any other VIs or other DLL's.  In case of this there's also no support directory generated by the build process.
    I have no idea why it doesn' work. I hope anyone can help me.
    Thanks in advance
    Kay
    Attachments:
    Debug.zip ‏75 KB

    This may be unrelated, but Labview and .Net4.0 dont work well together. Not yet anyway. I had to compile my assembly in 3.5 to get it to work.
    Please read the following:
    http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/configuring_clr_version/
    http://digital.ni.com/public.nsf/allkb/32B0BA28A72AA87D8625782600737DE9
    http://digital.ni.com/public.nsf/allkb/2030D78CFB2F0ADA86257718006362A3?OpenDocument
    Beginner? Try LabVIEW Basics
    Sharing bits of code? Try Snippets or LAVA Code Capture Tool
    Have you tried Quick Drop?, Visit QD Community.

  • Runtime engine huge issue

    Hi,
    I have a very big issue with the labview runtime engine.
    I use the print at completion mode for a VI and it seems the runtime engine doesn't support either the PNG compression property or the Scale frontpanel property. Which one I still need to find out.
    The executable says that arg 3 of my property node is not supported.
    Now, this is killing for my application as I can not use the application without this feature.
    If someone has an idea, please let me know. I'm under high time pressure and really have no other choice than to distribute a complete development setup if I can't solve the issue.
    Regards,
    Marcel

    Remember that PNG is a lossless bitmap image. There is some compression but it is a lossless compression so there isn't a setting for level of compression. I think that there are some differences in compression algorithms but the difference is minor and only useful if you have particular images that compress better than others. There is only 1 compression type which is zlib, but there are filters that can be applied before compression:
    Compression
    Filters
    PNG can be completely implemented with opensource free software and the specification is patent and royalty free. I don't know why the "compression type" needs to be specified for PNG.
    -Scott

Maybe you are looking for