How to handle runtime error in PreUUT step when running in Parallel mode

Question

I would like to run Test UUTS in parallel mode, and some actions are done in PreUUT such like read serial number and fixture control.
The process model won't goto PostUUT Step when runtime error occurs in PreUUT step, so i would like to add some actions to check if sequence error in cleanup and go back to setup in PreUUT step, but i find it skip all the actions in setup and main step?
What should i do if i want to go back to run PreUUT again as the first time to run when runtime error occurs?
Or, is there any good way to handle this kind of error withour restart program?
Solved!
Go to Solution.

Answer 1

This question does not depend on PreUUT or ParallelModel at all.
First of all:
A Runtime Error is a situation where TestStand encounters a problem which makes further testing either impossible or senseless. So a Runtime Error always indicates a situation where proceeding the test sequence is not recommended.
Nevertheless, there are situation where you want to handle those errors without stopping the execution. A "traditional example" for this is initialising serial/GPIB devices. If the device does not reply, there might be different issues the operator can easily resolve and (if corrected) the sequence can proceed properly. The operators action could be:
- Check if device is switched on
- Check connection between PC and device
So the error state is used to inform the operator about the malfunctioning device and regarding of the actions the operator takes, the execution will either proceed or terminate.
When TestStand encounters a Runtime Error, it initially reacts with displaying a dialog. This behavior can be modified in the Station Options >> Preferences >> On Runtime Error.
Furthermore, you can install callback sequences which are called if an error occurs. Those would be either SequenceFilePostStepRuntimeError or ProcessModelPostStepRuntimeError (depending on the fact if you are changing the process model or simply working with client sequence file callback overrides). These are "normal" sequences you can use in order to get system information, loop on the step or....essentially do whatever you want. If you want to proceed though, you must not forget to reset the error flag.
hope this helps,
Norbert 
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.