Mechanic Guides
Automotive Oscilloscope Persistence: Save the Capture Behind the Color
Separate persistence colors from individual capture history before interpreting an automotive waveform outlier. Includes an original three-part evidence handoff card.
Published · 5 min read
Quick answer
Persistence combines acquired waveform points into a display. Read its colors using the selected mode and legend, then preserve individual acquisitions when the tool supports them. A composite screenshot alone does not establish event order, a complete history or a failed component.
Decide what the colored view needs to answer
An overlaid trace can help a mechanic notice a departure that is difficult to see in a changing display. The next decision is whether the saved evidence supports investigating that departure. A useful handoff identifies both the display that drew attention to it and the underlying acquisition that another technician can inspect.
This is a file-review and documentation workflow. Follow the applicable vehicle and equipment instructions for connections, mounting and any permitted acquisition. It supplies no universal trigger, test-drive maneuver, component acceptance threshold or safe method for an unknown circuit.
Read the legend before interpreting a color
Pico's automotive persistence guidance, updated November 25, 2025, describes incoming waveforms overlaid into a composite. Its Time mode uses intensity to represent age; its Frequency mode uses color to represent how often waveform data occurs in the display. Saturation and decay controls affect the view. Those meanings belong to the identified mode and configuration.
For the shop record, write the mode, legend and display settings before describing a colored outlier. A color representing less frequent displayed data is not, by itself, a counted vehicle fault. In this context, Frequency describes the display population; do not report that color as a frequency measurement in hertz.
State exactly what was observed: a departure in the displayed trace, the relevant channel and the operating condition if known. Keep a proposed explanation in a separate entry. The color alone does not identify which vehicle component caused the departure.
Distinguish a composite from selectable waveforms
Keysight's FlexDCA persistence documentation explicitly distinguishes display memory from acquisition memory for that instrument family. It illustrates why visible accumulated points and retained waveform records are separate questions. Check the actual shop tool's documentation and saved files before promising that an older trace can be selected again.
Pico's waveform buffer overlay explanation, updated December 9, 2025, contrasts blended persistence samples with overlays that keep individual buffers as waveform layers. The article describes a feature introduced in PicoScope 7.1.58 Early Access and warns that its functionality may change. Verify the installed version and supported behavior; do not assume every persistence mode or oscilloscope provides the same history.
When supported data is available, locate the individual acquisition containing the departure and retain its recorded companion channels. Confirm what actually reopens. If only a screenshot survives, describe it as a composite image and record the unavailable raw waveform data. A plausible reconstruction would create evidence the original file does not contain.
Build a three-part evidence handoff
Use three linked entries for the same observation:
- Composite view: screenshot or supported export, channel legend, persistence type, decay, saturation and any known clear/reset boundary.
- Acquisition evidence: original supported data file, selected buffer or record identifier, available timestamps, units, scaling, coupling and relevant companion channels.
- Coverage note: what interval and captures are actually retained, known gaps or unavailable timing, operating conditions and the next verification question.
The file names and links are the shop's documentation choices, not a promise of an automatic tool export. A timestamp that is absent should remain absent. Do not infer event order from intensity unless the selected mode and retained evidence support that specific interpretation.
Pico's automotive memory-buffer overview describes reviewing stored acquisitions separately from a single displayed waveform. For a particular job, verify the retained records rather than importing a catalog capacity into the case note. A stated maximum buffer count does not document how many useful records this test actually saved.
Check the files before changing the view
Before clearing a display or beginning another permitted capture, use the instrument's supported save process for the evidence you need. Reopen the saved data and check that the relevant acquisition, channels, units and context are present. Keep the composite image as an annotation linked to that file, rather than using it to fill gaps in the underlying data.
A fictional handoff contains a composite screenshot with a faint departure. The file package also contains selectable acquisitions, but the technician has not yet identified which one corresponds to it. The useful next step is to inspect the retained records and document the match or the remaining uncertainty. Reporting a fault count or replacing a part from the screenshot would exceed the evidence.
Keep waveform averaging and saved reference waveforms identified as separate processing and comparison choices. Neither label supplies the missing acquisition history of a persistence image. Request STEP Early Access to discuss the capture files, limitations and next checks your shop needs to preserve during a diagnostic handoff.