Turn a test specification
into a controlled workflow.

A sequence combines individual steps with groups of child steps. Use the grid to edit fields, the tree to follow hierarchy and the visual view to review the arrangement. Collapse completed sections while working on another part of a long sequence.

Test sequence editor Inside the software

Enlarge

Link saved CAN, LIN, relay, programming, vision or Data Link operations where the workflow calls for them. The linked configuration and its relevant limits remain part of the engineering review.

A step holds more than a command string. It connects the selected device and action to response interpretation, a result and the next operation. Store useful responses as variables when later calculations or commands depend on them.

Use loops for repeated operations and sweeps for checks across a configured range. A sweep defines its range, step size, dwell and stop behaviour, with results retained for individual points. Repeated testing and monitoring should also define how the run ends and how outputs are returned to the intended state.

Timing includes both configured waits and actual device or product response time. A short delay is useful only if the intended state is established before the measurement is taken.

Use the UDAQ / RS485 RELAY SEQ workspace to arrange relay commands, timing and response checks. Trial the configured sequence with the intended device, then link it to the main test flow.

A relay operation can select a measurement path or coordinate fixture switching before a dependent check. Review initial states, settling times and completion actions against the station design. Relay sequencing and ordinary I/O are separate from licensed UDAQ firmware programming.

Run phases distinguish preparation, the test itself and completion work. Use them to make required initial conditions and final output states visible in the flow. Review the effect of disabled groups, linked sequences and coordination between operations.

• Establish the required supply, relay and communication state before dependent checks.
• Define the response to a rejected measurement, timeout or operator stop.
• Include the required completion and cleanup actions for the fixture.
• Confirm how shared instruments and synchronisation affect multi-DUT plans.

Run a selected step, group, range or full sequence. Live debug and communication evidence help compare the command sent with the actual reply and resulting decision. This makes a wrong decode, missing response or premature measurement easier to separate from a product fault.

Virtual-device trials are useful while developing logic. Final acceptance requires the intended instruments, product and fixture. Programming actions need deliberate execution and must not be treated as automatically repeatable after a failure.

Assign the reviewed flow and model to the appropriate DUT position in a test plan. Check barcode requirements, active models and the specialist licences used by linked operations. Validate the full production route, including record storage and any MES or label actions.