Does labview run time engine 8.6 LVRTE86std​.exe supports DAQ?

Due to the LONG TIME required to build an installer with exe, and this kind of DAQ issues http://forums.ni.com/ni/board/message?board.id=170​&message.id=324343&query.id=1071542#M324343
I want to just give the user the Labview run time engine 8.6 LVRTE86std.exe  http://joule.ni.com/nidu/cds/view/p/id/1101/lang/e​n , and ask them to copy paste the exe.
But does the LVRTE86std.exe contains all the necessary dependency for DAQ? Including the Sound and Vibration dependencies required for DAQ? Is there some document I can look up to see whether LVRTE86std.exe supports DAQ and I dont have to build an installer of my own?
Solved!
Go to Solution.

No, the runtime does not include DAQmx. It does not include any hardware drivers. That is discussed in numerous posts.

Similar Messages

  • 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

  • Does Labview run-time engine 6.0 application created by Windows NT/2000 can install & run on UNIX

    LabVIEW exe created in Windows and running in UNIX

    LabVIEW source code from one OS can be ported to another OS (except for OS specific things like ActiveX) but executables cannot. You would need the unix version of LabVIEW and it's app builder to create an new exe.

  • Installing LabVIEW Run-Time Engine 8.5.1

    I want to run saved VI's from one computer with LabVIEW 8.5 Professional Development (8.5) on another computer using the Run-Time Software.
    After installing LabVIEW Run-Time Engine 8.5 (LabVIEW85RuntimeEngineFull.exe from http://joule.ni.com/nidu/cds/view/p/id/861/lang/en), do I need to do anything else before running a saved VI created in LabVIEW 8.5 from another computer? I install the program, but the only options under programs-national instruments are:
    -data socket
    -License Manager
    When I installed LabVIEW DSC Run-Time System 7.1 on the same computer there was an shortcut under "programs-national instruments-" to LabVIEW DSC Run-Time System 7.1, which is what I need but for the Run-Time Engine 8.5 instead.

    Joseph is correct. The run-time engine is only for "stand-alone" executables created with the Application Builder (included in the Professional version or higher, or can be purchased separately if you have the Base package). To run a vi in the development environment, you need one of the LabView packages.
    Message Edited by Edjsch on 05-12-2008 01:48 PM
    Message Edited by Edjsch on 05-12-2008 01:48 PM

  • 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

  • Unable to locate the LabVIEW Run-Time engine

    Using LabVIEW 2011, I have built an executable and installer including the LabVIEW Run-Time engine. I built the app on a 32-bit system. I'm deploying it to a Windows7 64-bit system. When I ran the installer, rebooted, then tried to run the app, I got an error messsage stating "Unable to locate LabVIEW Run-Time Engine", stating that the LVRTE 2011 was needed to run the app, and asking if I want to download from NI. I have tried downloading the RTE and re-installing it, but when I try, I get an error message from the installer stating that there is a newer version of the RTE already installed, and the installer exits! I have tried un-installing the application, but have had no luck removing the RTE. Now I'm stuck. The re-installed executable application says it can't find the RTE, and the RTE installer says there's a later version already installed!
    I can't go forward or backwards!
    Prior to running the installer for this app, I had a working LVRTE for 2011, and was running some other executable LabVIEW programs on the target box. However, since this new application had additional components not included in the original install of the RTE, I built the new installer which included the additional components. Once I ran that installer, my problems began.
    In my frustration, I've tried downloading from NI both the 32 and 64-bit versions of the RTE, and installing them. I realize that the app was built on a 32-bit system, so the 32-bit RTE SHOULD have run it fine, but didn't.
    At this point I have removed the 64-bit RTE using the NIUninstaller. I believe I need to completely remove all 32-bit RTE components and start over, but I have not been able to. The 32-bit RTE does not show up in any un-install utilities I've found.
    What could be causing this problem, and how do I get past it??
    Thank you.

    One thing I did discover in my struggles is that the RunTime engine on the target box needs to be based on the environment of the development box. So if you built the app on a 32-bit machine, you would need to install the 32-bit RTE, even on your 64-bit target box.
    The RTE Uninstaller might not show up in the Windows Add/Remove Programs utility. In my case the 64-bit RTE uninstaller showed up, but the 32-bit did not. The NiUninstaller (C:\Program Files\National Instruments\Shared\NIUninstaller) did list both RTEs for uninstalling, but still didn't get me past the problem.
    I was finally only able to get past the problem by doing a system restore to a point in time prior to my changing of the RTE.
    Good luck.
    Dan

  • NI LabVIEW Run-Time Engine + TCP/IP

    Hello, Anybody knows how to activate TCP/IP service on PC with standard NI LabView Run-Time Engine installed. If I trying communicate with server from my PC (LVRTE) its works correctly.   However, when I am trying interchange client and server applications it appears with error 1.  Probably I need to add some settings to *.ini files on PC with LVRTE? --- Alex  

    <Alex> wrote:
    Client/Server applications are communicate via standard TCP/IP VIs. I have tried to add 3 line as you wrote to server.ini, but it's didn't help
    As I indicated, the lines are only applicable to using the VI Server. You had not indicated whether you were using the VI Server or just the TCP/IP VIs. At this point we need a better explanation of what you're doing. Specifically:
    What does this: "If I trying communicate with server from my PC (LVRTE) its works correctly." mean? What is the "server"? What's it running? What do you mean by your "PC (LVRTE)"?
    What does this: "However, when I am trying interchange client and server applications it appears with error 1" mean? What is the "interchange client" and the "server applications". Reading this implies you have more than one application running on the "server", whatever that is.
    Seeing some code wouldn't hurt either.

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

  • MAX giving error - Unable to locate Labview run-time engine

    I have LV 7.1 and 8.5.1 installed on a WinXP pc. No problems until now.
    I installed some support software for a LabJack  interface, which required LV version 6.1 run-time, so I let it install that.
    I now get the error whenever I run MAX:
    "Unable to locate the Labview run-time engine. LVBrokerAux71 requires a version 7.1 (or compatible) Labview run-time engine...."
    After closing the error boxes, MAX seems to work fine. Both versions of Labview also work. I uninstalled run-time engine 6.1 and re-installed version 8.5.1, but that made no difference. I tried to install run-time version 7.1 from the msi file but it would not let me because a later version of the run-time is installed.
    What is LV Broker? Why does it not accept version 8.5.1 run-time engine? Is it possible to have 2 versions of the run-time engine installed, and if so, how?

    Dear CDancer
    Thank you for contacting NI. First of all, you can have as many versions of LabVIEW run time engines you want loaded on your computer without a problem. LV Broker is installed by all drivers that uses LabVIEW testpanels like DAQmx does. In your case it seems that the LV Broker installation is corrupted or has failed. This can be rectified by overwriting the files in the specified directory listed below:
    C:\Program Files\National Instruments\Shared\LabVIEW Broker
    Your directory should look like the screenshot I have attached; labelled LV Broker Directory View
    I have attached a ZIP File that will replace the LV Broker directory. Please try replacing your files with these if different to the screenshot and let me know how you get on. Many thanks.
    Many thanks for using the NI forums and I look forward to your reply.
    Kind regards
    David
    Applications Engineer
    National Instruments UK
    Attachments:
    LV Broker Directory View.JPG ‏57 KB
    LV Broker.zip ‏413 KB

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

  • LabView Run-Time Engine 2009 installation failure

    Hi,
    I have problem to install Labview Run-Time Engine 2009.
    This error occur:
    Die Installation von NI VC2008MSMs x86 ist auf Grund des folgenden Fehlers fehlgeschlagen.
    Auf den Windows-Installationsdienst konnte nicht zugegriffen werden.
    Die kann vorkommen, wenn Sie Windows im abgesicherten Modus ausführen oder der
    Windows-Installer nicht korrekt installiert ist. Wenden Sie sich an den Support, um Hilfe zu erhalten.
    (The installation of NI is VC2008MSMs x86 failed due to the following error.
    The Windows Installer Service could not be accessed. That can occur when you run
    Windows in Safe mode or Windows Installer is not installed correctly.
    Contact your support personnel for assistance.)
    I've tried to reinstall and reregistrate windows installer, I've even tried to upgrade windows installer to version 4.5
    I've installed Microsoft Visual C++ 2008 Redistributable x86.
    Im runing Windows XP Service Pack 3
    (Microsoft Windows Version 5.1 (Build 2600.xpsp_sp3_gdr.100427-1636_ Service Pack 3))
    I have no problem installing other programs, I can for example install labview runtime engine 7.1.1.
    So my question is:
    How to solve this problem, how can I make an installation of Labview Run-Time Engine 2009 on this computer that gives me the error described at the begining?
    Best regards
    Simon
    Solved!
    Go to Solution.

    Hi,
    I have already looked at that forum issue.
    So I have already tried to delete all keys in regedit.
    The problem is, if I continue with my installation, about 10 other new issues will appear.
    And my installation will not complete, it will fail.
    The installer does not install, it will tell me that the installation failed, and it will only install a few things.
    Not all the things that I need to run my program.
    See attached pictures ibn zip file to see some errors I receive, I only picked a few of them out.
    So when I then tries to start my program I will recive the error in picture program error. (Run-time engine error)
    So it's not only that the installer tells me that the installation doesn't go through, it doesn't.
    Best regards Simon
    Attachments:
    Pictures.zip ‏414 KB

  • LabVIEW Run-time Engine 7.1.1 installation failure on Windows 7 SP 1 32-bit

    I am attempting an installation of LabVIEW Run-time Engine 7.1.1 on my Windows 7 SP1 32-bit OS computer and the installation hangs.  This happens near the beginning.  Is there a compatibility issue?  The window does not have any error messages.  It says: "Updating System, The features you selected are currently being installed."  The progress indicator blinks periodically, but does not move forward.  Please help.  Thanks!

    I recently tried to install the LabVIEW 7.0 runtime engine on my Windows 7 (64 bit) machine to try out an old software. Ended up removing it quickly again, since any LabVIEW version I started up after that, including LabVIEW 2013 showed an installation dialog on startup about (updating installation information, please wait!).
    Basically there are so many possible problems why it could fail. Apparently the runtime engine installer had played with some other NI component that he had no idea would ever exist when it was created and caused that component to always think it needed to update itself to finalize its installation. In your case it could be anything from a missing Visual C runtime version framework that the installer simply expects to be present but doesn't since Microsoft has in the meantime released about 5 versions of Visual C and doesn't install all runtime versions anymore on newest Windows. Or it could be a conflict with your hyper-duper .Net Framework 4.5.x.y that the installer does not be prepared for. Maybe that or something else was not present on your 64 Bit machine where you could install the runtime engine.
    Basically the reasons for the install to fail are legion, and trying to figure it out is always more hassle than moving on and let old software be old software.

  • LabVIEW Run Time Engine and ActiveX Automation Server

    Hi,
    I have a question related to LabVIEW Run Time Engine and ActiveX Automation Server:
    We have a tool developed in LabVIEW and TestStand. End user interface is a LabVIEW GUI (it's an executable) which executes TestStand sequences. Some TestStand sequences call lower level LabVIEW VIs.
    Everything works fine with LabVIEW installed, but I was wondering if I could run this tool on deployment machine with only LabVIEW run time engine installed. We are using LabVIEW 6.1 and with only the run time engine installed, I get the error message: "Unable to launch the 'LabVIEW.Application' ActiveX automation server ". 
    BTW, we are planning to upgrade the versions soon.
    Is it possible to make things work only with the run time engine?
    Thank you.

    Thanks for the response, Brian.
    I did upgrade to LabVIEW 8.0 and TestStand 3.5. Everything works fine on the development computer where LabVIEW and TestStand is installed. On the target computer in the lab, I installed LV RTE 8.0 and TestStand 3.5, and now when a VI is called in a sequence file, I get the following:
    RunState.PreviousStep.Result.Error.Code  -18002 
    RunState.PreviousStep.Result.Error.Msg  "LabVIEW: The VI is not executable"
    So, the executable opens and works fine (which means that the LV RTE is installed properly), but when a sequence calls a low level VI, it does not make it through.
    comments/suggestions are appreciated. Thanks.

  • Installer Error of LabView Run Time Engine 6.0.2 "premature"

    I cannot Install the LabView Run Time Engine on a Computer which runs on Windows 2000.
    The Installation breaks on start with the Error Message: "Installation ended premature, because of an Error!"
    Does anyone know what to do is ?
    Thanks for Help

    It's rather difficult to guess why since the error does not give any more information, but there are a few things you can try. First, if you are installing from a CD, try downloading the installer to your desktop first and then run it. CD-ROMs can sometimes run slower that the installer and this can cause problems. Also, check to see what other NI software may have been installed on this machine and determine if any of it could conflict with the 6.0.2 Run-Time Engine. Just possibilities but hopefully they can get you going!
    J.R. Allen

  • Are LabVIEW VISA functions supported by LabVIEW Run Time Engine?

    I have an executable file that I created using LabVIEWS Application Builder. When I run the application on another computer that does not have LabVIEW installed, it crashes with a Windows message stateing the my application has generated erros and will be shut down by Windows. I have isolated the problem as having something to to with VISA Reasource Names.
    Does anyone know if there has been any issues regarding the use of VISA function in LabVIEW Run Time Engine? The version of LabVIEW that I have is 6.0.2. The version of Run Time Engine is 6.0 .
    Dan

    Yes there are issues with the RTE 6.0 and VISA. Use the RTE 6.0.2
    LabVIEW, C'est LabVIEW

Maybe you are looking for

  • Third Party Apple Loops not being shown in Loop Browser.

    Hey Everyone! I posted this in the GB forum but nobody answered... maybe here someone can shed some light on this issue. I am a quite experienced user of GB, Logic and Soundtrack, and usually I find the workarounds for these kind of problems but I'm

  • Apple tv error code -3905

    I'm trying to set up apple tv for first time and cannot get it to maintain network connection for more than a couple of seconds. Get error code -3905. Any clues??

  • Command lines for compiling forms

    Hi all, I want to know if there are command lines producing the actions equivalent of Maj+Ctrl+K and Ctrl+T when we are working with a form. Thank you very much indeed.

  • Getting error with word wrap

    So this is the error im getting: Error: Error #1502: A script has executed for longer than the default timeout period of 15 seconds.           at flashx.textLayout.elements::FlowElement/getAbsoluteStart()[C:\Vellum\branches\v1\1.0\dev\ output\openSou

  • Lightroom hangs on editing Preferences

    Every time I try to edit the Preferences, LR5.4 (64 bits) hangs and Windows (8.0)  says that he will close the program. The rest of LR works fine (except editing with Nik plugins), so I do not know what to do. Any Clue? Agustin