run time engines

[L_V_Developer]

If you have several runtime engines installed, will  the executable pick the correct RTE to operate correctly?

ie@ I have several executables developed using different versions of Labview. The code is locked, so I can't open it and save it using the latest version of labview. If I call these executables using Testand 3.5, will they run correctly if I have the correct RTE for each installed?

[smercurio_fc]

They should.

[waldemar.hersacher]

Each executable will find its own runtime engine. The runtime engines are installed in different folders under National Instruments\shared\LabVIEW Run-Time.

[Hillman · Accepted solution]

Hi L_V_Developer,

Thanks for the post.

Just to confirm all the points,

Both LabVIEW runtime engines will exist separately, and the target machine will be able to run the executable using the runtime it was built with. You can install as many runtime engines on a machine as you would like, and they will not interfere with one another.

For example:
If you want to send someone a LabVIEW executable built on LabVIEW 8.6, and they are already utilizing LabVIEW executables built with LabVIEW 6.1. The new 8.6 LabVIEW runtime engine will exist next to the older LabVIEW 6.1 runtime engine on the target machine, and nothing will be overwritten or conflict.

Note: The version of the run-time engine must match the version of the LabVIEW development environment the executable was created on. For example, an executable created in LabVIEW 5.1 requires the LabVIEW 5.1 Run-Time engine to run. The exception to this is with minor LabVIEW revisions (e.g. a LabVIEW 7.1 executable can be run on the LabVIEW 7.1.X Run-Time engine). 

This obviously indicates that the run-time engines are not backwards compatible, e.g., LabVIEW Run-Time Engine 8.5 cannot run executables made in LabVIEW 8.2.1.

In order to check which run-time engines you already have installed to your PC, browse to the following directory:

C:\Program Files\National Instruments\Shared\LabVIEW Run-Time

In that directory, you will find a different folder for each version of run-time engine that you currently have installed onto your system.

Let us know if you have any problems,

[L_V_Developer]

OK, now for the second part of my question. If this works for LAbview. Will it also work for Teaststand and Labwindows/CVI?

[Hillman]

Hi There,

Are you calling executable's from Teststand and CVI?

If so, then Im not sure what would have changed. If not, then make sure you setup the abView Module Adapter (Configure-->Adapters...-->LabView) correctly.

Message Edited by Hillman on 02-02-2009 04:44 PM