|Download Help (Windows Only)|
In addition to following common approaches to debug components of a TestStand test program, consider the following additional approaches to debug components of a TSM test programSequence Execution
Sequences can be in a running or suspended testing state. Testing is running when continuously testing DUTs. When testing is running, each test socket is executing tests for one DUT. Testing is suspended when one or more TestStand test socket executions are suspended at a breakpoint. One test socket can be suspended while other test sockets are running. The background of the Execution window changes to yellow to indicate that the execution is suspended. You can examine sequence variables only in executions that are suspended.
When testing is paused, executions are not suspended. Pausing a lot does not suspend executions the way using the default TestStand Sequence Editor Debug»Break or Break All menu items do. When you pause an execution, testing continues until each site completes testing its current DUT. The executions then wait for operator input before sending the End of Test signal to the handler or prober and proceeding with testing the next batch of DUTs. To suspend test socket executions to examine variables or to step into code modules, set a breakpoint on the step where you want to suspend. You cannot examine variables in the sequence editor for executions that are not suspended.
Use the following techniques to debug TSM sequence execution:
To monitor the bin counts for each site while testing in the sequence editor, use the Lot Statistics Viewer, in which you can view lot statistics while running or debugging a sequence in the sequence editor. You can also control test program execution in the Lot Statistics Viewer.
When developing, testing, or debugging a semiconductor test program, the test developer might not have access to an actual handler or prober. In such cases, the test developer might need to simulate a handler or prober to verify that the test program behaves correctly. Use the NI Simulated Handler Driver TSM installs to simulate handler/prober functions when you do not have access to an actual handler or prober.