NI-DAQmx Run-time Engine

Is a run-time version of the NI-DAQmx v8.6 driver available yet? I'm distributing an application from LV 7.1 that requires DAQmx and want to include this as part of the installation. I found run-time packages for v8.3 but I'm using v8.6 in my development work so hate to switch to an older version. Are there any compatibility issues in using v8.3? Thanks.
Art

HI Paul,
Thanks for your suggestions. Just prior to receiving your response, I had in fact tried to build just an installer for the daq driver from LV 8.5. The problem is that it forces the project to be saved before it will create and installer and then proceeds to include the empty project and the LV runtime engine. In my case, I named the project test and the installer created c:\test on the target and installed the LV runtime as well as the daq driver. I also ended up with a regiestered application - test. Once I manually uninstalled test, I had the result I wanted, but too long a path to get there.
I bit the bullet and migrated the code from LV 7.1 to LV 8.5 so that I could build a comprehensive installer. Generally, things turned out well. My biggest question is why the application builder / installer insists on putting both LV 8.2 and 8.5 RTE on the target. I want, and expect, only LV 8.5 RTE. I'm have installed and am running off of the 3rd Q release for the NI developer suite. Why is 8.2 RTE loading and how do I correct this?
Another strange result is that my daq device and channels do not show up in MAX. I included the level 5 daq driver and MAX in my installer as well as the hardware configuration. The application works ok, and if I manully import from my *.nce file then I get a warning that my device will be replaced. Is this normal? The GPIB controller shows up as normal. The only thing that seemed odd during installation was that the daq driver didn't complete installation after restart because I forgot to plug in the daq device cable. Afterward it seemed ok.
I also have a couple of bugs with the application builder / installer. I converted my LV 7.1 build script and made needed changes. I see the following behaviors.
1) I have setup a file to install into a subdirectory. Every thing works ok except when I subsequently go back into the Installer Properties window and go to the Source Files. I see two problems. First, in the Project View my files are in the correct locations, but the icon for the one in the sub-directory is switched with the very last one in the list. Second, in the Destination View the next-to-the-last file from the Project View is the one shown in the sub-directory while the file that should be in there is listed directed below it in the list (but not in the sub-directory). Everything installs to the correct location, but this maked it very confusing to edit the installer.
2) Whenever I use the Build All command, the application builder fails with the following error. If I start the build individually from the Properties window, then the build completes successfully.
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 1 occurred at Copy in AB_Engine_Copy_Error_Files.vi->AB_Application.lvclass:Copy_Error_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW:  An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488:  Command requires GPIB Controller to be Controller-In-Charge.
C:\Program Files\National Instruments\LabVIEW 8.5\user.lib\errors\McPherson-errors.txt
Thanks again for help.
Art

Similar Messages

  • Is there a redistribu​table for the Core NI-DAQmx Run-Time Engine?

    Also, is there a silent installation option?

    Hi,
    I'm not sure what you mean about a redistributable, but you can download the DAqmx core run-time engine here: http://joule.ni.com/nidu/cds/view/p/id/3812/lang/e​n
    You should be able to do silent install by following this KB: http://ae.natinst.com/public.nsf/web/searchinterna​l/188FE05BA8933F4486256BC300708527
    Trevor B.
    PSE
    National Instruments

  • 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

  • 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

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

  • LV8 without run-time engine?

    I am using a LabVIEW 8.0 development system. I built a project and want to build a installation build to install the application. However, when I tried to add Labview 8.0 run-time engine to the installation build (In BuildSpecification->Additional Installers), Labview prompts me that my machine does NOT have a Labview 8.0 run-time enine, and the selection for NI Labview 8.0 run-time engine is RED!
    How could this be possible? I have a Labview 8.0 development system, and labview tells me that I don't have Labview 8.0 run-time engine? What's the reason for that?

    Hi Lylee,
    This can occur when the project and build spec are created on a different machine with a slightly different version of the runtime. You should have another 8.0 runtime listed under the additional installers that is not red. You can then uncheck the "red" 8.0 runtime and check the normal one. The reason the one you have checked now if red is because that is the version the build spec is looking for but it does not exist on the system.
    For example, if I make a project and build spec that had DAQmx checked as an additional installer, then opened the project on a machine that did not have DAQmx installed, DAQmx would still be checked and listed under additional installers but it would be red.
    If you do discover that somehow your system does not have the Run-Time Engine installed, you can download those here.
    David_B
    Applications Engineer
    National Instruments

  • Run time engine, Error of type 1002208

    Hi,
    I want to build an exe  using LV 8.6 development (project builder).    When I finished the project in LV8.6 development, it works ok.  But When I copy the project (include the exe file) to the computer installed only run-time engine (standard) and Measurement & Automation Explorer, V4.0.0.3010, The screen indicates "  VI has an error of type 1002208, The full development version of LV is required to fix the errors."    Is there anything wrong when I build the application?  Thank you.
    Hsien
    Solved!
    Go to Solution.

    Hi Dennis,
      When i built the application, I didn't build an installer into the project.  I pretty much followed the HELP in LV 8.6 example: Build a stand-alone application.
    The vi is mainly to read the TC signal and voltage signal from the computer connected to a scxi-1000 chassis and modules (scxi-1102 etc.)    Yes, the vi called the sub vi (like DAQmx  Created Channel [AI Temperature-Thermocouple].vi; DAQmx read.vi etc.).  When I built the exe file, I have placed these vis into "always included" under "source file" category.  Thank you.
    Regards,
    Hsien

  • Error involving Report Generation Toolkit and Labview Run Time Engine

    Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??

    I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.
    Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?
    I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.
    I displayed my App.Property of APP.DI
    R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?
    Any ideas ?
    Greg Klocek

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

  • LabVIEW 2011SP1 Error building installer: LabVIEW Run-Time Engine 2013 is missing 3 dependencies???

    I'm having a problem building an installer in LabVIEW 2011SP1.
    It's been a while since I've tried to build an installer but it used to work fine and building executables is still working fine.
    Now when I try to build the installer I get "The build was unsuccessful."
    Possible reasons: Error generating preview for My Application 3.1.7.
    Details:
    Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
    CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_InitializeDistribution.vi >> IB_MSI.lvclass:Report_Preview_Error.vi >> IB_Source_Container.lvclass:Report_Preview_Error.vi
    Loading product deployment information
    *** WARNING ***
    NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing.  Visit ni.com/info and enter the Info Code "" for more information.
    *** Error: An internal error occurred for which the cause is unknown. (Error code -41)
    *** Error Details:
    Error in MDF API function: _MDFCommon_GetNextLogMessage
    Error in MDF::GetInstance - MDF static instance is not initialized!
    *** End Error Report
    Loading product deployment information
    *** WARNING ***
    NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing.  Visit ni.com/info and enter the Info Code "" for more information.
    The really strange thing about this is that I'm using LabVIEW 2011SP1, I don't even have LabVIEW 2013 installed, not even the runtime.
    Where is the problem? Why is it even complaining about LabVIEW 2013? Has anyone seen this before?
    Troy
    CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
    I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
    Beware of the man who won't be bothered with details. - William Feather
    The greatest of faults is to be conscious of none. - Thomas Carlyle
    Solved!
    Go to Solution.

    I do have the LabVIEW 2013 discs but didn't install it.
    I checked in Control Panel > Programs and Features > National Instruments Software and the LabVIEW 2013 Run-Time is not listed there.
    I also checked in MAX > Software and I must have missed it the first time I looked. LabVIEW Run-Time 2013 is listed there after all.
    Now I remember installing VISA 5.4 to get rid of a nasty bug. It must have installed the 2013 Run-Time when I did that.
    So now I need to distribute 2 runtimes with my application?!?!
    Troy
    CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
    I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
    Beware of the man who won't be bothered with details. - William Feather
    The greatest of faults is to be conscious of none. - Thomas Carlyle

  • Unable to run vi with labview run time engine

    Hi All,
    I have a VI that controls and reads from an NI PXI Spectrum Analyser (5600). The VI works perfectly as expected, I can make a project of it and create a runtime application and installation with no problems, using Labview 8.6.
    When I make a call to it from Test Stand 4.1 it works lovely.
    When I change the VI adaptor in Test Stand 4.1 from development to use the LV Run Time engine 8.6 it fails to work, Test Stand gives the following dialogue (see attached).
    I have uninstalled all older versions of Labview as I've had similair issues before, I've mass compiled everything I think is associated with this VI.
    I don't really understand! And am tearing my hair out.
    The only idea I have is that perhaps there is something in one of the 5 DLLs that is causing a problem or the NI_AALBase.lvlib, NIAALPro.lvlib or NI_PtbyPt.lvlib librarys that are password locked and I presume don't get mass compiled.
    I have attached the problemVI.lvproj.
    Thanks for any advice or help.
    Matt
    Attachments:
    problem VI.lvproj ‏41 KB
    teststand.JPG ‏43 KB

    Matt,
    it sounds like you are having older versions of toolkit/driver VIs in your application. In developement environment, this works since the dev-system is capable to recompile older VIs just during loading and therefor not having issues with older versions.
    Running the VIs using the Runtime Engine, recompilation is not possible. Because every VI knows "its version", the VI will not be executable unless the RTE version matches the VI's. If the VI is older (or newer, doesn't matter), the observed error occurs.
    Please make sure that you have current versions of drivers and toolkits installed in your LV environment instead of simply copy them from older versions of LV (this would be the common source for such issues).
    hope this helps,
    Norbert 
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • Run-Time Engine error

    I have created an automated test and had it running as an executable on a stand alone test computer. I updated my LabView software to 8.6.1. I just made some changes to the test and recompiled it. When I tried to run it on the stand alone computer it gave me an error about the LabVIEW 8.6.1 run-time engine missing. I thought when the project was built all the files that pertained to running it were also built into the folder. Has anyone run into this that could offer some advice.
    Thanks
    Chirs
    Solved!
    Go to Solution.

    Did you create an installer or simply build the exe? If you only built the exe you will need to install the run-time engine on the target machine. If you created an installer you can include the installation of the run-time engine as part of the installer.
    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

  • VISA Write differs between TS Development System and LV Run-Time Engine

    Hi all
    I made an application on LabVIEW to test BERs (Bit Error Rates), and I used VISA Write between two COM ports to exchange data.
    Everything works fine using just LabVIEW.
    Afterwards, I used TestStand to call my application (VI). The LabVIEW adapters from TestStand were set to Development System by default, and everything works OK!!
    Finally, I needed to disable the development system, and set the LabVIEW adapters from TestStand to LabVIEW Run-Time Engine and I notice that the speed of the data exchange between the two COM ports decreased dramatically.
    The only difference was the speed...because all the data (changed slowly in this case) arrived correctly on the other COM port too.
    The symptom was the same as decreasing the baud rate...but the baud rate and all the other configurations remained the same. The only difference was the change between Develpment System to Run-Time Engine to notice this decreased speed between the exchanged data using VISA Write.
    Any solutions for this?
    Thanks in advance
    Joao
    Solved!
    Go to Solution.

    Joao,
    you state that using the LV Developement System as execution platform for your LV code modules result in faster datatransfer between the COM ports than using the LV Run-Time Engine.
    So i am pondering: Does this refer to TS at all?
    Please check the following:
    Run you communication using a sole LV application in LV Developement System. This should be fast. Now build an executable of this application and run that one. Do you see the same behavior?
    If there is no difference in a sole LV approach, there have to be some settings in the TS approach making this slow. So please let us know:
    Are there different modules involved in that data transfer (which in fact points to the reply Christophe made)?
    What about loading/unloading options of the modules?
    How big is the hierarchy of the modules, e.g. is it necessary for the RTE to load stuff the Dev Env has already in memory due to loading a lvproj.......?
    Could you provide a simple example sequence+modules showing this behavior?
    What versions of LV and TS are you using?
    hope this helps,
    Norbert
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • 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

  • 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

Maybe you are looking for

  • Error with concurrent users- Activation Passivation Bind variable ?

    I have a programmatic view object based on procedure call that returns a ref cursor. Application Module has a function that exposes get Method for this View object using client interface. Everything works good until many users call the same Method ,f

  • HT3924 Target Display mode screen direction

    Can anyone advise on how to change the direction of screen link whilst in Target Display mode? My lap top sits to the right of my iMac due to the length of Thunderbolt. Screen link goes from right of laptop to left of iMac, would like to swap to left

  • What is a system memory "page out"?

    I heard that looking at "page outs" in activity montor (under system memory) is a good way to know if you need more ram. Can someone explain what a page out is? What % of page outs represent a problem?

  • HT4993 How do I unlock a sprint Iphone to a tmobile

    I recently got a sprint Iphone 4s and I think it's unlocked because it doesn't say sprint on it and I tried using a tmobile sim card but it doesn't work, can anyone help please? thanks

  • Another Master/Slave question HELP!

    Hey gang. So you guys answered my original question of replacing the original hard drive in my G4 AGP Sawtooth. Thanks again! My next question concerns the whole Master/Slave aspect. The 2nd internal drive I put in several years ago is a Maxtor 120 o