Test Stand LabView adapter 8.6 run time will not run 8.5 VIs

[bs2112]

I’m trying to run a script I developed with a dev computer on a regular PC set up with a Test Stand User Gui, and run times for Test Stand and Labview.

With the Test Stand Labview adapter set to 8.6.1 all of my ENA(Agilent Network Analyzer) calls fail for “VI Version is too early to convert  to the current  LabVIEW version.”  The ENA library is written in 8.5.  If I set the adapter to 8.5.1 then all of the VIs developed in 8.6 fail.  In addition it will not run any VIs that I save back to 8.5.  I installed a demo Labview development version (2010?) and everything ran fine with the adapter set to Development System.

I am not sure what to try next to get it to run on the regular PC, any hints.

Test Stand = 4.2

LabView = 8.6

Running in windows XP

[asbo]

The run-time engine cannot recompile any code whatsoever, so any VIs you want to use with a particular version (e.g., 8.6.1) must be compiled into that version. The reason that the 2010 demo worked was because it was development, which can recompile code. Upsave the ENA library for 8.6.1 and everything should be savvy.

I believe the only exception to this would be 8.6 versus 8.6.1, which makes the verbiage "VI version is too early to convert" justified.

[dowNow · Accepted solution]

Any LabVIEW RTE can only run VIs of that specific version. It takes the LabVIEW ** development environment ** to "save as previous," or open an older version and resave it. The LVRTE simply cannot do this.

When you configure the LabVIEW adapter to LabVIEW Runtime Engine, you have to pick one version of the LVRTE in the dropdown menu. By definition then, all your VIs must be of the same version, and match the version selected in the LabVIEW Adpapter Config.

I agree that saving everything as 8.6.1 is the way to go. You should build a new installer and do a new runtime installation and not just replace VIs. You might get lucky replacing VIs, but it is not a best practice.

Good news, if you upgrade to TestStand 2010 the LabVIEW adapter can run more than one version of the LVRTE during an execution. (I haven't personally tried it ;-))

cc

[bs2112]

One of the many things I tried was saving the ENA library to 8.6, but I could not get it work.

This is the Original library I installed and was trying to Convert (8.0 upgrade agena.zip)

http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=001CE83736F3674BE0440003BA7CCD...

I am about to try this one. (8.2.1 Upgrade)

http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=74D1F1D4EB5268E8E04400144FB7D2...

I am pretty new to labview so I am not sure how to make the save to previous version workfor libraries, but I can easily do it with individual VIs.  For libraries, it creates a new directory, and puts in all of the files and then asks me about saving the lib files as something else.  This is where I think I get it wrong.  I tried it again today and got the same results.

I greatly appreciate the Help

Brian

[Dennis_Knutson]

What version of LabVIEW runtime do you really want to run? It's far simpler to load your 8.5 code with a newer version and just do a save. "Could not get it to work" is not at all a good description of a problem, Provide details.

[bs2112]

I am not sure why but the installer was the fix.  I built a project, added all of my VI's, and then created an installer for the Sequences and the VI's I had written.  When I ran the intaller on the target machine, everything worked.

I will create a seperate installer for the device drivers and anouther for the Test Stand User Interface.  I had tried combining all three but that had other issues.  Also this way if I make code changes I just need to rebuild the installer and send it over.

Thanks for the Help

Brian

[Manooch_H]

Just to clarify, TestStand has had a feature that will allow steps to run in the correct LabVIEW Run-Time Engine version regardless of the global LabVIEW Adapter configuration. In the Advanced Settings Dialog Box of the LabVIEW Module, you can check the Always Run VI in LabVIEW Run-Time Engine check box. This feature has been around since TestStand 3.1.

In TestStand 2010 (released December of 2010), we added a feature to the global LabVIEW Adapter configuration that let's TestStand automatically determine which LabVIEW Run-Time Engine version to use to execute a step. Choose the Auto detect using VI version option in the Version combo box control of the LabVIEW Adapter Configuration Dialog Box to enable this feature.

Hope this helps.