10-04-2011 10:30 AM
I would like to wait for a VeriStand alarm in TestStand, then continue execution of the sequence. Is this functionality built in or will I have to construct something from the VeriStand API?
10-04-2011 10:30 AM
I would also need a timeout for the wait, in case the alarm does is not tripped.
10-05-2011 03:47 PM
Hi jnclaker,
Admittedly, I am more familiar with VeriStand than I am with TestStand, but I would think you would just use the NI VeriStand Get Alarm Status.vi.
You would just drop this as an action step, and link the step to the NI VeriStand Get Alarm Status vi. From there, you would take in the alarm statuses into TestStand via loading the outputs into variables in the Value column, shown in the reference image below (which uses the Read PNG File.vi rather than the NI VeriStand Get Alarm Status vi, but you get the idea).
If you need to constantly monitor these alarms via this method, it would probably be best to create a custom step type and place that at key points in your sequence where the alarm values need to be read. If this needs to be done constantly throughout the sequence, it might be best to run a subsequence in a separate thread and call the vi in that.
For more information, here is a more generalized tutorial describing the process for Adding an NI VeriStand Step Type to NI TestStand.
I hope this all helps. Post back if you need any further clarification.
~kgarrett