Confirm a New Oscilloscope Acquisition Before Saving a Test Waveform

An oscilloscope can retain a useful-looking waveform after the event you intended to capture never occurred. Automation that immediately reads the display or waveform memory may then attach an old trace to a new board. Establish evidence that the requested acquisition actually completed before saving it as a test result.

Tektronix’s oscilloscope automation example uses operation-complete synchronization with the supported instruments. Consult your model’s programming manual for the exact acquisition and status sequence; a fixed software delay is not a universal completion test.

Define what constitutes a fresh capture

Specify the intended acquisition mode, trigger condition, channel sources, and record requirements. Determine which status or metadata proves that a new acquisition followed the arm request. Where available, retain acquisition identifiers or timestamps together with the station attempt identity.

Keep waveform acquisition separate from waveform transfer. A transfer can succeed even when it retrieves an earlier record. Likewise, acquisition completion does not by itself prove that the selected source or trigger condition represents the event required by the product test.

Verify the order of operations

1. Apply and verify the approved acquisition configuration.
2. Arm the instrument using the documented sequence.
3. Generate or wait for the intended event.
4. Confirm completion through the supported status mechanism.
5. Transfer the waveform and its scaling metadata.
6. Associate the saved capture with the current test attempt.

When a trigger does not arrive within the defined observation window, record that condition explicitly. Do not substitute the last available waveform. The appropriate disposition may be an incomplete measurement or a product failure under a defined test requirement; it depends on what the absence of the event establishes.

Challenge the automation

Use distinguishable, safe stimulus conditions in consecutive validation runs. If both runs intentionally produce identical traces, a stale-data defect may be difficult to expose. Preserve the instrument setup and trigger source used for each check.

Before releasing the automation, verify a saved waveform independently and confirm that amplitude and time scaling match the capture metadata. A screenshot may assist review, but retain the numerical data when the acceptance calculation depends on it. The clock correlation guide explains the additional evidence needed when comparing that capture with events from other systems.