LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows - Supported Features

Hi,
Can some one please point out what features are supported by the LV RTE (Minimum ) [LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows]
1) Is there a limit on the size of the exe which can be run on it?
2) Will this support additional modules like DAQ etc.,? Or do we have to chose the regular installer ( 170 Mb ) for that purpose?
3) If a list of what it does or does not support is available, it would be extremely helpful.
Thanks In advance.
Regards,
Vijay

Anand, 
I did go through both the links that you had sent earlier before posting on the forum. For eaxample refer the following link where it says,
http://joule.ni.com/nidu/cds/view/p/lang/en/id/1599
It does not contain the full run-time engine, but will allow some executables to run.
1) What do they mean by 'some' executables. Is there a list of yay's and no's available?
2) Can someone from NI reply to this and shed more knowledge?
Regards,
Vijay 

Similar Messages

  • Announcement: LabWindows/CVI 2010 SP1 Run-Time Engine Updated

    A new version of the LabWindows/CVI 2010 SP1 Run-Time Engine (10.0.1.434) is now available for download. The new version includes Security Update 5Q5FJ4QW which resolves security vulnerabilities in components installed with LabWindows/CVI 2010 SP1 and earlier and LabVIEW 2011 and earlier. Further details can be found at KnowledgeBase Article 5Q5FJ4QW: How Does National Instruments Security Update 5Q5FJ4QW Affect Me? Installing the security update will have the same effect as installing the new version of the Run-Time Engine.
    The update can be downloaded from the Drivers and Updates page. The LabWindows/CVIRun-Time Engine is a free download.
    National Instruments
    Product Support Engineer

    The correct link should be this one
    Proud to use LW/CVI from 3.1 on.
    My contributions to the Developer Zone Community
    If I have helped you, why not giving me a kudos?

  • 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/8A0E6274D9B​D7B1986256F62006AD402?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/F3DC40A6E3F​3B25B862570AD005D1D3D?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/9E00E7EFE06​35E678625734600779EFE, 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

  • LabVIEW 8.0 Run Time Engine

    Hi,
    I've a question about LabVIEW 8.0 run time engine.
    I installed "LabVIEW_8.0_Runtime_Engine" from the NI website, but NI software in Add/Remove Programs does not list LabVIEW 8.0 Runtime Engine. However, LV 7.0 and 7.1.1 run time engines are listed in there. 
    Did anyone notice this?
    I also have installed TestStand 3.5 on the same computer.
    When I run an executable created in LabVIEW 8.0, I get the error message:
    "VI version is too early to convert to the current LabVIEW version" 
    Comments/suggestions are appreciated.
    Thanks.

    CarlaU wrote:
    The first thing that I would check is to go into Measurement and Automation Explorer (MAX) and click on the Software Tab. I would then check to see which version of the LabVIEW RTE shows up (if any). In theory, if the RTE shows up in MAX, then it should show up in Add or Remove Programs under National Instruments Software (highlight this and click Change....this should pull up a list of all NI products on your computer).
    It's in MAX, but not Add/Remove Programs>NI
    CarlaU wrote:
    If it doesn't show up there, then there are two other things that can be done. The first one involves modifying the Windows Registry. There are a great KnowledgeBase article that discusses how to do this in order to remove the driver.
    Nope - there's nothing to do with the RTE there either.
    CarlaU wrote:
    The second idea is to use a utility we have that I cannot post on the forum. If you create a service request via email or phone then we would be able to help you get the older versions fully uninstalled. You can create a service request at www.ni.com/ask. I hope this helps!
    Thanks Carla - I'll try that avenue.
    Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

  • LabVIEW 8.0 Run-Time engine & shared variables

    Has LabVIEW 8.0 Run-Time Engine the shared variable's support, I wonder?
    The thing is that .exe with globals/locals runs alright, but beeing replaced with shared variables it refuses to run.
    What's wrong? May be need in library(s) absend?
    Thanks.

    You can use the Shared Variable in the Run-Time Engine (you do not need DSC).
    Can you be more specific about what happens when it refuses to run? Are you seeing an error message?
    If you are using Network-Published shared variables, they need to be deployed before you run the application.  You can either deploy them manually with the project, or your application can programmatically deploy them.  You can find some more information about this in the LabVIEW Help under "Shared Variables and Stand-Alone Applications or Shared Libraries" (follow this link and scroll down to the bottom):
    http://zone.ni.com/reference/en-XX/help/371361A-01/lvconcepts/project_variables/
    -Chris

  • Why is VI not executable using Labview 7.1 Run-Time Engine?

    Hi,
    In our Teststand sequence, we have a Labview Action step which is returning an error: "The VI is not executable", along with the error code: -18002.
    This error occurs on a Production PC using the L.V. 7.1 Run-Time Engine.
    I'm aware of Mass Compiling to ensure all the VI's are the correct version, but this has not resolved the problem.
    The software was installed on the production PC using a Teststand created installer, with the Labview Adapter set
    correctly to the Run-Time Engine, i.e. not trying to open the Labview Developer Server to execute the step at run time.
    Because it's the 1st Labview module to be executed, I added another similar step to run beforehand, i.e. the new simple
    Labview code ran first. This executed correctly, but then the next step caused the error above.
    The small number of associated sub-vi's are on the target PC, and have been mass compiled.
    I've had -18002 errors before, but this is one I cannot cure.
    All suggestions gratefully received.
    Gary.

    Hi Guys,
    Regarding this -18002 error when using the Run Time Engine instead of the Development Environment, what is the VI within the step that is failing (in any of the cases you've mentioned) trying to do? Are they built around any toolkits?
    In my experiments with a simple VI (with just a user dialogue) using the LabVIEW 7.1 RTE in both TestStand 3.1 and 3.5 this morning, I haven't found any issues
    There is a possibility if any of the sub-VIs or toolkits you use contain a Merge Errors.vi, that the Run Time Engine picks up a copy of the VI built for previous versions of the RunTime Engine (due to the order in which the sub-VI directories are scanned), and it cannot convert it.
    There are a few solutions for this, the easiest one looks to be to copy the error.llb\Merge Errors.vi for LabVIEW 7.1 into the same directory as the VI you're calling (so TestStand can pick it up easily).
    Can you let me know if this solution helps at all? If not, would it be possible to post up any of the code or sequence you're having problems with?
    Best wishes,
    Mark
    Applications Engineer
    National Instruments

  • Labview 6.0 run-time engine will not control BKPrecision power supply.

    I created a test program in Labview 6.0 to control a BKPrecision power supply and Measurement computing DAQ in our test system. I am able to control both intsruments from my PC which has Labview loaded on it. I created an executable from the application builder tool for distribution. When i install the run-time engine and executable on a new PC (Labview not installed), i am unable to control the BKPrecision power supply. The BK power supply is connected to the serial COM port of the PC.
    Do i need to install drivers that are not included in the executable build?
    Do i need to install VXIpnp (VISA interactive control)?
    thanks,
    Tim
    Solved!
    Go to Solution.

    tmann-
                The API Drivers are often times for more specific Operating Systems than the others (Linux, Pharlap, etc.) and they are more easily accessible for programmers that want to (and have enough time to put up with the headaches ) of building speciality drivers off of ours. 99% of the time you just want the drivers that come up first when you type in your driver name (NI-VISA). As to versions, issues can crop up later from not using the exact same driver version but all the drivers are built off of each other (they hardly ever scrap an entire driver and start over) so the problems should be minor. Its up to you about switching. Unfortunately to downgrade version you have to completely uninstall the driver from Add/Remove Programs>>National Instruments Software>>Your driver and then reinstall the correct one. If you have time, I think it is well worth it to do it right the first time. Hope this is helpful!!
    Grant H.
    National Instruments
    LabVIEW Product Marketing Manager

  • Does exist a run-time engine LV 8.0 for NT ?

    I have developped a program in LabView 8. I need to run it on an older machine (PIII 550 Mhz), actually running under Windows NT 4.0 SP6. It seems that the run-time engine of LabView 8.0 is no more compatible with NT. Is it true?
    Well, I can upgrade the OS on this older machine, but... :-(
    Thanks.
    Jiri

    Hello Jiri,
    afaik LV8 requires WinXP as minimum. So you better use LV7 (or even LV6) for your older WinNT/P3-550 machine...
    Best regards,
    GerdW
    CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
    Kudos are welcome

  • Uninstall LabVIEW but leave run-time engine and DAQmx

    Hoping there is an easier way to do this, basicall we are developing software on a customers computer that we buy and will eventually ship to them. However we can't ship them LabVIEW so we make an executable and just keep the run time, DAQmx and MAX. Is there anyway to do this easier than uninstalling LabVIEW and reinstalling everything else?
    Windows 7
    LV2013

    Under Windows, try going to Control Panel | Programs and Features and find National Instruments Software. You might be able to select all except the run-time, DAQmx and MAX, then select uninstall. If not, then perhaps consider just making a full installer for your LabVIEW executable solution, this will clearly install only the necessary components for your code to work (if it's LabVIEW 2013).
    Thoric (CLA, CLED, CTD and LabVIEW Champion)

  • Why does "NI LabVIEW Run-Time Engine 6.1" window appear when I start LabVIEW?

    it also prompts "insert the 'NI LabVIEW Run-Time Engine 6.1' disk.
    Attachments:
    windows.jpg ‏26 KB

    Hi,
    There can be many reasons why this error would appear. Most probably, you have a broken installation of the Run-Time engine.
    Just reinstall the run-time engine from the LabVIEW 6.1 CD. You can also download it from our web site:
    LabVIEW Run-time Engine Version 6.1 for Windows 95/98/NT/2000/ME/XP
    Zvezdana S.
    NAtional Instruments

  • Is Labview Run-Time engine 2009 SP1 compatible with Windows 8

    I potentially need to install a Labview executable and Run-time engine 2009 on a Windows 8 OS.  From looking at the run-time engine support, it only looks like it only shows windows 7 down to XP.  Does anyone have any experience using Runtime 2009 on Windows 8?

    Hi Awhite144,
    The first version of LabVIEW to officially support Windows 8 is LabVIEW 2012 SP1. That being said, I would expect LabVIEW 2009 to work fine on Windows 8, and if you run into any trouble, feel free to post it here. LabVIEW 2012 SP1 installs a number of older LabVIEW run-time engines (including LabVIEW 2009), so it will install on Windows 8.
    I have not personally used LabVIEW 2009 on Windows 8, maybe if someone else has experience with it they can weigh in, but I expect it to work.
    As an important consideration, I assume you are talking about the full version of Windows 8, not Windows 8 RT. 
    Regards,
    Jeff Peacock 
    Product Support Engineer | LabVIEW R&D | National Instruments 

  • Labview 2010 run-time engine silent install

    I am having trouble with installing the run-time engine for LabVIEW 2010 with the silent option.
    I am using the minimum version of the run-time engine.
    Before I used the LV7 run-time engine. Then I could install it silently using LVRunTimeEng.exe /qb!
    In LabVIEW 2010 the run-time engine is no longer a single file but a directory that contains the installation files. There are two files that can be used to launch the installer Setup.exe and LV2010runtime.msi.
    Setup.exe does not seem to accept any command-line arguments. LV2010runtime.msi however accepts the command-line arguments and can be installed silently.
    Now my problem is that I am building a windows installer using a third party application and it is only possible to launch exe files after the installation completes. Before I could launch the LVRunTimeEng.exe /qb! to install the labview 7 run-time engine but now when I have upgraded to labview 2010 I cannot do the same for Setup.exe.
    My question is if it is possible to use the Setup.exe file to install the Labview 2010 run-time engine (minumum) silently?

    Setup.exe runs a number of other .exe files during its execution.  This article looks like it will allow you to run setup.exe silently by supressing all messages and windows:
    http://digital.ni.com/public.nsf/allkb/878FC4C374013ADF8625733D00688F67

  • UNABLE TO LOCATE THE THE LABVIEW RUN-TIME ENGINE.LVBROKERAUX71

    UNABLE TO LOCATE THE THE LABVIEW RUN-TIME ENGINE.LVBROKERAUX71 REQUIRES A VERSION 7.1 (OR COMPATIBLE) LABVIEW RUN-TIME ENGINE。PLEASE CONTACT THE VENDOR OF LVBROKERAUX71 TO CORRECT THIS PROBLEM
    Uninstalled DAQ and reinstalled.  MAX still throws an error. 
    Any Isead besides uninstalling 3/4 of my software?
    Merry Christmas!
    Matthew Fitzsimons
    Certified LabVIEW Architect
    LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison

    To clean up your system, you will need to uninstall the LabVIEW 7.1 run-time engine, and the "LVBroker," and the "LVBrokerAux71" components using the MSI Blast utility.  To obtain this utility, please create a service request for phone or e-mail support, and contact one of our Applications Engineers about this issue.  Thank you!

  • 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

  • Error on installation of LabVIEW Run-Time Engine 8.5.1: "This application has requested the Runtime to terminate it in an unusual way"

    Hi,
    a colleague in India cannot install the LabVIEW Run-Time Engine 8.5.1 on Windows XP. On attempting to install, an error box is shown, which says:
    (window title)
    Microsoft Visual C++ Runtime library:
    (message box text)
    Runtime error!
    Program: C:\National Instruments Downloads\LabVIEW 8.5.1\Runtime Engine\setup.exe
    This application has requested the Runtime to terminate it in an unusual way.
    Please contact the application's support team for more information.
    http://img529.imageshack.us/my.php?image=runtimeerrorvt7.jpg
    I didn't find any relevant clues for this in NI forums. A search at Google brought me to http://support.microsoft.com/kb/884538/en-us, offering a HotFix to solve the problem. Unfortunately, the installation of this HotFix does not solve the problem.
    Do you know this behavior and do you have any ideas how the problem can be solved?
    Thanks in advance.
    Best regards
    Manuel
    Message Edited by Manuel Häderle on 10-07-2008 10:41 AM
    Solved!
    Go to Solution.

    Hi there
    log in as administrator and kill all processes not needed and try again. I've seen cases where one of these free download tweak applications (like "Memory Defragmentation" and stuff like that) caused that error. 
    Best regards
    chris
    CL(A)Dly bending G-Force with LabVIEW
    famous last words: "oh my god, it is full of stars!"

Maybe you are looking for

  • Adobe flash videos now only show up/play once fully loaded.

    All online flash related videos used to start playing once I hit play. They would continue to load as they played. This changed a month or so ago. Now after I hit play I just get the blank screen UNTIL the video fully loads. Then it plays. I thought

  • Let us prepare Configurator Tutorial together

    For all: For the last 3 months I spent a lot of time to learn Configurator by myself. Does any one what to join me prepare a good tutorial for others to use. We have many good tutorial for java,database and other programming software. Like that let u

  • Special Procurement using External Procurement & Subcontracting

    Hello everyone! We currently have a material  that is set up as "F" Procurement Type (External) with Special Procurement Type "30" (Subcontracting). We have active scheduling agreements for subcontracting procurement of this material.  User also need

  • What happened to my text?!

    This is a problem I've been seeing ever since the first day I turned on my new iMac, but it's never given me enough trouble to bother asking about it until today. http://img511.imageshack.us/img511/9937/mactext2gj8.png Before today, it would just dro

  • Firefox takes up 2.6 million RAM after just an hour...

    Hi, I've had a problem for about a year now where Firefox takes up too much physical memory. Recently it's been getting so bad that my RAM (6GB) usage is at 95% or higher and the freezing and lagging from Firefox gets so bad that I can't even close t