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?

Similar Messages

  • Installing NI-DAQ (MAX) also installs Run-Time engine?

    Hello all,
    I have noticed, on computers where I have installed MAX (which installs NI-DAQ) that the Run-Time engine also appears.
    Does MAX install the Run-Time? Or was it MAX that installed? Or was it probably already there....?
    Thanks,
    Richard
    Richard

    That would make perfect sense. It'd be "nice" if the CD eluded to that fact, so you don't have to bother with finding the RTE if it's already there.
    Thanks Analog Kid --- good Rush song by the way... but the're all good! (except maybe Rivendell, but only a true fan would know that one).
    Richard
    Richard

  • 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

  • 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

  • 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 

  • How to install Vision run-time engine to a desktop PC converted to real-time target

    Hi, all
    I don't know how can I install the vision run-time engine to a desktop PC which I converted to a real-time target.  The same problem applies to installing real-time run-time engine and labview run-time engine to the real-time target.  The only way to install software to real-time target is through "add/remove software" in MAX for remote system, but it is not for all types of run-time engine installation.  
    I am also confused about how to activate those run-time engines for the desktop PC as real-time target.
    Please help and great thanks.
    Wei 

    Hi turtle,
    Here is a link that explains how to set up a desktop PC as a real-time target.  The section for Formatting & Setup should help you the most.
    NI Developer Zone Tutorial: Requirements for Desktop PCs as LabVIEW Real-Time Targets
    Justin D.
    Applications Engineer
    National Instruments

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

  • Run time engine install from build package failure

    when trying to install LV 8.0 Run Time engine from build package, an error is generated that the target computer needs to have LabView 8.0 installed.
    i have verified that the run time engine is included as an additional installer under the build project.

    Hi MJK34,
    If you are being prompted to install LabVIEW there must be something in the build that requires LabVIEW, not just the runtime.  Can you post a screenshot of your build specification?  Thanks.
    Stephen S.
    National Instruments
    1 Test is worth 1000 expert opinions

  • Calling a VI which uses "system exec.vi" with LabVIEW run-time engine as adapter

    Hi,
    My TestStand sequence calls a VI which includes a call to "system exec.vi". When I try to load it in TestStand and if LabVIEW adapter is set to run-time engine, I get an error message "Unable to load Vi...". If I switch the adapter to "Development system", then it works fine.
    Is there any way to use "system exec.vi" in a VI which is called in TestStand with LabVIEW run-time ?
    Thanks,
    Alex
    Solved!
    Go to Solution.

    Hi Alex,
    In you case, you are getting a -18002 error.
    The reason is explained in the following link:
    -18002 Errors in TestStand
    http://digital.ni.com/public.nsf/allkb/D82FEAF0B4BA293A862575710053E252?OpenDocument
    Please have a look at the 2nd reason. This is your case.
    Hope it helps,
    Regrads
    Julien De Freitas / Applications Engineer / Certified LabVIEW Developer (CLD)
    National Instruments Switzerland

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

  • Does Vision Development Module obviate the need for the Vision Run Time Engine?

    I have several computers with the full version of Labview (8.0.1 and\or 8.2) as well as the most recent version of the Vision Development Module (VDM 8.2.1), all fully registered and activated.  In addition, I have one computer we have designated the "build" computer which has the professional version of LV 8.2 as well as LV 8.0.1 Full version w/ Application Builder (we have delayed migrating certain applications to 8.2 for various reasons).  Instead of distributing applications as source distributions to these computers (uncompiled VIs), we would like to use our build computer to compile applications that make use of the Vision image processing VIs.  I know that all of these computers have the appropriate LV run time engines installed, but I was wondering if I need to install (and thus purchase) the Vision Run Time Engine for each of these computers.  I know that when you install VDM, you also get a copy of the vision RTE (in C:\Program Files\National Instruments\Vision\Run-Time Engine).  Does this mean the engine is already installed and ready to run compiled applications?  Or do we need to pay for the engine on each computer?

    The Development module includes the RTE for that machine.
    For the other machines, you will need to purchase the Vision RTE and install and activate for each machine. See the KB article below for more details.
    http://digital.ni.com/public.nsf/websearch/F1699570F78FECBB86256B5200665134?OpenDocument
    Ed
    Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
    Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

  • VI backwards compatibility with older run-time Engines

    I currently developed a VI in Labview 8.6.1.  I also created an exe for it so that I can run it on another computer.  However, the other computer has an older version of the Run-Time engine installed and so my program cannot be executed on that computer without upgrading the run-time engine to 8.6.1.  But....that computer also has some programs that run on that version of run-time engine.  I have two options here but I do not know the effects or how to do it.
    1) Install a newer version of the run-time engine (8.6.1) - Will this break the current functionality of the programs already on it?
    2) Is it possible to have my VI run on older versions of the run-time engine?  If so, how do I do that?
    Thank you.
    Solved!
    Go to Solution.

    As dennis said simply install the new runtime engine. We have machines that have 5 versions of the runtime engine on them and we haven't experienced any problems.
    Mark Yedinak
    "Does anyone know where the love of God goes when the waves turn the minutes to hours?"
    Wreck of the Edmund Fitzgerald - Gordon Lightfoot

  • 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

  • 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

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

Maybe you are looking for