Known Good Waveforms — Using Reference Patterns for Diagnostics

Why known good waveforms matter

A scope trace on its own is just a shape. It only becomes a diagnosis when you compare it against a known good waveform — a reference capture from a healthy component on the same (or an equivalent) vehicle. That reference tells you what "normal" looks like for the exact signal you're chasing: the correct amplitude, the correct edges, the correct ringing pattern, the correct dwell.

Without a reference, you're guessing. With one, a five-second overlay tells you whether the injector opens too slowly, the coil is arcing internally, the crank sensor gap is wrong, or the CAN bus is being pulled down by a shorted module.

What to compare: the three deviation categories

1. Timing

Does the event happen when it should, and does it last the right amount of time? Examples: injector pulse-width vs. commanded ms, coil dwell in ms, crank/cam relative phase, ABS pulses per revolution. Timing drift usually points to a control or mechanical fault (worn timing chain, weak actuator, wrong reluctor gap).

2. Amplitude

Does the signal reach the expected voltage or current? A COP firing line that peaks at 8 kV instead of 15 kV means low cylinder pressure or open plug gap. An injector current that plateaus at 0.8 A instead of 1.0 A means a stretched winding or high supply-side resistance.

3. Signal integrity

Does the trace look clean, or is it noisy, missing edges, or ringing abnormally? A ragged crank sensor pattern, glitches on a CAN differential, or a rounded rising edge on a Hall-effect square wave all point at wiring, shielding, or a failing sensor — even when the "average" shape looks right.

Where reference patterns come from

• PicoScope Waveform Library — the largest public collection of automotive scope captures, indexed by signal type and vehicle. If you own a Pico, you already have direct access from the software.
• AESwave / ATG training libraries — curated by working instructors, with narrative explanations of what each trace shows.
• OEM service information — a small subset of manufacturers publish expected sensor waveforms in their factory service manuals.
• WaveWrench Pro's built-in baselines — reference patterns for cranking current, secondary ignition, COP primary, saturated and peak-and-hold injectors, MAF, MAP, O2, crank/cam, and CAN differentials are shipped with the analyzer so you can compare in one click.

Hardware: it doesn't matter what captured the trace

A known good waveform recorded on a PicoScope, a Snap-on Verus, an Autel MaxiScope, a Hantek, or a screenshot from a phone-based scope is still a valid reference — provided the timebase and voltage scale are noted. WaveWrench Pro reads uploaded PicoScope waveforms (PNG, JPG, or exported CSV) the same way it reads captures from any other brand, and normalizes them against the internal baselines before scoring.

If you're evaluating a scope purchase specifically for waveform comparison work, prioritize (in order): sample memory depth, glitch/edge trigger support, and differential probe options. Screen size and pretty UI matter far less than being able to catch the intermittent event in the first place — see the intermittent fault capture guide below.

A repeatable comparison workflow

1. Identify the signal exactly. Not "injector" — "saturated port-fuel injector, bank 1, cylinder 3, hot idle, 14.2 V system voltage."
2. Pull the reference. Same signal type, same operating condition. Amplitude and pulse-width shift with RPM and load, so match the state.
3. Match scale before you match shape. Set your capture to the same V/div and time/div as the reference, or the eye lies to you.
4. Walk the three categories in order: timing first, then amplitude, then integrity. Most faults show up in one category clearly; edge cases show up in two.
5. Confirm mechanically. A waveform deviation is a hypothesis, not a verdict. Follow up with a pressure test, leakdown, resistance measurement, or scan-tool bidirectional command before quoting parts.

Where WaveWrench Pro fits in

Manual library lookup is slow and error-prone: you have to know which reference to search for, find one that matches the operating state, and eyeball the overlay. WaveWrench Pro collapses that into one action — upload the capture, tell it the signal type and vehicle, and the analyzer overlays it against the matching baseline, quantifies the timing/amplitude/integrity deviations, and ranks the most likely causes with a technician-grade explanation.

You still make the call. The analyzer just removes the "where did I put that PDF" step from every diagnosis.

Frequently asked questions

Related guides

• Automotive oscilloscope guide →
• Ignition waveform diagnosis →
• Fuel injector waveforms →
• Relative compression test →
• Intermittent fault capture →
• Triggers & timebase →