Call a VI whith the Run-Time Engine in TestStand

[tadkozh]

Hi,

I'm using TestStand 4.2.1. On the same PC I've installed LabVIEW Run-Time Engine 2009 (9), 2010, ...

On another PC I developped a series of VI with LabVIEW 2010. My client want VI in the 2009 version, that's why I use a Run-Time Engine.

I placed an action step, selected my VI and the adapter was not able to load the VI (as viewed in the attachment).

Before I had selected the right Run-Time Engine (in Configure -> Adapters), and I saved the VI in the 2009 version (instead of 2010).

What is the problem ?

Another problem is that in an other VI I use an XML library (the default in LabVIEW), How convert the entire library in the 2009 version ?

Thanks for your help

[RayFarmer]

It's not only the top level VI that needs to be at the correct version. you need to make sure all VI's and CTLs used within your SequenceFile are at the correct labview version.

That includes any subVI etc.

[tadkozh]

Hi,

Yes, I set all VIs in the correct version (I don't have any ctl).

[TSJim]

Hi,

One way to check if vi's are compiled in LV2009 is to select menu item 'View VI Hierarchy' from the top level vi.  Then select 'View>Full VI Path in Label' and 'Always Show Labels'.  Check that none of the VI's are in the LV2010 paths.

To fix, you may have to create a project (File>New Project from your top level VI - Add the VI to the project when prompted).  Right click on the Build Specifications and create a new 'Source Distribution'.  Check that under 'Additional Exclusions' that VI's in vi.lib, user.lib, and instr.lub are not excluded.  This should package up all of the VI's into a library that will run in the LV2009 RTE.

Thanks,
Jim

[tadkozh]

Hi,

It seems that the generated library is built with the 2010 version. I didn't found a way to build the entire library in a previous version of LabVIEW. Did I miss something ?