NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

"Do Together" flow control

Has anyone proposed a new type of flow control for future versions called "Do Together"
 
There is an educational programming package out there called "Alice" and is worth checking out if you haven't.
It allows programming in a very different and creative and intuitive way.
But what really stood out for me was the new construct called "Do Together" which allows for immidiate parallelism of commands w/out extra work.
 
It seems that it only makes sense to have the ability to parallel a grouping of steps w/ all the multi-core talk going around and the inherent parallel nature of some tests on a single DUT w/out needing to make seperate sequences for each of them.
0 Kudos
Message 1 of 4
(3,155 Views)
This sounds like a good idea.  For those unaware, there is something similar for LabVIEW steps-  Run VI Asyncrhonously.

Also, an easy way to give suggestions to NI R&D is through the Product Feedback page, located at http://www.ni.com/contact

Allen P.
NI
0 Kudos
Message 2 of 4
(3,144 Views)
You can kind of do this at the sequence level by using the "New Thread" option on your sequence calls. For example, if you had three sequence "a", "b", and "c" that could all be run in parallel you could have three sequence calls, one to each sequence, in your top level sequence and then three wait steps at the end of your top level sequence (if you want the results to show up in the report) to wait for the asynchronous calls. Also for VIs what Allen suggested is good solution too. Certainly if it worked more automatically as a builtin feature like you are suggesting that would be easier (and I think it's a great suggestion), but in the meantime it is possible to get similar asynchonous execution the way I described.

Hope this helps,
-Doug
0 Kudos
Message 3 of 4
(3,126 Views)
Yes, I already knew about the parallel sequence calls as per my comment
"...parallel nature of some tests on a single DUT w/out needing to make seperate sequences for each of them."
I'm not looking for a workaround, but rather a truly parallel structure.
But thanks for chiming in. Be sure to check out "ALICE" though. Really eye opening to a new way to program, especially w/ the 3d graphics.


@dug9000 wrote:
You can kind of do this at the sequence level by using the "New Thread" option on your sequence calls. For example, if you had three sequence "a", "b", and "c" that could all be run in parallel you could have three sequence calls, one to each sequence, in your top level sequence and then three wait steps at the end of your top level sequence (if you want the results to show up in the report) to wait for the asynchronous calls. Also for VIs what Allen suggested is good solution too. Certainly if it worked more automatically as a builtin feature like you are suggesting that would be easier (and I think it's a great suggestion), but in the meantime it is possible to get similar asynchonous execution the way I described.

Hope this helps,
-Doug






Message Edited by NJKirchner on 03-13-2008 03:15 PM
0 Kudos
Message 4 of 4
(3,118 Views)