Include run time engine exe

Hi
I woul d like to know how sould I have to do to include run time engine ni daq driver741 and my application in the same executable file truth  application builder?
thank you
Olivier

olivier66 wrote:
HI and thank you again
 I
just want to know if its possible to create the installer for win98
because aparrently if you clic on the tab advanced in the installer
properties you can only choose to build it for windows 2000 at least.
I guess it is not possible so Is there anonther way to do that?
thanks in advance
Olivier
LabVIEW 8 is only supported for Win2000 and XP. If you need Win98 support you need to stay with LabVIEW 7.x.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Similar Messages

  • How do I create installer that checks the available Run Time Engine on the target system

    Hi,
    I am looking for a soultion on custom Installer where this Installer once done with the Installation should be capable of checking the presence of Runtime Engine on the target system. I amaware of including/checking the LV RTE checkbox for such options and we are working on some other concept. The thing is we would like to give the user a pop-up or any message that shows the presence of Runtime engine on the target system after finishing the installation. In case the runtime engine is not already installed on the target system, this time the message will be for the link to get the .exe and close the installation. 
    Overall we would like to minimize the size of our Installer that in case will get increased if we include Run Time Engine along with the Installer. 
    I am also assuming that such checking can be done through Advanced Tab in the Installer properties by including any such .exe for performing those things but looking for more options if possible to get it done. 
    Please do let me know if someone has any idea about it. 
    Thnaks in Advance,
    Vivek

    Hi teststand,
    you can start another program which checks if the rte is available. It should also be possible with only a batch file.
    Mike

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

  • Include LabVIEW Run-Time Engine in C# Project Distribution

    I have written a software package in Visual Studio using C# which calls a number of functions from a dll which I have built in LabVIEW. I am now trying to produce an installation program for my C# package but can't quite work out how to include the LabVIEW Run-Time Engine in this installation.
    I am creating the installation program by defining a Visual Studio Deployment Project and I have added my LabVIEW dll to this. However, the dll requires the LabVIEW Run-Time Engine to also be installed on the target PC. I was hoping that there would be a set of files to implement the installation of the LabVIEW Run-Time Engine that I could include in my Visual Studio Deployment Project and do the installation of both my C# code and my LabVIEW dll (inc Engine) in one operation. Is this possible? Or do I need to produce a LabVIEW installation for my dll separately from the C# installation?
    Info:
    Development OS = Windows 2000
    Target OS = Windows XP
    C# Development Environment = Microsoft Visual Studio 2005 V8.0
    LabVIEW Version = 8.5
    Also, I am using the Order Analysis Toolkit and noticed that there seemed to be an 'Order Analysis Run-Time Engine' installed on my PC. Do I need this too?
    Thanks for any help.
    CAS

    Hi CAS,
    One way of automating the installation of the LabVIEW run-time engine is to use commands in a batch file (*.bat). These commands would be executed automatically at the same time as your distribution installer to install LVRT with your C# application. For more information on command line options, have a look at this KB. I don't have so much knowledge of C# distributions, though, so there may be a better way to approach this that someone else in the community could advise you on.
    With regard to the order analysis toolkit, you will also need this runtime engine installed. A point to note, though, is that the toolkit requires a run-time licence to be deployed in this fashion. It is now part of the Sound and Vibration Measurement Suite and needs to be licenced accordingly.
    I hope this helps!
    Best regards,
    Tom
    Applications Engineering, NI UK

  • Call VI in EXE but have it execute in Developmen​t Environmen​t not Run Time Engine

    I am working on building a palette editor for distribution of a reusable code library for my company (I know the VIPM does this very well already).  I have the code complete and am trying to create an executable that I can distribute that will call the code I wrote to update/create the palette .mnu files for the reuse library, which lives on the company network.  I am using the Palette Editing VI's and it seems as though they cannot be built into an executable.  So I wrote some code to dynamically call my palette modification code (I call it the Reuse Library Manager).  When my executable calls the Reuse Library Manager dynamically I get a broken run arrow on the Reuse Library Manager front panel and the following reasons for the broken arrow:
    It seems to me that the reason the Reuse Library Manager works when called in the development environment and not when called dynamically is because the dynamic call uses the run time engine for execution.  This made me think of how in the VIPM it opens LabVIEW while it installs packages.  If anyone knows, does the VIPM open LabVIEW in order to run the Palette Editing VI's or is it for another reason?  If it is this reason how can I force the dynamically called VI's to run in the development environment by opening LabVIEW programmatically from an executable that is running in the run time engine?
    Let me know where clarification is needed.
    Message Edited by jmcbee on 04-28-2009 10:00 AM
    CLA, CLED, CTD,CPI, LabVIEW Champion
    Platinum Alliance Partner
    Senior Engineer
    Using LV 2013, 2012
    Don't forget Kudos for Good Answers, and Mark a solution if your problem is solved.
    Attachments:
    Reuse.PNG ‏14 KB

    Hi jmcbee,
          In spite of years of using LV and building a resuable library of code, I've done very little with customizing the standard paletts, however,
    Many times when deploying a new distributable I've seen a dialog like what you posted.  In most cases the problem was solved by rebuilding distributable to include the missing VIs.  In one case I added the VI-lib to the target-platform and made-sure VI-lib was in distributable's VI search-path.
    There are two ways I know of to build distributables which include the VI-lib code,
    1) Include all VI-lib VIs when building the distributable
     - In LV 8x, uncheck "Exclude Files from VI lib" project-property.
     - In LV 7.1 it's possible but I don't remember how! (probably a post on it around here.)
     - This can add an enormous number of un-needed VIs (see this post.) 
    2) Re-write the VIs so that they are no-longer identified with VI-lib and get included "naturally".
     - Open each VI diagram, select-all, paste in new/untitled diagram.  In your case naming will be tricky, but it's doable.
     - This is a great advantage in 8x as it allows LLBs to be built with File\Save As\Create Hierarchy.
    In addition, here's a tool to call following "Open VI Reference" (if it returns an error.)  This VI open all broken children making it much easier to identify specific missing parts (typically VI-lib.)
    Luck/
    Cheers!
    "Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
    Attachments:
    Util.VI.OpenBroken.vi ‏57 KB

  • 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

  • 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

  • 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

  • Unable to locate labview run time engine (lab view 8.5)

    Hello I have a problem whit the labview 8.5 installer. I have created I project with included a .vi file (a simple panel wich control a serial port, with parameters (baud rate, stop bits, ...)), then I have created an application for this file (.exe) and then the installer (I have included the labview run time engine 8.5). When I run the setup.exe  I have the following error message:
    Unable to locate labview run time engine, the application require a labview run time engine 8.5 or compatible...
    What I'm missing??
    Thanks
    Maurizio

    are there one other reasons why it would not work.  I have asimilar problem.
    I intsalled version 8 of run time engine and acrtivated software.  Now I am trying to run compiled application provided to me by third party.
    When I click on application it says
    Unable to locate LV run time engine
    Test server requires a version 6.0 or compatible LV engine.
    How do I know if the engine I installed and activated is running and is it supposed to be able to execute a program which is expectin rev 6 of the rund engine?

  • Does the DAQmx drivers include LVRun-Time Engine?

    Does the DAQmx drivers include LVRun-Time Engine?
    1. I first installed LVRun-Time Engine 7.1.1 on a new PC.
    2. Then i ran the installer once again and selected remove to uninstall the program.
    3. Next I installed DAQmx drivers 8.0.1
    4. After this I tried to run my compiled labview.exe and it works fine(!)
    When I look in control panel - add/remove programs and select National Instruments software and press change, I can see that NI LabVIEW Run-Time Engine 7.1.1 is installed.
    Now why would version 7.1.1 be included in DAQmx 8.0.1?
    Question1: Was perhaps the LVRTE install refreshed by the DAQmx install?
    Question2: Is it not possible to completely remove installed software with the regular uninstall? I am trying to verify the install procedure as it will be on a fresh PC.

    The run-time engine is included with DAQmx. If you look at the distribution, there is a Products folder that has it. My guess is that it's included for something like VI Logger or even the test panels in MAX.

  • You may not need to install the Run Time Engine...

    I know this has been mentioned before, but after a long search of the archives, I couldn't find the right person to give credit to - sorry!
    If you have a simple exe, you may not need to install the runtime engine on the target machine at all - all you need to do is include some of the engine's files with the exe for it to work. Try it out: copy the following files & folders into the folder containing your exe:
    ..\National Instruments\shared\nicontdt.dll
    ..\National Instruments\shared\nicont.dll
    ..\National Instruments\shared\LabVIEW Run-Time\your_version\everything (including all sub-directories)
    so, using 6.1 as an example, you exe's directory would like something like:
    ..\AppDirectory\MyApp.exe
    ..\AppDirectory\MyApp.ini
    ..\AppDirectory\My_Apps_DLLs,if_any
    ..\AppDirectory\nicontdt.dll
    ..\AppDirectory\nicont.dll
    ..\AppDirectory\lvapp.rsc
    ..\AppDirectory\lvjpeg.dll
    ..\AppDirectory\lvpng.dll
    ..\AppDirectory\lvrt.dll
    ..\AppDirectory\mesa.dll
    ..\AppDirectory\serpdrv
    ..\AppDirectory\models\heaps_of_stuff_in_here
    ..\AppDirectory\errors\more_stuff_in_here
    ..\AppDirectory\script\and_some_bits_in_here_too
    Take all of this data to a machine without LabVIEW or the runtime installed, and try to run the exe - all going well, it will execute without any problems. This exe distribution method can be really useful, especially when distributing autorun presentations on CD-ROMs.
    * DISCLAIMER: as far as I am aware, this method is NOT authorised or supported by NI - use it at your own risk!
    cheers,
    Christopher
    PS: I'd like your feedback: please give this posting a rating
    Christopher G. Relf
    [email protected]
    Int'l Voicemail & Fax: +61 2 8080 8132
    Aust Voicemail & Fax: (02) 8080 8132
    EULA
    1) This is a private email, and although the views expressed within it may not be purely my own, unless specifically referenced I do not suggest they are necessarily associated with anyone else including, but
    not limited to, my employer(s).
    2) This email has NOT been scanned for virii - attached file(s), if any, are provided as is. By copying, detaching and/or opening attached files, you agree to indemnify the sender of such responsibility.
    3) Because e-mail can be altered electronically, the integrity of this communication cannot be guaranteed.
    Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

    Yes, this method is not supported. However, this method is good if you wish to write your own installer for a LabVIEW Application. (Note: The method above does not install DataSocket, NI-Reports, or any of the 3D Graph controls.)
    I would still suggest running the LabVIEW Run-time Engine installer so that more than one application can use it.
    Randy Hoskin
    Applications Engineer
    National Instruments
    http://www.ni.com/ask

  • LabVIEW Run-Time Engine

    Hi ,I have used Application Builder to make EXE file from my source files but I have noticed it is not possible to use this EXE file in another PC without LabVIEW because LabVIEW run-time engine is needed so I tryed Installer
    but I have few questions and I would really appreciate if u help me
    1- What kind of source files should be added to the installer?  I would like to install an EXE file and Data folder  so do I need to first use the application builder to make the application then add all the application files(EXE and Data folder) one by one to the installer or Do I need to add my LV files to the installer and LV make exe and data folder again for me?
    2- I am using LV2010 and I would like to add run time engine for 2010 so I checked the box for LV2010 run time engine but many options are included to this engine like NI TDM,NI SSL etc ... and after making the installer I noticed the size of my file was so big (109MB) while I want to make a small size installer for email   .Is there any chance to reduce the size of installer by unchecking some of the options?
    Many thanks

    You build an executable first, then you build an installer for the executable. When building the installer, simply add the executable and LabVIEW will figure out what else is needed in the typical case.
    If you want a small installer, don't include the run time engine. Instruct your customers to donwload and install the free runtime engine from here.
    Make sure they install the "standard", not "minimum" version. Also make sure they install the 32 bit version if your LabVIEW 32 bit, even if they install it under a 64 bit OS.
    LabVIEW Champion . Do more with less code and in less time .

  • 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

  • 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

  • Necessity of a run time engine

    Can anyone tell me whats the detailed concept behind the necessity of installing the labview run time engine along with a labview application to make it work?
    veena.

    "Veena" wrote in message
    news:[email protected]..
    > What i wanted to know was what does a run time engine exactly does and
    > whats its necessity? I havent explored the versions compatibility
    > parts...am new to labview and exploring various things theoretically
    > and practically, since I cant find a particular place or book that
    > gives a overall view, and theres only manuals available for now...
    > Veena
    I'm taking a guess here, Labview is an interpreted language and that means
    it needs something to convert the labview code into machine instructions,
    the converter is the Labview runtime engine.
    I think even if you create a *.exe file you need the runtime engine to run
    it. I don't have the full d
    evelopment version though so don't quote me on
    that.
    If you look in the help index for run-time engine you will find this answer
    "Using the LabVIEW Run-Time Engine
    If you create a system using LabVIEW that runs applications or shared
    libraries, then you must install the LabVIEW Run-Time Engine. The LabVIEW
    Run-Time Engine includes the libraries and other files necessary to execute
    LabVIEW-built applications and shared libraries. All client computers
    running LabVIEW-built applications and shared libraries must also have the
    LabVIEW Run-Time Engine installed.
    The LabVIEW Run-Time Engine also includes a browser plug-in that allows
    clients to view and control VI front panels remotely using a browser.
    All applications and shared libraries built with a particular version of
    LabVIEW will share the same LabVIEW Run-Time Engine installation, so only
    one installation is required. If you use applications or shared libraries
    that you create with different versions of LabVIEW (for example, 5.1,
    6.0,
    and so on), you must have the Run-Time Engine for each version of LabVIEW
    installed on the system.
    You can find an installer for the LabVIEW Run-Time Engine on your LabVIEW
    CD. "

Maybe you are looking for