Cannot open vi in TestStand 3.5 using Labview Run-Time Adapter

[MarcoMauri]

I've got a problem using a VI in TestStand 3.5.

The vi is very simple, here is the content:

The Adapter we have chosen is Labview 2011 RTE, and the test vi is coded in Labview 2011.

We have mass compiled vi.lib.

When we want to use this VI in a step Test Stand reports it cannot open the vi.

Thanks in advance for any help,

Marco

[Norbert_B]

Marco,

what is not working? Is the EXE not called correctly? Or do you get an error?

Besides: LV 2011 was never tested with TS 3.5....

Norbert 

[MarcoMauri]

Hi Norbert!

It seems Test Stand cannot open the vi with Labview 2011 RTE as adapter.

Here is the screenshot of what i get:

Note that if I create a source distribution of the simple vi (that contains only System Exec.vi) everything is fine.

Thanks,

Marco

[Norbert_B]

Marco,

the dialog clearly states a possible reason for this:

The VI or some of its subVIs is not compiled for LV 2011.

You can make sure by using Mass Compile that the code is in the correct version. If this does not help, test it purely in LV (calling the step's module from a LV dummy and run it as EXE).

Norbert 

[MarcoMauri]

The vi contains the code I've shown above (see it attached to this post) and has been created with Labview 2011.

We found that a more complex vi was not being loaded due to the presence of System Exec.vi and created this test vi to verify that.

Disabling System Exec "solved" the issue with the large vi (it was loaded, at least).

We got the same problem on a second PC using Test Stand 3.1.

thanks a lot,

Marco

[Norbert_B]

So i understand that the call to the EXE is the issue. Do you get error messages?

Does the EXE start to run, but not work as expected?

Can you test this with a more up to date version of TS (e.g. TS 2012 eval)?

Norbert 

[MarcoMauri]

With TS 2010 SP1 the step is working fine, and we have solved the problem this way.

Anyhow, I would like to understand what was happening with the older version of TS.

The EXE didn't start at all because TS fails to load the step itself, so I could not execute it.

Switching from Labview RTE to the development  framework fixed the issue (step loaded without any problem).

Thanks,

Marco