Witch runtime engines must be included (COM acces)

I have made a program that gets a pressure value from an external pressure gage. This signal is transferd to the PC by the COM-gate (RS232) and at the development system (The PC where I have made the application) it works great.
However if I make a executable and execute this one on a nother computer I get a communication error (the error coms out of my software, but sinces in that there is none communication)
Do I have to install a extra runtime engine to be able to acces the com gate with labview? (I have checked that I used the right COM, and the problem occured at 2 different PC's)
Please help me!

They're on the Additional Installers tab:
Attachments:
LV_additional_installers.png ‏104 KB

Similar Messages

  • NI VISA Runtime engine

    When "Building" a LabVIEW program containing NI-VISA sub VI's (e.g. to communicate with USB), I have had problems getting the "Built code" to find my NI VISA devices, even though the NI VISA USB  Drivers are correctly installed on the "target machine".
    (The "built" code WILL run if the target machine has a LabVIEW installation on it, including NI VISA)
    So - will the NI VISA runtime engine be automatically included in the "Build" (Because of the NI VISA sub VI's), or do I have to specify this myself - And how?
    Thanks. Peter.
    Solved!
    Go to Solution.

    You specify installing the NI VISA Runtime Engine when you build and installer for your built executable. Look on the Additional Installers tab of the Installer Properties Dialog Box.  The NI VISA Runtime Engine should be selected automatically but if it's not you can uncheck the Automatically select recomended installers checkbox and select any other installers you want to include in your install.
    If you're not using an installer then no runtime engines are installed and you'll have to do that manually on each machine you copy the executable to.
    This all assumes LabVIEW 2013.  The selection process is slightly different in earlier versions but all the options are still available.
    Kelly Bersch
    Certified LabVIEW Developer
    Kudos are always welcome

  • Installer Build Error using LV Runtime Engine 2010

    I had an executable and installer working that were built in LV2009.  Since then I modified my source code and saved as LV version 2010.  I rebuilt the executable, but when I tried to run it on the target computer, I got an error message saying that LV Runtime Engine 2010 was needed.  So I tried to rebuild the installer using LV Runtime Engine 2010 as an Additional Installer.  However, this build was unseccessful and I got a lenghty error msg that I don't understand (see attached).
    Thanks in advance.
    Solved!
    Go to Solution.
    Attachments:
    Installer Build Error Message.docx ‏13 KB

    Hello,
    I am building an installer with LV2010 SP1. I have added the runtime engine to be included in the installer. I get the following error 
    ------------------ERROR MESSAGE-----------------------------------
    CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> AB_UI_FRAMEWORK.vi >> AB_UI_Frmwk_Installer.lvclass:Build.vi >> Installer.lvclass:Build_from_Wizard.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi
    Loading product deployment information
    Adding files to installer
    Done adding files
    Preparing to build deployment
    Copying products from distributions
    Copying distribution 'PSUTS' from: C:\CBESVN\PSUTS\Software\builds\PSUTS Installer\Volume\ to: C:\ProgramData\National Instruments\MDF\ProductCache\
    *** Error: Windows SDK function returned an error. (Error code -12)
    The system cannot find the path specified.
    *** Error Details:
    Error in MDF API function: _MDFDistCopyList_CopyItem
    Windows function FindFirstFile returned an error. Error code: 3
    *** End Error Report
    Done building deployment
    CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> AB_UI_FRAMEWORK.vi >> AB_UI_Frmwk_Installer.lvclass:Build.vi >> Installer.lvclass:Build_from_Wizard.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi
    Loading product deployment informationAdding files to installerDone adding filesPreparing to build deploymentCopying products from distributionsCopying distribution 'PSUTS' from: C:\CBESVN\PSUTS\Software\builds\PSUTS Installer\Volume\ to: C:\ProgramData\National Instruments\MDF\ProductCache\ ***************** Error: Windows SDK function returned an error. (Error code -12)The system cannot find the path specified.
    ***************** Error Details:Error in MDF API function: _MDFDistCopyList_CopyItemWindows function FindFirstFile returned an error. Error code: 3*** End Error Report************** Done building deployment
    --------------------MESSAGE END------------------
    In the additional installer page: I see the installer source location (see attached image file) as 'C:\CBESVN\PSUTS\Software\builds\PSUTS Installer\Volume' which is really my installer's source location. But I am not sure how this location got assigned. I have tried to create new build spec from the same project, still the installer source location stays the same. How do I get this issue solved?
    Attachments:
    Additional.jpg ‏174 KB

  • USB/Serial Drivers and App Builder Installer Questions...are drivers included in the Installer with the LV runtime engine?

    Hello all,
    I'm wondering if someone can help me out with how drivers and all are treated with applications distributed with App Builder, used to create a stand alone, full install of app and labview engine with Installer.
    What has happened  is, my application was created using the NI branded USB to RS232...and USB to RS485, and they work great.
    On the application when running..you fire it up, it finds the USB to serial device, and I have a dropdown that finds the available COM ports to use (along with setting parity, etc).
    I've installed on different computers (without previous labview installs) with the installer. They all worked.
    The customer has received the installer....and despite us telling them to use the NI branded USB/Serial interfaces..they are trying to work with a different USB/serial cable.
    They say the COM ports aren't even showing up when they run the installed application.
    So, I'm not sure where to start. Is this a driver issue?  Does the App Builder Installer...install the drivers for the interfaces I was using with it? Is there a way for the person to find and install a driver on their own...or would I have to somehow find out a driver for what they use....then, basically redo the App Builder Installer build...to include that driver with the executable I send back out?
    I guess I basically need a better understanding of how drivers for external access/communications are handled when you use App Builder to create a stand alone application complete with the labview runtime engine...and nothing else.
    Thank you in advance,
    cayenne

    The main thing is that LV uses VISA to talk to serial port whether native on the machine or from USB dongles that you plug into the computer. It sounds to me like their dongles aren't working.
    Can the customer see the ports in the Windows Device Manager? Can they access them through something like hyperterminal? How does your program find the USB/Serial devices?
    Mike...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • Can visa runtime engine be included in application build?

    I just installed my program on a new machine and it wouldn't work. Turned
    out I needed to also install the visa runtime engine. Is there any way to
    automatically include that in the application build?

    I've seen that you can tick of under the "additional installers" that Visa runtime is included, however, this will look for the installer files on the CD's. Is there a way to update this ? (I have 4.0 on the disc, and would like to included 4.2 in my build for installation/deployment.
    The file I download from NI is a .exe, but the linking to the build configurator is some strange windows code (see attached screenshot)
    /Brian
    Attachments:
    screenshot 13-08-2007 17.57.JPG ‏95 KB

  • How do CVI7.0 runtime engine and TestStand3​.0 runtime engine work in a test system?

    I developed code modules from CVI 7.0, and test sequence from TestStand 3.0. Now I want to deploy all to a test system. Should I create distribution kits for CVI and TestStand, and install to a target PC? Do each kit include the RTE? How do the runtime engine work in a system?

    hp7550,
    I saw your post earlier entitled "what is a run-time engine?". It looks like this post is addressing the same issue.
    To answer your questions, it is not necessary to create a distribution kit for your CVI code modules. You can simply install the CVI Run-time Engine, which you can find if you go to www.ni.com and click on the Drivers and Updates link on the left-hand side.
    Then you will need to deploy your TestStand system using Tools >> Deploy TestStand System in the Sequence Editor. That tool will go out and gather all the CVI code modules your sequence calls - unless you are calling a DLL or something dynamically inside of a code module; in which case, you need to add that dynamically called DLL (or code module) to your TestStand workspace.
    To install the TestStand Run-time Engine, make sure the Install TestStand Engine option is checked on the Installer Options tab of the deployment utility. You can customize what gets installed with the engine by clicking on the Engine Options.
    For more information on deployment, see Chapter 14 of the TestStand Reference manual (Help >> Search the TestStand Bookshelf...).
    To answer your last question a run-time engine simply gives you access to the compiled code that corresponds to the functions you used from the CVI or TestStand libraries during development.
    I hope that helps.
    Best Regards,
    Matt P.
    Applications Engineer
    National Instruments

  • What is needed to run a .llb file using a runtime engine?

    I would like to run a .llb file on a computer that doesn't have LabVIEW installed. Is that possible? If so, what is needed to do that? I have tried to install a runtime engine, but can't get it to work. The .llb file is currently running on LabVIEW version 6.0 on another computer, but I don't know with what version of LabVIEW the .llb file was created. The computer on which I would like to run the .llb file has Windows XP.
    Thank you for any help!

    Mathan wrote:
    You have to create an executable with the help of project explorer.
    The user has LabVIEW 6 (as he noted in the original message). LabVIEW 6 has no project explorer.
    To OP: I am assuming the LLB contains a top-level VI that can be run. Otherwise, this is a moot question. If you want to open the VI and view it, then you need the development version on the target machine. If you want to run the top-level VI in the LLB then you must create an application that you can copy over to the other computer. The other computer requires the LabVIEW Runtime Engine in order to run the executable.  To build the application you need the Application Builder. This is a separate product from LabVIEW, but was included with certain LabVIEW editions.. If you do not see a menu option for building the application then you do not have the Application Builder. You would need to contact your local NI sales office to see if you can still buy a copy. I doubt you will be able to, but it's worth a try. 
    EDIT: Sorry for the duplicate info. I got sidetracked while composing the message, and did not see the additional responses from Dennis.
    Message Edited by smercurio_fc on 08-18-2009 09:51 AM

  • Labview 8 Application Builder and VISA Runtime Engine

    Hi,
    I am using Labview 8 Application Builder and everything is working fine except for 1 small thing. My program makes use of some of the VISA functions and when I build the application I'm having to include the VISA Runtime Engine Installer as a separate item on the CD to make the .exe file work.
    What I would ideally like is for people who want to use the application to run the installer and that all necessary components (including the VISA Runtime Engine) are also installed in the one installation. At the moment they're having to do 2 installations and I would like to streamline this.
    Is this possible?
    Ken

    Hi,
      this How-To explains about making those selections and including the different drivers :
    http://zone.ni.com/reference/en-XX/help/371361A-01/lvhowto/add_installers_to_build/
    and this tutorial covers the screenshots a little more step by step.
    http://zone.ni.com/devzone/conceptd.nsf/webmain/5ADBC06AC32E508A8625706E0062EBD1
    Hope that helps
    Sacha Emery
    National Instruments (UK)
    // it takes almost no time to rate an answer

  • Distribute CVI runtime engine without the installer ?

    Customer wants to distribute CVI runtime engine with their application in VB.net.
    They don't want 2 installer (one for VB.net, one for CVI).  They want to extract the files out of CVI installer, and included in VB installer.
    Any one did this before?
    For CVI 2013.
    TIA.
    George Zou
    http://webspace.webring.com/people/og/gtoolbox

    I use CVI and deliver CVI dll to customer.
    I don't create installer.
    Customer don't want installer.
    They use VB.net, they create their own installer.
    And they don't want to call CVI Run Time Engine installer.  That's the problem.
    George Zou
    http://webspace.webring.com/people/og/gtoolbox

  • Installer build wants wrong runtime engine

    LabVIEW 8.6
    Windows XP Pro
    When I build the installer for my application, it wants me to have available the install disk from November 2007.
    Expanding the list for that disk, I find that it wants the runtime engine for version 7.1.1.
    If I remove NI-DMM 2.9 from the 'National Instruments Installers to Include' list in the Installer Properties, the error goes away.  The description for that installer indicates it comes from the August 2008 device drivers disk.
    At one time I had other versions of LV on the computer.  I have removed all other versions, including the directories in c:\Program Files.
    My application uses the DMM device driver, so I assume that I need to check the box for the additional installer.  I've looked for more documentation on when and why I should select different items in the list, but couldn't find anything useful.  Would it be possible for the installer to automatically select those items required and perhaps let me direct it otherwise by choosing fewer or more items?
    Bottom line, do I need to select the DMM driver to ensure that my application will run on a computer that doesn't have LV installed?
     - les

    Hello all,
    I couldn't really understand what was doing on in the above questions and answers but from the forum topic I believe I am in right place. I have an issue similar to those desscribed above. I have LabView 8.6.0 installed on my computer but when I run LabView it starts asking for 'NI LabView Runtime 7.1.1'. I tried feeding in the labview 8.6.0 but it doesn't accept it and keeps asking for 7.1.1.
    The program used to run fine couple of months back and I then didn't use it for a while and I had other prgrams installed durig this time. And when this month I tried to use LabView it started giving me this trouble. I don't know what went wrong. I installed some ftdi chip drivers also. So, I am thinking if that kind of messed things up.
    Also, I have this windows installer message come up sometimes which is not when I open LabView but some other programs. I don't know if this windows installer has to do anything with it.
    Whatever the case it is could someone please help me figure out how I can get the right runtime work for my LabView 8.6 and if also possible how i can get rid of this windows installer message. I don't remember the error code right now because it comes up randomly. Next time I see it I am going to save that number. But in the meantime if anyone can help me with LabView 8.6. runtime engine problem.
    Thanks,
    Lovepreet

  • Runtime Engine 7.1.1 Disk 2 when starting Labview

    I have labview version 8.2.1 installed on my computer.
    The other day I installed some application by another company that must have installed Labview Runtime Engine 7.1.1 on my computer.  I didn't need that program anymore, so I uninstalled it. 
    Now anytime I try to run any labview programs on my computer, I get several dialog boxes wanting me to put NI Labview Runtime Disk #2 in my CD drive.
    How can I get rid of these dialog boxes?
    Please help!!!

    Hi bkundework,
    This issue seems very strange but I do have a few suggestions. The first idea that comes to mind is to repair LabVIEW 8.2.1 from Add/Remove Programs. If you no longer have the 8.2.1 disks or if a repair does not work, you should install the LabVIEW Run-Time Engine 8.2.1. This download is available on NI’s website.
    These two ideas are the easiest ways to possibly fix things. If they don’t, a list of all the NI Software you have installed would be helpful for going forward.
    Charlie M. CLD

  • Runtime Engine 8 & Application deployment

    Can anyone direct me to a kbase article on the correct way to deploy applications using the latest runtime engine?  
    My first application said it was missing one of the libraries used to create the VI - why wouldn't the build include any VI's in the program etc? 
    I could use a good tutorial or article explaining the correct steps etc.
    thanks!'
    m 

    Found solution to my own problem
    Best practices:
    http://zone.ni.com/devzone/conceptd.nsf/webmain/BBE67528EBCA22B7862570700077EBB9#9
    Using application builder:
    http://zone.ni.com/devzone/conceptd.nsf/webmain/5ADBC06AC32E508A8625706E0062EBD1

  • Runtime Engine installer spawns from unrelated software

    Hello all,
    When I run a completely unrelated app (Quickbooks timer, in case you're wondering), Windows Installer launches and attempts to install LabVIEW 7.1 runtime engine. Has anyone else encountered this, and why would it occur? Is there an easy solution besides installing the runtime engine?
    Thanks

    Hello CT_JIM,
    We are probably seeing this behavior because your application (Quickbooks Timer) is querying Windows to confirm that all MSI installers are installed properly. In this case some part of the LabVIEW RTE must not have been installed completely and Windows is trying to correct it.
    This can typically be resolved by reinstalling or repairing the RTE to fix the install.
    Please let me know if you have any questions.
    Regards,
    Matt F
    LabVIEW Run-time Engine Version 7.1 for Windows 2000/NT/XP
    Keep up to date on the latest PXI news at twitter.com/pxi

  • Runtime Engine Redistribution Options

    I noticed that when developing Crystal Reports for Visual Studio 2010, one must install the Crystal Reports runtime engine in the client machines in order for the reports to work.
    According to the documentation, the runtime engine can be installed by executing any of the following files as appropriate:
    CRforVS_redist_install_32bit_13_0_1.zip
    CRforVS_redist_install_64bit_13_0_1.zip
    What I am curious about is if this is the only way to install the runtime engine or if there are other ways. For example, what if someone purchased the full version of Crystal Reports 2011? How would you deploy the runtime engine to the client computers in this case? Is the runtime engines for the full version the same as the one that comes with Visual Studio 2010 runtime engine?
    Most importantly, if there are two engines, what would happen if both engines are installed in the same computer?
    Thanks.

    Hi Rene,
    As far developing the Reports with CRVS2010 is concerned you would require Visual Studio 2010 and then install the following
    http://downloads.businessobjects.com/akdlm/cr4vs2010/CRforVS_13_0_1.exe
    The other you mentioned should be used when deploying the application. You can learn about it here.
    Crystal Reports for Visual Studio 2010 - Deployment
    If you purchase CR2011, you can design the reports, but it does not contain .NET runtime. You would have to use CRVS2010 runtimes. Do look at this.
    So, what's up with CR 2011 and .NET SDK - actually, any SDK?
    Two engines shouldnu2019t be a problem as each of them would have different version.
    CRVS2010 (13.x) and CR2011(14.x)
    Thanks,
    Saurabh
    Edited by: Saurabh.Pathak on Nov 3, 2011 8:30 PM

  • Customizable Runtime Engine

    Hi,
    I am using LabVIEW 8.6 and I am interested to understand how to customize the LabVIEWRun time engine. Basically to shrink its size.
    I just create a sample program and installer with and without Runtime Engine.
    The VI and the projec is attached.
    The Sizes are,
    VI                                               ->      6.9 KB ( Just a UI with a loop)
    EXE                                            ->  151.0 KB 
    Installer without Runtime Engine    ->   10.4  MB  
    Installer with Runtime Engine         ->   74.7  MB
    I understand the Rutime engine includes the support for all the LabVIEW features (Web service, trace, tdms, etc).But while distributing the application developed in LabVIEW we may need the support for only the features the Application developed/configured for. Right?
    Though transfering a 100 MB is not a problme now a days, I am just wondering, how it can be customized.
    Thanks,
    Pandiarajan R
    Certified LabVIEW Architect
    Attachments:
    RTE.zip ‏122 KB

    Pandiarajan wrote:
    I understand the Rutime engine includes the support for all the LabVIEW features (Web service, trace, tdms, etc).But while distributing the application developed in LabVIEW we may need the support for only the features the Application developed/configured for. Right?
    Though transfering a 100 MB is not a problme now a days, I am just wondering, how it can be customized.
    Besides the options then you create the installer no. I think NI could have done it, but they do not dare. If the installer was more modular it would have resulted in a lot of extra support work for NI. As people hate to read read documentation. It is much more convenient to phone NI support and yell at them. So NI has taken the all or nothing approach. As a self defense. And I can not blame them. But I have to admit a modular RT setup would have been nice.
    Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
    (Sorry no Labview "brag list" so far)

Maybe you are looking for