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

Similar Messages

  • Can't install run-time engine on Ubuntu 8.04. Get /bin/sh failed to load.

    Simply receive a message when trying to install the LabView run-time engine .rpm file that says /bin/sh failed to load (or is required, I forget exactly).  I checked, I have BASH installed, and /bin/sh is a shortcut to an executable on my machine.  Is this a bug in the installer, or is there something else I need?

    LabVIEW installation is not supported on Debian based Linux systems (of which Ubuntu is the most popular).  However, many people have had success installing to various flavors of Ubuntu.  You can search these forums using the key Ubuntu and find the problems they had and how they solved them.  If you cannot find an answer to your problem, let us know.
    This account is no longer active. Contact ShadesOfGray for current posts and information.

  • Error 1722 when installing Run-Time Engine 6.0

    I am unable to install the necessary LabView Run-Time Engine 6.0 required to run my VitalView Software.  I have reviewed the message boards and attempted all possible solutions: disabling anti-virus programs, following the NI support links: http://digital.ni.com/public.nsf/websearch/334E91287EDEA75286256D9B003A947A?OpenDocument.
    None of these methods will allow for the Run-Time engine to be installed.  What can I do?
    Help very much appreciated, thank you! 

    My OS is Windows XP.  
    I am trying to install an older LabView run-time engine since my application VitalView asks for a LabView 6.0 Run-time engine (or something compatible). 
    I have attached the jpg of the error message that I receive whenever I attempt to install the LabView engine.  
    Thank you so much for your help!
    Attachments:
    Error1722.jpg ‏57 KB

  • Installing run-time engine 7.0 on windows NT

    I attempted to Install Labview run-time engine 7.0 (LVRunTimeEng), on windows NT with workgroups 4, but got the message wrong OS. I am sure I downloaded the correct version (which is supposed to support Windows NT). Anyone have the same problem ? Anyone know how to fix it?
    Thanks in advance
    Jonny

    This message comes from the MSI installer engine. The engine requires Service Pack 6 to be installed on NT 4.0 systems. Can you verify that you have this service pack.
    Naren

  • How can I uninstall Labview run time engine from the machine?

    I understand that Labview has not given any provision to show customized 'License Agreement screen'. Isn't it? This is the main cause of my problem. Since I want to show our own license agreement (LA) screen, I made the one using Labview. To show this license agreement screen, I first install a small application which has only this LA screen with Labview run time engine. The customer can see License Agreement Screen with Labview Run Time Engine on his machine. If My customer accepts the LA, I will install the main application further by calling another setup.EXE file.
    If my customer selects 'Do Not Agree' to the LA, I will quit the installation process. Here I also want to 'uninstall' Labview Run Time Engine
    from his machine since he doesn't accept License. I would like to know how to uninstall Labview run time engine from his machine?
    Another way which I could think is to run the LA screen from the CD with Labview run time engine on the CD. I will start installing the main S/W to the customer's machine with LABview Run Time Engine only after he accepts License agreement. I would like to know how to run the Labview application from CD without installing run time engine on the target machine?
    Can anyone suggest solution to my problem?
    Thanks,
    Chander

    J-Tek,
    I would suggest re-installing the Run-time Engine and then uninstalling it after a reboot. Also, you can download a program called Msicuu.exe (for NT, 2000, XP or Msicu.exe for 9x) to help clean up the registry for uninstalled programs.
    Randy Hoskin
    Applications Engineer
    National Instruments
    http://www.ni.com/ask

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

  • Error 63 run-time engine

    Hi, I'm trying to communicate with an instrument through TCP/IP using AK protocol. I've created a VI that works fine on my PC where I have installed Labview 2011.
    When I create an executable from this VI to use it on a PC without Labview, it does not work and I receive the error 63.
    Of course, I've have installed run-time engine and also VISA run-time, and I use the same configuration on the port (same ip address and port).
    Moreover, the executable works also fine on my pc as well as the VI.
    Have you got any suggestion?

    Error 63 is "LabVIEW:  The network connection was refused by the server.". 
    Is the target machine on the same subnet as the instrument?
    No routers/firewalls between the two devices?
    Net nanny/web filtering/firewall turned off on the target PC?
    Instrument doesn't have to be configured to allow connections from the target machine's IP?
    My guess is network configuration.  Try pinging the instrument's IP from the target machine, see if that goes through.
    First thought was missing drivers/modules, but since you've got VISA and RTE installed, I think you're covered there.

  • Client view vi webpage without needing run time engine

    I am trying to create a environmental webpage attached to a Labview vi where end user can browse the web page from their home computer internet.  Problem is I read that the end user need to have the Run Time Engine installed in their computers, now this sucks. If the end users need to remember to install run time engine to every computer their visit, there will no business.  Is there someway to bypass this? 
    http://zone.ni.com/reference/en-XX/help/371361B-01/lvhowto/creating_html_documents_an/
    "If you want clients who do not have LabVIEW installed to view and control a front panel remotely, they must install the LabVIEW Run-Time Engine, then view the front panel remotely."
    Solved!
    Go to Solution.

    Hi sunflower2772,
    if you want to use the NI function of webserver, then you have to install the runtime engine (there is also a smaller one), the same as using some JAVA code.
    If you don't want to do this, then you have to write your own webserver.
    Mike

  • Can labview export shared libaray use in C++ without run-time engine?

    Hi, everyone
    Now, I write a VI for a algorithm and export it as a dll.  I use the dll in my C++ apps. It is good. But I want to know how my apps can run without labview run-time engine or I must  install run-time engine?

    you can install run time engine or include dll which will be used by your application.

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

  • Install labview 6.1 (or compatible) run-time engine with labview 2011

    I have installed a trial period version of Labveiw 2011 in order to check for possible upgrade issues I may have if I decide to upgrade from labveiw 6.1. Well, needless to say there have been alot. That is as expected since I have not updated labview in many years. I am still not under any pressure to update; however, I would like to in order to get support and make sure I do not have any compatibility issues with new  equipment purchases. I have been able to resolve most of my compatibility issues with simple code fixes and such. However, twice now I have run into an error when launching labview executeables compiled by two different equipment manufacturers. The equipment I am using is not even old...maybe a year or so. When I launch the labview executables to control this equipment on a PC that has the trial period labview 2011 installed, I get an error message stating something like " This requires a Labview 6.1 (or compatible) run time engine." I have tried to download and install the 6.1 labivew engine but I can't install this engine on a PC which has labview 2011 installed. Can someone explain how I am to run these executables under labview 2011. I can't imagine these executables were developed using 6.1 since this equipment is not even a year old now.
    Solved!
    Go to Solution.

    Im not for sure I am on the same page with you here. Im not trying to develop any code myself. I have some labview executables that came with hardware we purchased in order to control it. We used to have labview 6.1 installed; so everything was working ok. But now that I have installed 2011, I get an error message when trying to run these executables. The error message states that this executable requires a labview 6.1 or compatible run-time engine. I have seen this error on both XP and Windows 7 machines. I did not develop the executable, it was developed by the hardware manufacturer. But since this hardware is only about 1 year old, I an assuming they used a newer version of Labview to develop this code. Certianly newer than 6.1.
    So I guess my question is..is there a way for me to get this executable to work on a PC that has labview 2011 installed. I have tried to install a labview 6.1 run time engine but it will not install. Any other options?

  • 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

  • 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

  • Path where to install the run time engine (on Linux)

    I have a cluster of Linux computers where I would like to run compiled LABview (8.20 at the moment) applications build
    with the application builder.
    Therefore I would like to install the LABview run time engine on a NFS mount file system seen from each computer.  But
    the installation procedure of the run time engine does not propose to
    choise the installation directory, but force the installation
    in  /usr/local/lib.
    I try to workaround this problem and have copied the /usr/local/lib/LABview.8.2 directory to my NFS filesystem and
    made the 'necessary' links.
    Unfortunatly it doesn't run and  fails because  the
    liblvrt.so.8.2 library  can not access patched versions of the
    libOSMesa.so.4
    and libGL.so.1 librairies but uses the standard ones in /usr/X11R6/lib.
    Even by setting my LD_LIBRARY_PATH correctly to access the patched librairies versions it does not run because the
    liblvrt8.2 library seems to be  linked with the following
    'rpath'   (given by the command 'strings liblvrt.so.8.2 |
    grep patchlib')
    $ORIGIN/LabVIEW-8.2/patchlib:$ORIGIN/patchlib:/usr/X11R6/lib:/usr/lib:$ORIGIN:$ORIGIN/LabVIEW-8.2/linux:$ORIGIN/linux:$ORIGIN/resource
    which prevents to access the patched librairies versions if the $ORIGIN is not set. Therefore I tried to set $ORIGIN as an
    environment variable but it doesn't change anything.
    Therefore my question is: Did somebody have already had this type of problem,  what is $ORIGIN and how I can set it ?
    Thanks in advance.

    Sir,
    Please could tell me the distribution you use ?
    Cordially,
    Pierre R...
    Certified LabVIEW Developer

  • Does Labview run-time engine 6.0 application created by Window NT can install & run on other OS?

    I created a Run-Time engine 6.0 application from my Vi and it is working fine! I wonder that this application can install and run on other OS system? What I have heard is "Yes" ... but I am not sure!
    Any one know for sure? Thanks.

    > I am sorry that I did not clarify my question enough, I meant other
    > kind of OS 's that are not from Microsoft Windows!
    >
    Across multiple OSes, you will most likely be able to load the VIs and
    execute them in the LV environment or rebuild the executable with no
    problem. But, you will not be able to run executables built for Windows
    on Mac, Solaris, or Linux. The reason is that executables have to meet
    binary standards, and those standards differ between the OSes. It
    really doesn't matter what language/tool the executable is built with,
    if it is the OS that is loading it, it will be specific to the OS.
    It would be great of someone like ISO or ANSI declared an executable
    standard that all OSes could load and execute, but since t
    he goal of
    executables is maximum flexibility and maximum performance, it is
    unlikely that this new standard would win out over the existing ones.
    If this comes about, the LV team will definitely be looking to take
    advantage of it.
    Greg McKaskle

Maybe you are looking for

  • This is a problem for the experts around here

    I really need help with this - I have been trying to get this to work for 2 weeks now and so far no one has been able to help. See http://www.kirupa.com/forum/showthread.php?t=248030 and http://www.kirupa.com/forum/showthread.php?t=249806 for my prev

  • Business Area Wise Payment in F-53

    Hi Frnds., We are using ECC 6 and have document splitting functionality active. I have  created an invoice using FB60, with debiting 2 exps  belonging to 2 Business Areas and crediting one vendor. In the GL view, two vendor line items are generated f

  • Asset Retirement for Interco Asset, Partner not in SAP

    Hello, We need to retire an asset to another affiliate that is not in SAP, that is defined as a customer. In this case, which transaction needs to be used for this asset retirement. F-92 or ABT1N ? What would be the difference ? Regards, Siri.

  • Report folder permission can not add group

    after upgrade to 11.1.1.2.0 ,when set report folder's permission, in the group list ,can only see "Administors", no other groups created by myself. how can i add other groups to this list?

  • Adapters list!

    Hi, our basis guy installed XI and when I see Adapter monitoring I see only JPR  not any other adapters. does it mean ,if we have JPR we have all other adapters too? in PI7.0 SP12. I told him adapters should appear atleast in greyed state,but he says