Automotive Oscilloscope Pre-Trigger: Budget the Time Before and After the Event

A trigger can capture an intermittent event while leaving too little history to explain what preceded it. Pre-trigger planning addresses that gap: decide how much time must remain before the event, how much must remain after it, and whether the acquired record actually meets that plan.

This guide gives professional mechanics a time-budget worksheet. For trigger mode and qualifying conditions, use the separate trigger modes guide. Here the question is the duration of evidence retained around a qualifying event.

A percentage needs a duration

Pico's trigger guidance describes pre-trigger as a percentage that positions the zero-time point within the view. The setting allocates context around that point. It does not tell you, by itself, how many seconds of history are available.

Check your instrument's definition of record duration and horizontal position. Separate the complete acquired time span from a later zoomed view. Also check whether a trigger delay or another timing control changes where the actual event appears.

The PicoScope introductory guide illustrates how the same total time span can contain different amounts of pre-event history when the percentage changes. Use the principle; do not copy its software controls or example settings as a vehicle test specification.

Work backward from the unanswered question

Before configuring the scope, write two durations in the job notes:

• Required history: how far before the chosen event must the record extend?
• Required follow-up: how long after it must the record continue to show the behavior being investigated?

These are evidence requirements for the particular complaint. They are not universal settings. A brief transition and a slow recovery may call for different windows. If the required duration is unknown, document a trial plan and review what it captures before making a stronger conclusion.

For a record with no added trigger delay, an illustrative planning calculation is: before-event duration = total duration multiplied by the pre-trigger fraction. The remaining fraction supplies the after-event duration. Confirm the acquired time axis instead of assuming the controls produced the intended allocation.

Fictional example: percentage alone loses the budget

A technician wants 3 seconds of history and 1 second of follow-up around an intermittent event. An illustrative 4-second record with 75% allocated before the event meets that time budget: 4 multiplied by 0.75 gives 3 seconds before; 1 second remains after.

If the total record is changed to 2 seconds while 75% is retained, the budget becomes 1.5 seconds before and 0.5 seconds after. The percentage is unchanged, but both evidence requirements are now missed.

This is original planning arithmetic, not a recommended scope configuration for a vehicle. The required channel, event, input rating, sample detail and operating condition must still be established separately.

Verify the actual record

Tektronix explains pre-trigger viewing as a way to examine signal behavior before a trigger event. Earlier observations can help investigate sequence; temporal order alone does not prove that one component caused another to fail.

Review the saved acquisition for these points:

• Identify the actual trigger event and the first and last recorded times.
• Check that the required history and follow-up are present.
• Confirm channel labels, references, scaling and operating conditions.
• Retain acquisition settings and the original file where supported.
• State whether the complaint occurred and whether any required interval is missing.

Revisit the aliasing guide when extending the time span. A longer record still needs adequate sampling for the feature of interest. This guide does not promise continuous gap-free acquisition, unlimited history or identical behavior across scope models.

Follow vehicle and instrument instructions for safe measurements. Verify the setup using an allowed operating change; do not create a fault or an unsafe condition merely to test capture timing.

Hand off the missing interval honestly

A useful fictional note says: “The capture contains the event and recovery, but only half the planned history. It cannot answer what happened earlier; another acquisition is required.” That conclusion preserves the value of the existing record while defining its limit.

Download the capture-window worksheet above and retain planned versus actual durations. STEP is in Early Access. Request early access to discuss organizing your shop's diagnostic evidence and next tests. This guide does not imply automatic waveform capture or causation analysis by STEP.