You can initiate a retest from the TestStand Sequence Editor, an operator interface, or a handler/prober. The STDF log file includes retest information.

Manually Initiating a Retest from the TestStand Sequence Editor or Operator Interfaces

Click the Retest button on the TSM toolbar or in the Lot Statistics Viewer while execution is paused to manually initiate a retest. In a custom operator interface, you can create a button bound to the PerformSinglePartRetest command to perform the same functionality as the Retest button.

When you manually initiate a retest, TSM retests the DUT without calling the EndOfTest or StartOfTest callbacks in the handler/prober driver and discards the bin results of the previous test for the retested DUT.

Initiating a Retest from a Handler/Prober

A handler/prober can initiate a retest by sending a Part ID or part die coordinates that match a previously tested part. TSM detects this condition, tracks the test as a retest of the previous matching DUT, discards the bin results of the previous test for that DUT, and does not increment the part counts.

STDF File Contents after Retesting a DUT

When you retest a DUT, the STDF file includes the PIR, PRR, PTR, and FTR records for every test run, including retests. The WRR, PCR, HBR, and SBR summary records include only the results of the last retest and do not include retested results. The TSR summary record includes the counts of all tests run, including retests.