Quick answer: Begin with a known output-off state and verified limits. Automation should explicitly configure settings, read back status, handle communication failures and return to a defined safe state rather than assuming commands always succeed.
On this page
Establish a known initial state
Verify the instrument model and configuration before using a script. Begin with output disabled, suitable setpoints and documented protection settings. Record whether prior settings persist after restart; the application should not silently depend on an unknown stored state.
Send commands and verify status
Use the exact programming manual for supported commands, units, terminators and query responses. Read back setpoints, output state and available error/status information. A successfully transmitted command is not proof that the output has settled or that the DUT is receiving the intended voltage.
Timing and logging
Separate command latency, instrument update rate and electrical settling. Choose dwell and measurement timing from the test requirement and verified instrument behaviour. Record readings, settings and relevant status with timestamps so a run can be reviewed or reproduced.
Plan failures before unattended operation
- Define the response to communications timeout and script termination.
- Decide how output state is verified after a restart.
- Use appropriate fixture monitoring and interlocks where the system requires them.
- Keep batteries and energy-returning loads within documented compatibility and test procedures.
Troubleshooting a failed sequence
Stop at a defined safe state. Check model identity, ordered interface, connection settings, command support and instrument errors. Retry only with a clear fault-handling policy; repeated commands must not unintentionally advance a test or change a limit.
Practical checks
| Check | What to verify |
|---|---|
| Startup | Verify model identity, limits, protection state and output OFF. |
| Commands | Use the exact command manual, terminators and supported units. |
| Verification | Read back settings, measurements and instrument errors. |
| Failure path | Define output behaviour on timeout, script failure and restart. |
Updated