ni.com is currently undergoing scheduled maintenance.
Some services may be unavailable at this time. Please contact us for help or try again later.
05-16-2011 04:48 AM
Hello,
Would anyone can help with this tiny problem ?
We have a batch (.bat) that launches a given list of TestStand sequences, which works as expected.
However, we would like to monitor the result of each sequence and display it to the operator.
Our idea is to get the sequence result in a VI, run at sequence end, and add it to a queue, that will be retrieved and displayed on a VI monitor, run separetly.
The only problem we have left is to be able to retrieve the sequence global result. Any idea or suggestion ?
Thanks
Raphael
Solved! Go to Solution.
05-16-2011 05:04 AM
I'd rather use an UI Message to send a string with the step name and result.
05-16-2011 05:50 AM
Thanks. The problem is not the monitor and how to pass the information to it.
We already have a test monitor (using queues) that is working as expected.
The test sequence is queuing information, mainly at steps end with step result, and the monitor is displaying information from that queue. The queue is resseted at each sequence start.
We would like to derivate that monitor to display only sequences (launched by a batch file) overall-global-final result of all the sequences ran. Using UImessage is maybe a better way, but we do not want to spend time re-writing another monitor.
The problem is how do we retrieve this overall-global-final sequence result in LabVIEW ?
05-16-2011 10:00 AM
Hi,
Maybe this thread will help
Regards
Juergen
05-16-2011 10:04 AM
Hi
... and for a complety stand-anlone report stuff
Take a look at this
http://forums.ni.com/t5/NI-TestStand/Saving-ResultList-as-binary-file/td-p/653522
Regards
Juergen
05-16-2011 01:18 PM
Hi,
If you are talking about getting the status of your Main Sequence, Passed, Failed, Terminated, Error, then look in either process model execution entry point sequence, Test UUTs or Single Pass, and check out the step status of the step MainSequence Callback, step.result.status.
You could add a single step to your process model just after MainSequence Callback to read the status and drop it on your que. Check out the expression in the precondition of the statement step Record MainSequence Failure in the SequentialModel.seq as an example.
cc
05-17-2011 08:32 AM
Thanks for all your answers. We finally ended by queuing sequencefailed value from sequence context property node.
I also discovered the TestStand database logging and started to use this in parallel.
Thanks again