Automotive Oscilloscope Pulse Width Trigger: Define the Event Before the Capture

Write the event in a sentence first

A shop is investigating an occasional change in a repeating waveform. An ordinary edge capture may retain many transitions without answering which pulse deserves inspection. Before selecting another trigger type, write the question: which channel, which pulse polarity, and which duration condition would identify the event of interest?

Keep the reason for that condition beside it. A vehicle service limit, an observed comparison and an exploratory search boundary have different evidential status. An exploratory setting must not quietly become a pass/fail specification in the repair report.

This guide concerns capture planning and saved-data review. Connections, references, accessories and any permitted vehicle operation require the applicable procedure and equipment instructions. It supplies no universal voltage level, pulse duration or probing method.

Separate the trigger rule from the measurement

Pico's advanced-trigger guide describes pulse-width selection by positive or negative polarity and by conditions such as narrower, wider, inside a range or outside a range. It contrasts this with a simple edge trigger, which can select a transition without selecting the desired pulse duration.

For the actual scope and software, identify these fields before a permitted capture:

• Source channel and the signal quantity represented by that channel.
• Pulse polarity relative to the selected trigger level.
• Threshold value, units, reference and any relevant trigger conditioning.
• Comparison operator and duration value, or both bounds of a duration window.
• Acquisition mode, retained time window and available context around the event.

Use the instrument's own definitions. Similar menu labels do not establish identical limits, boundary behavior or support on another scope. Save the setup rather than relying on memory of a slider position.

Pico's automotive trigger reference states that Auto can display data after waiting even when the trigger condition was not met. Record the acquisition's trigger status or origin. Do not report Auto-timeout, forced or otherwise unqualified data as a confirmed width-condition match. If qualification cannot be established, mark it unconfirmed. The trigger-modes guide covers that distinction.

A pulse-width trigger condition also does not define every later automatic measurement. Keysight's Infiniium pulse-width measurement reference defines positive and negative widths using the relevant middle-threshold crossings. Its measurement can use a selected region and one or multiple occurrences. These are measurement settings for that instrument family, not universal trigger defaults.

When a saved width looks inconsistent with the trigger setting, compare the source, polarity, crossing definition, region and selected occurrence first. The displayed number may describe another pulse or another definition. Preserve the disagreement until the records explain it.

Try the rule on a fictional record

Consider invented candidate widths of 0.60 ms and 1.20 ms under one consistently defined polarity and threshold. A strict less-than 1.00 ms search condition selects the 0.60 ms candidate. A greater-than 1.00 ms condition selects the 1.20 ms candidate. Changing the operator changes the event being requested.

These numbers are arithmetic examples, not vehicle limits or signals to apply to equipment. A candidate exactly at a boundary needs the actual instrument's documented comparison behavior; do not infer an equality rule from the label alone.

For a shop handoff, pair the selected condition with the saved pulse it identified. Record the relevant crossings and their interval using supported tools. Consult the scope documentation before treating the trigger marker as the beginning of that pulse. Use the separate cursor-measurement guide to retain the measurement definition.

Keep enough context to review the event

A cropped picture containing one narrow feature can leave the next technician unable to identify its channel, units or place in the acquisition. Preserve the original supported data file and setup, together with an annotated view when useful. Confirm which file actually reopens before describing it as retained evidence.

Use an event worksheet with these entries:

• Diagnostic question and source of the proposed comparison criterion.
• Scope, software version, channel identity and complete trigger rule.
• Original acquisition file, record identifier and available timestamps.
• Saved width result, polarity, threshold definition and measurement region.
• Retained context, known gaps and changes between attempts.
• What the event supports, what remains unresolved and the next authorized check.

The pretrigger-window guide covers retaining context before a trigger. A suitable view does not establish uninterrupted observation of everything that happened outside it.

If no event is retained, report the configured search and the observation limits. Do not convert an empty result into proof that the signal never crossed the condition or that the circuit is healthy. If an event is retained, investigate it against the applicable vehicle evidence before naming a failed component.

Request STEP Early Access to discuss how your shop needs to keep capture conditions, saved evidence and the next diagnostic check together.