VI backwards compatibility with older run-time Engines

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

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

Similar Messages

  • Will hardware drivers work with the run-time engine or only a full version of Labview?

    Hello.
    I'm trying to get a quatech I/O card to work. The instructions with the drivers we were given state "you must have labview installed before installing these drivers".
    A program I wrote on my machine works fine with those drivers and does toggle outputs on the card, but when I build it into an executable on our test unit (doesn't have a full version of Labview, just the Run-Time engine) the card doesn't work.
    We installed the run-time engine on the unit, then the drivers.
    I guess my question is: Do most drivers work with both the full version of Labview and the run-time engine? Or do I need to somehow 'convert' these drivers to work with the run-time engine?
    Th
    anks for your help!
    Dave Neumann
    [email protected]

    Dave:
    I can't determine which dll is required but if there are more than one that
    shipped with the quatech I/O card try to placing one dll at a time in the
    same directory as the exe so that you can determine which one is the
    required one. If that doesn't do it then it may need more than jsut one of
    the dlls so placing all that came with the quatech I/O card s/w driver
    package in the same directory as the exe should do the trick.
    Best of luck.
    -Tom
    "Neumannium" wrote in message
    news:[email protected]..
    > Tom,
    >
    > Thanks for your reply. One of the problems I'm having is figuring out
    > which .dll I would need to include (I'm not a software guy).
    >
    > Would the .dll your speaking of be different th
    an the one which is
    > installed with the drivers? I'm looking at a .dll that is installed
    > when you install the labview drivers for this card, but the run-time
    > engine still doesn't want to get the card to work. (The file installed
    > when I install the drivers is called 'daqlv32.dll' and I don't know
    > how to find any other .dll's I might need)
    >
    > Actually, it appears the card 'is' being seen by the run-time engine,
    > but I'm getting impulses rather than distinct changes of state.
    >
    > Anyway, thanks for the help.
    >
    > Dave Neumann
    > [email protected]

  • Getting LabVIEW load error code 59 using LabVIEW 2010 with a Run Time Engine.

    I use a vi compiled with a run time engine to run separate vi’s in my application directory. Once a file association is made with this exe file any Vi in my application directory is available to be loaded as needed. This is a process that has been very successful for me over the years and would prefer to continue using this process. Most of my applications are running in LabVIEW 8.6 and have moved them to 2009. First indications are in 2009 this process is still working. However, I plan to go on to 2010 before upgrading my test stations.
    In 2010 I get the error 59: “The source file’s compiled code has been separated, and this version of LabVIEW does not have access to separated compiled code.”
    The same dialog box also presents, (Hex 0x626)  “Cannot open a VI with separated compiled code in a Run Time Engine that has no access to the VIObjCache.”
    What can I do in the build that will get around this error?
    Thank you

    Thank you for the solution. I am sure this works until the next vi in the vi library gets this option selected.
     The bigger issue is I was doing something that National Instruments did not support. When I started in the days of LV 4.0 it was recommended to me that I use this method as virtually all my applications were for in house projects. This is still my preference because it gives the most versatility and allows modifications of single files rather than compiling the entire application.
    The final solution I ended up with for those who may be having the same issues. My recommendation for what it is worth, is to compile the application as an executable. This is from what I can tell the only acceptable and supported method. Using this method the problem is solved.
    I have accepted this as the solution. I still don't like it. I could list the reasons why but it is a mute point.
    Thanks again for taking the time to respond to this issue and offer the solution you found.

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

  • 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

  • Building an Application in Windows to be used in Linux (with the Run-Time Engine)

    Hi All,
    I have an LabVIEW project I have developed in a Windows environment.  I can create an Application (.exe) using the Build Specification -> Application Builder which works fine on the development platform.
    I now want to distribute the application to a Linux Environment.  The OS is openSUSE v10.3 (with GNOME).  I have downloaded the two rpm files needed for the run-time engine and installed them, as per here:http://digital.ni.com/softlib.nsf/websearch/97E14BA3E0C14A89862572C300567733?opendocument&node=13207...
    Now, the question is; how do I create an Application in Windows which can be used on the Linux Box?  According to the Application Builder instructions, it's simply a case of removing the .exe extension in the Target File Name options, however, this gives an error "Invalid Extension."
    If I do create an exe and manually remove the extention is doesn't work on the Linux enviroment (typing ./application).
    Has anyone had experiance of this?
    Many Thanks for Any Help,
    Oliver
    Windows XP SP 2
    Labview 8.2.1
    openSUSE v10.3 (with GNOME)
    LabVIEW Run-time Engine Version 8.2.1 for Linux

    The cross-platform nature of LabVIEW refers more to the code than to the executable.
    LV (given the appropriate development version) can compile the same source code into a Windows (using LV for Windows), Linux (using LV for Linux) or Mac (using LV for Mac) program.
    This means you will still have three versions of your program, one for each platform.
    If you want to distribute VIs (without block diagrams), you will also need different versions of these as without the block diagram, they cannot be re-compiled for a new platform.
    Shane.
    Say hello to my little friend.
    RFC 2323 FHE-Compliant

  • Browser plug-in with mac run-time engine problem

    I have repeatdly tried to get web browser (Both Explorer 5.2.3 and Safari) VI viewing on my Mac (OS 10.4.2). I have reinstalled the run time engine (Labview 7.1.1 as downloaded from NI) numerous times with no luck. I get the usual "Browser plug-in required" message.
    Doing a seach on my machine in the Internet plug-in folder reveals no new plug-ins after installation of the RTE.
    I can run this VI work fine on a remote PC running Explorer, so I think my VI server is running fine. I quit the PC before trying it on the MAC to avoid any license limitations.
    Any suggestions? Is the browser plug in available as a seperate down load? I could not locate it on the NI site.
    Thanks
    -G

    Hi G,
    Lets try this. Install the LV71NPlugin file, in the attached image, in the /Library/Internet Plug-Ins directory. I had to save the image with a different extension to be able to upload it to the forum so...
    1) Download the file
    2) Change the file extension from "abc" to "dmg"
    3) Copy LV71NPlugin to /Library/Internet Plug-Ins
    Please let me know if this works for you.
    Thanks
    Chris J
    Attachments:
    LabVIEW71BrowserPlugin.abc ‏83 KB

  • How can i access remote front panel in RT with LabVIEW run time engine in client PC

    Hi to all,
    I have developed the RT application with cRIO 9075 integrated chassis. And i have access its remote front panel in client PC. Now i want to access the remote panel in the client PC without having LabVIEW runtime engine. If i connect the remote panel with that client, it shows only the vi border. i doesn't downloads the  front panel.
    How Can i access its remote front panel without LabVIEW runtime engine in the client PC?

    You cannot view a remote front panel without the LabVIEW runtime - the LabVIEW runtime is what makes the remote front panel possible.  What you will want to do instead is likely create a Web Service that you can access from a remote PC without requiring the LabVIEW runtime.  However, this will require you to develop a web-based HTML or similar UI to interact with the VIs running on your system - NI hasn't yet created a way to export a LabVIEW front panel as an HTML'ish page.  
    -Danny

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

  • Labview using Report generation toolkit in 2011 run time engine

    is that possiblity to run the  word in labview using Report generation toolkit in 2011 run time engine

    It is possible to use the Report generaion toolkit with the run time engine.  But you will have to include a lot of VIs from User lib since the report generation toolkit uses a lot of dynamically called VIs and classses.
    Certified LabVIEW Architect
    Certified Professional Instructor

  • Can I run two separate versions of the LabVIEW Run-Time Engine on one PC?

    Hello, I am curious if anyone knew if it is possibly to install and use two separate versions of the LabVIEW Run-Time Engine on one PC?  I currently have the 2009 Run-Time Engine installed on one machine and wanted to install the 2011 Run-Time Engine as well. I know that you can run two separate versions of the LabVIEW program on one machine, but what about the Run-Time Engine?
    Thanks!
    Solved!
    Go to Solution.

    I'm guessing this is a bug that NI needs to fix.  I see no reason you shouldn't be able to install the run-time engine of an older version.  I'd be interesed in if it allows you to install the older development environment, which also includes the older run-time engine.  There are some command line switches for NI installers as mentioned here:
    http://digital.ni.com/public.nsf/allkb/C361087EE9F20810862577850073128E
    I wonder if there is a force install option.
    Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
    If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

  • VI not same as LavView Run-Time Engine after 2.0 to 3.1 conversion

    I get a dialog
    Unable to load VI 'Front Pannel Development.vi' with the Run-Time Engine.  It is
    possible that the version of the VI or one of its subVIs is not the same as the
    LabView Run-Time Engine version.
    Note : For optimal execution performance, you should ensure that all your VIs are
    compiled to the same version.
    Configuring TestStand to use the LabVIEW Development System to run your VIs may fix
    this problem.  To change the configuration, go to Configure>>Adapters>>LabVIEW.
    Do you want to edit the VI in LabVIEW?
    Yes or No.
    When leave the Specify Module dialog.  for a step that calls a VI.
    That VI uses some Labview specific set and get variable sub VIs. 
    Changing them to TestStand 3.1 equivalent did not get rid of the
    problem.  I have also tried mass compile on the VI
    directory. 
    Any Ideas how to fix this?  I did try the Configuring adapters thingy but that was already right.

    Hi,
    Dont forget to mass compile the VI's in the TestStand folder's as well.
    Regards
    Ray Farmer
    Regards
    Ray Farmer

  • How can I uninstall Labview run time engine from the machine?

    I understand that Labview has not given any provision to show customized 'License Agreement screen'. Isn't it? This is the main cause of my problem. Since I want to show our own license agreement (LA) screen, I made the one using Labview. To show this license agreement screen, I first install a small application which has only this LA screen with Labview run time engine. The customer can see License Agreement Screen with Labview Run Time Engine on his machine. If My customer accepts the LA, I will install the main application further by calling another setup.EXE file.
    If my customer selects 'Do Not Agree' to the LA, I will quit the installation process. Here I also want to 'uninstall' Labview Run Time Engine
    from his machine since he doesn't accept License. I would like to know how to uninstall Labview run time engine from his machine?
    Another way which I could think is to run the LA screen from the CD with Labview run time engine on the CD. I will start installing the main S/W to the customer's machine with LABview Run Time Engine only after he accepts License agreement. I would like to know how to run the Labview application from CD without installing run time engine on the target machine?
    Can anyone suggest solution to my problem?
    Thanks,
    Chander

    J-Tek,
    I would suggest re-installing the Run-time Engine and then uninstalling it after a reboot. Also, you can download a program called Msicuu.exe (for NT, 2000, XP or Msicu.exe for 9x) to help clean up the registry for uninstalled programs.
    Randy Hoskin
    Applications Engineer
    National Instruments
    http://www.ni.com/ask

  • Distribute application without labview run-time engine

    I read a lot of post saying if the target machine has the same run-time engine installed, then I don't need to distribute the application with labview run-time engine. Somehow this rules doesn't work for me. I have a PC installed labview 2010 development system and has run-time engine 2011 SP1. I also download the same version of run-time engine and installed it in a target PC. When I distribute my labview application, if I select to include the run-time engine in build properties, the application will be able to install and run properly in the target machine; If I don't include the run-time engine, then I wouldn't be able to run the application.
    Does anyone help me on this? I don't want to always build the application with the run-time engine since it's quite big
    Solved!
    Go to Solution.

    Could you take a look at my NI software list and let me know what labview run-time engine is really in use?
    And in build properties, it actually list addition installer include labview run time engine SP1. If I includes this version of run-time engine and run the installer in target machine, it will still install the run-time engines just like there is no run-time engine installed in the target machine before.
    Attachments:
    NI software.jpg ‏98 KB
    Installer.jpg ‏216 KB

  • When opening PT Assembler, Windows tries & fails to open NI Run-Time engine

    I am using PT Assembler, a front-end for the Panorama Tools software bundle, to stitch microscope images taken by LabVIEW using the QCam Suite.  Whenever I attempt to open PT Assembler, Windows informs me that it needs to configure the NI LabVIEW Run-Time Engine 7.1.1, which it cannot as it is not installed.  After cancelling the configuration 4-5 times, my program opens and runs without errors.
    PT Assembler has absolutely nothing to do with with NI or Labview as far as I can determine, so why does Windows try to open it with the run-time engine?   I attempted to install the 7.1.1 engine from ni.com but was informed that it was unavailable.  Is there any way I can keep Windows from attempting to use the engine?  I could install a later version of the engine and hope it works, but I am a bit leery about how it might affect my program.

    Hi rhazelton,
    If this program hasn't been created in LabVIEW, then I'm not sure why it would be doing this..  However, you should be able to download the 7.1.1 run-time here.  Give it a try and see what happens!
    Regards, 
    Brian A.
    National Instruments
    Applications Engineer

Maybe you are looking for