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

Similar Messages

  • Is it possible to choose the serial port if only the run time engine is installed

    I have an application, which communicates over the serial port. When I use the full version of Labview I can change the serial port without any problem from Com1 to Com2 (similar to the example “Hardeware input output -> serial -> Labview serial vi"). When I build an application and try to run this program on a computer where only the run time engine 6.1 is installed, it is not possible to choose the serial port. Since there is no “Measurement and Automation Explorer” available on the run time engine and no directory C:\VXIpnp is created, when the run time engine is installed, I do not see a way, how I can satisfy the computer with the information it needs for configuring
    the different ports. Any suggestions?

    Hi Daniel,
    Before LV6.1 there was LV5.1 In LV5.1 the way to Spedify a resource was to use a string control with correct VIsa Resource Class identifier. For eg. "GPIB0::11" or "ASRL1::INSTR". With Introduction of VISA Resource Name Control and linking with MAX, These names are Available from Pull Down List and Can be Aliased, meaning ASRL1 which is Serial Port 1 can be called COM1 and so on. However the old method still works with all 6.1 Controls. Only thing is you have to make sure you Dont Conflict the Class Names ie Use "GPIB::.." instead of "ASRL..." when addressing Serial Port VI's.
    To solve your Problem I would Build a Menu ring with COM1 to COM4 in the Pull Down List.
    Next, If I use the Traditonal Serial Port VI wich accepts the Integer as Seria
    l Port #. I just Wire the Menu Ring to this VI.(Remember COM1 is 0, COM2 is 1 for this VI)
    If I use VISA Config Serial Post. I build an Array Constant with Corresponding VISA Class Names So in our case a String Array Constant of 4 elements "ASRL1::INST" to "ASRL4::INST". I Use Index Array Function With the Index Wired to my Menu Ring. The Array Input Terminal Wired to the Array Constant. The Output of this Array will be correct Visa Class Name Based on slection of my Menu Ring. I can Wire this as Input to my VISA Config Serial Port Vi.
    I have attached a Small VI to Illustrate this.
    Drawback: You must Predefine what Ports you will Want to Use. Basically you define all the cases.
    I hope this Answers your Q!
    Good Luck
    Mache
    Good Luck!
    Mache
    Attachments:
    Serial_Port_Select.vi ‏36 KB

  • Can I use the labview run-time engine 2010 with my LV 2012 program?

    Hi all,
    I will receive the new Labview Developer Suite 2012 DS2 in a few days and
    I am wondering if it is possible to run LV2012 programs on the LV run-time engine 2010 or is it necessary to update all my clients from run-time engine 2010 to 2012?
    Stay Hungry, Stay Foolish
    Solved!
    Go to Solution.

    Hi Benjamin,
    You will not be able to use the LabVIEW 2010 run-time engine with LabVIEW 2012 applications.  Versions of run-time engines need to correspond with the version of LabVIEW that you have installed.
    The following links direct you to our download pages for the run-time engine:
    The 32-Bit Run-Time Engine can be downloaded from our website as can the 64-Bit Run-Time Engine, depending on which version of operating system you, use by clicking the link under "Standard Download".
    Hope this helps.
    Marshall B
    Applications Engineer
    National Instruments UK & Ireland

  • Error -18004; An error occurred accessing the LabVIEW Run-Time Engine DLL. TS 4.2.1 / LV 2010

    When I try to run a VI that is reentrant in parallel execution, I receive this error.  The details of the error is:  LabVIEW:  The property or method is not supported in this version of LabVIEW.
    This is run under the Simple Operator Interface in LV 2010.  The TestStand engine is version 4.2.1 using LV 2010 run-time engine adapter.
    If I save for previous version to LV 2009 SP1 and set the TS adapter to 9.0.1 (2009 SP1), this works.
    Can anyone reproduce this error (bug?) ?
    Solved!
    Go to Solution.

    have you got the latest updates for TestStand using LabVIEW 2010?
    http://digital.ni.com/public.nsf/allkb/7D728B70F167CE088625776E00582C7B?OpenDocument
    Regards
    Ray Farmer

  • Does CVI install the LabVIEW Run-Time Engine?

    Hello,
    running the NI Update Service suggests to download a 226 MB patch for the LabVIEW 2012 Run-Time Engine... (all I installed knowingly was CVI2012)
    --> How can I check if the computer has this engine installed, what is the file name to search for (and is it needed by CVI)?
    Thanks!
    Solved!
    Go to Solution.

    Hello,
    1) You can use Measurement And Automation Explorer (MAX) to see the National Instruments Softwares installed:
    2) Some CVI softwares use the Labview runtime.
    By example, when you use the CVI Menu: Help / Find Examples... , you launch NIExampleFinder.exe which uses the labview runtime:
    3) When you install the NI-VISA library, the software C:\VXIPNP\WinNT\NIvisa\NIvisaic.exe is also installed. This utility is a Labview Software.
    I think it's difficult to avoid the Labview runtime on a computer with NI softwares installed...

  • 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

  • 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/369618​104E25B08E86256F54006A4E2F?opendocument&node=13205​0_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

  • Upgraded from LabVIEW 8 to 2013 and now VI asks to find the installati​on package for Run-Time Engine 7.0

    I recently installed LabVIEW 2013 on a computer (running Windows XP 32-bit).  The machine also has LabVIEW 8 installed, which is what I was using prior to upgrading.  I opened a VI that was created in LV8 and then saved it and all its subVIs in LV2013.  Now when I open the VI in LV2013 and try to run it, a window pops up asking me to find the "lvruntimeeng.msi" installation package for LabVIEW Run-Time Engine 7.0.  If I cancel that dialog box and the subsequent message stating that the installion files were not found, the VI appears (at least from intial inspection) to run normally.
    I closed LabVIEW, downloaded Run-Time Engine 7.0 from the NI website, and tried to install it, but I received a message saying that it is already installed (as I had suspected).  How can I determine what part of the VI and/or its subVIs is trying to make use of Run-Time Engine 7.0?  Alternatively, how can I get LabVIEW to instead use the Run-Time Engine 2013 that was installed when I upgraded to LabVIEW 2013?
    Solved!
    Go to Solution.

    Bob_Schor wrote:
    Are you running your VI from a Project?  If so, you can look at Dependencies and get an idea what "dependent" VIs you might have.  There may be "something old" in your LabVIEW 8 code that has been superceded in 2013, but still "hangs around" -- if you can identify it, you can probably replace it with its "more modern" equivalent.
    If you do not have the VI in a Project, you can simply open LabVIEW, create a new blank project, and add your top level VI to it.  If all of your relevant VIs are in a single folder, add the entire folder.  Now look in Dependencies.
    BS
    Yes I am running the VI from within a LV Project.  After some more searching in the NI Knowledgebase I was able to fix the problem by using the following procedure:
    1.  Use the Measurement and Automation Explorer to uninstall Run-Time Engine 7.0
    2.  Restart the PC
    3.  Open the project, close the project choosing to "save all"
    4.  Restart the PC
    5.  Re-install Run-Time Engine 7.0 using a file downloaded from ni.com
    6.  Restart the PC
    7.  Open the project, close the project choosing to "save all"
    8.  Open the project and run the VI.  No more messages about LabVIEW trying to find Run-Time Engine 7.0.

  • Installing Run Time engine question

    Hi,
    I am new to this and I am looking for information on how to set up a test system PC.
    I have the 2014 developer software and one test seat but need to know how to install the labview 2014
    runtime engine and anything else that I need in order to use this test system PC to run Labview and teststand
    applications that I create with my development system PC...
    Is there any tutorials or instructions out there that I can download that will tell me everything that I need to install and how on my target test system?
    Thanks

    the Installation instructions are on the Download Page
    Installation Instructions
    Close all NI software.
    Run the LVRTE2014_f1Patchstd.exe self-extracting executable and follow the prompts.
    Repeat these steps for all development systems where you want to install the LabVIEW 2014 Run-Time Engine (32-bit).
    The installation files for the Run-Time Engine are automatically extracted to a directory on disk. The installer does not remove the files after installing, if you want to remove these files from disk, be sure to note their location during the unzipping process.
    Jeff

  • Uninstalling LabVIEW Run-Time Engine 6.1

    Hi, I get an error message during uninstalling NI LabVIEW
    Run-Time Engine 6.1:
    Error 2727 NETSCAPEPLAGINSDIR
    How can I fix this problem?

    Armen,
    Here is my guess as to what happened:
    1. You had Netscape installed on your machine.
    2. You installed the LabVIEW Run-time Engine which installed the remote panel plugin into Netscape.
    3. You uninstalled Netscape.
    4. You are trying to uninstall the LabVIEW Run-time Engine.
    If this is correct, then try installing Netscape again, uninstall the LabVIEW Run-time Engine, and finally uninstall Netscape again. If this does not work, then please submit a phone request at http://www.ni.com/ask to get help with MSIBlast.
    Randy Hoskin
    Applications Engineer
    National Instruments
    http://www.ni.com/ask

  • 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

  • Building an Application in Windows to be used in Linux (with the Run-Time Engine)

    Hi All,
    I have an LabVIEW project I have developed in a Windows environment.  I can create an Application (.exe) using the Build Specification -> Application Builder which works fine on the development platform.
    I now want to distribute the application to a Linux Environment.  The OS is openSUSE v10.3 (with GNOME).  I have downloaded the two rpm files needed for the run-time engine and installed them, as per here:http://digital.ni.com/softlib.nsf/websearch/97E14BA3E0C14A89862572C300567733?opendocument&node=13207...
    Now, the question is; how do I create an Application in Windows which can be used on the Linux Box?  According to the Application Builder instructions, it's simply a case of removing the .exe extension in the Target File Name options, however, this gives an error "Invalid Extension."
    If I do create an exe and manually remove the extention is doesn't work on the Linux enviroment (typing ./application).
    Has anyone had experiance of this?
    Many Thanks for Any Help,
    Oliver
    Windows XP SP 2
    Labview 8.2.1
    openSUSE v10.3 (with GNOME)
    LabVIEW Run-time Engine Version 8.2.1 for Linux

    The cross-platform nature of LabVIEW refers more to the code than to the executable.
    LV (given the appropriate development version) can compile the same source code into a Windows (using LV for Windows), Linux (using LV for Linux) or Mac (using LV for Mac) program.
    This means you will still have three versions of your program, one for each platform.
    If you want to distribute VIs (without block diagrams), you will also need different versions of these as without the block diagram, they cannot be re-compiled for a new platform.
    Shane.
    Say hello to my little friend.
    RFC 2323 FHE-Compliant

  • Run time engine and NI-DAQmx installation order

    Greetings Fellow Developers:
    I'm looking at a product manual that contains instructions to install NI-DAQmx, a product software installer created with LabVIEW 2009 SP1 Full and then the LabVIEW 2009 Run Time Engine in that order.
    This does not seem correct--particularly if a LabVIEW 8 (or previous) Run Time Engine is already installed.
    Since I need to test installation of my builds before distribution I'll need to install them on machines that have never had any NI products and also on machines that may have previous Run Time Engines.
    I feel the correct order is to install the Run Time Engine, NI-DAQmx and THEN the application.  Prior to running the application the USB device should be plugged in so the 'add hardware wizard' can install the USB driver(s).
    What is the consensus on this?
    Warm Regards,
    Saturn
    Solved!
    Go to Solution.

    Hello Saturn,
    Could you point out the location of the product manual that explains this order?  Typically, when installing National Instruments products, in particular LabVIEW, we recommend installing LabVIEW, drivers, and toolkits in that order.  So, installing the LabVIEW 2009 Run-Time Engine, DAQmx, and then your application should be the proper installation process.
    Regards,
    Roman Sandoval | National Instruments | RF Systems Engineer

  • The program doesn't find the run time engine

    I create an executable before normaly and after like an installer. When I try it into computer with full LabView licence the program works, but if I install it into a different pc, it requires me to install the run time engine, but the run time engine is installed into the pc. What kind of error can generate this problem?
    Solved!
    Go to Solution.

    Hi vsara
    Mike is correct, you need the VISA runtime to use VISA functions in an executable. If you don't want to install it as a standalone you can include it in your installer as an additional installer.
    Best Regards
    David
    Message Edited by Davidek on 10-23-2009 04:18 AM
    Message Edited by Davidek on 10-23-2009 04:19 AM

  • Run time engine present

    Hi all,
    Does any one know how to find what version of Run time engine is installed in the PC?
    Your help is greatly appreciated.
    Regards,
    Muthuraman S
    Regards,
    Muthuraman

    Muthuraman wrote:
    [...] Is there any possibility the exe is getting run in LabVIEW8.6 run time engine which is giving this issue?[...]
    No.
    I take it that the error dialog is created by Windows. 
    I guess that the target pc has some settings which are not compatible to the exe. I'd first check if the UI used in the exe uses special fonts which are probably not installed on the target. Other possible things are missing dlls or other components which have wrong versions....
    You can check the general functionality of your target if you build a simple exe which just uses a single VI with e.g. the standard state machine (found in the template browser).
    hope this helps,
    Norbert 
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

Maybe you are looking for

  • Best fit lines for loops and sine waves

    I am trying to find a best fit line that will work for sine waves and loops (hysteresis loops). I can get the sine wave just fine, but when I switch to a hysteresis it just puts a line across the middle (I assume because of the 2 y values for every x

  • Do you think middleware or XIF adapter is based on SOA?

    Hi, For current CRM 5.0 version, do you think middleware XIF adapter is based on SOA? Or classic tech.? How about it in new CRM?

  • Imac 14,2 crash¨, imac 14,2 crash¨

    Hi, I recently bought a kit of 16Go additional RAM for my new 14,2 later 2013 iMac. Following reference from corsair: CMSA16GX3M2A1600C11 (http://www.corsair.com/en/corsair-mac-memory-16gb-dual-channel-ddr3l-sodimm-memo ry-kit-cmsa16gx3m2a1600c11.htm

  • Tables - Modify Multiple Connections in PowerPivot

    Hi, Due to some legacy reasons, I have different tables which have 4 connections to SQL Server in PowerPivot. The 4 connections are actually referring to the same database, so how can I modify the connections so my tables refer to the same database a

  • Menu button has stopped responding

    Help! My 1st generation nano - my workout buddy - is not responding to my pressing the menu button. It seems to be completely dead and non-responsive. I haven't dropped it... but it may have become slightly damp from sweat. Now it is stuck on a calen