Give operators
a clear path to the result.

A test plan maps product models and test flows to DUT positions. Select the plan to bring those assignments into production. Configure sequential or supported parallel execution around the fixture and instrument resources.

Parallel operation needs a fixture and device-access design that can support it. Review specialist operations and factory exchanges against the chosen plan arrangement as part of commissioning.

Model Setting defines the required barcode slots and their rules. Configure capture through operator entry or supported scanner/device actions, then apply the relevant length, required-content, duplicate and interlocking checks.

A successful scan supplies identity; readiness also depends on the configured devices, sequence and start conditions.

Golden Sample rules support known OK and NG master checks at configured triggers. Use them to verify that the station accepts an expected good condition and detects an expected failing condition before the required production work proceeds.

Start rules can incorporate supported hardware triggers and readiness conditions. Required barcodes, enabled steps, required devices and applicable retry constraints contribute to the overall start decision.

Sequence configuration includes Show Popup, the operator message and acknowledgement settings. Use them for instructions that belong at a particular point in the procedure, such as confirming a fixture condition before the next operation.

Where acknowledgement is required, the operator follows the CONTINUE or STOP TEST path presented by the application. Configure the message and acknowledgement deliberately, and validate the stop and cleanup behaviour alongside the rest of the sequence.

Production testing Inside the software

Enlarge

The Testing workspace shows group/step progress, live values, limits and PASS / NG decisions alongside device status. In configured multi-DUT operation, preserve the association between each position, barcode and result.

Cycle and handling information describe different parts of the production process. Camera, CIE and event views provide additional context where the configured workflow uses them. The operator follows the defined start, stop, reset and recovery actions while engineering controls the underlying rules.

Production control continues outside the measurement steps. Rules define what happens on incoming responses, resets, handling periods and completion, including the actions needed to prepare for another unit.

Final measurements and test status feed the configured report, label and factory-exchange paths. Keep unit identity, attempt history and relevant evidence together so a later investigation can distinguish a product failure from a communication or storage problem.

Use the available recovery workflow and logs to resolve the underlying issue. Review the recorded attempt before deciding whether the product itself needs another test.