01-15-2009 02:02 AM
I am trying to run a vi in teststand the has two parrallel execution paths. In one path a sub vi sets up the trigger and awaits data from a scope module, while in the other path I start a power supply. The power supply waits until the scope is armed and then runs.
This works as a standalone vi. When I attempt to run this vi in teststand it runs the scope vi first and then runs the power supply. Of course the scope vi times out and exits and the data is missed.
I have tried a number of synchronisation methods, and while they seem to work standalone, as soon as I try them in Testsatnd I have this problem.
I am new to teststand and wondering if there is some config setup that I have missed that allows a vi like this to execute as it does standalone.
I have a number of simpler vis that run as expected but this one has me stumped.
I have considered splitting these vis up but would really prefer to have them in the same vi.
(Running the latest versions of teststand and Labview)
henry
Solved! Go to Solution.
01-15-2009 02:12 AM
Hi,
Use the Run VI Asynchronously step type. See Chapter Appendix E of the TestStand Reference manual.
I am making the assumption you are using TestStand 4.x.
If you don't have that step type because you have an early TestStand version, then you can use a SequenceCall and set this to run in a New Execution.
Hope this helps.
Regards
Ray Farmer
01-15-2009 10:24 AM
hkroker,
This is a known issue. Please refer to the following KB to help resolve your issue.
- Why Does My LabVIEW VI's Parallel Blocks Run Sequentially when Called from TestStand?
Regards
Anand Jain
National Instruments