More details on "Concurrent applications using System Exec.vi do not run concurrently when executed within TestStand"

[Ray.R]

Sorry, I didn't know how to append to the original question without "ansering it"..

Here is some additional information:


The vi works well in Labview..

It does not work well in TestStand.

Only one copy of TestStand is running.

I'll try to describe the situation better:

In Labview vi.

System Exec.vi# 1 calls application to start bitstream.
wait 2 sec
System Exec.vi# 2 calls application to receive bitstream while first application continues in parallel.

Both applications return values while they run.

This works when running the Labview vi by itself.
Insert this vi within a TestStand sequence and it no longer works... On
ly one application runs at the given time.. they should run simultaneously..

Thanks,

JLV

[Ray.R]

Feels strange answering my own question...

I found out how to do this and I will share it:

Open the vi which contains the first System Exec.vi.
(In LV) Under File menu, select "VI Properties".
Select category: Execution
In Preferred Execution System, select Other 1.

click OK..

JLV

[Ben]

If you stop and think about it, these are the only answers we KNOW are correct.

Ben

[Ray.R]

That's a good one, Ben 🐵

[PEHO70]

I had a similar problem, starting a sub-vi parallel to the system exec.vi, esp. communicate with a power supply to switch on after my firmware loader (external apllication) waits for the power-up sequence of the D.U.T. The problem was to wait for the completition of the loader for getting any error information over the standard error output ("successfully programmed" e.g), and turn on the power supply few msec after loader starts .......
thx for your hint

best rgds
Peter