STEP Diagnostics
STEP Diagnostics
Mechanic guides

Mechanic Guides

Automotive Oscilloscope Bandwidth Limit: Save the Evidence Before Filtering

Preserve original automotive scope evidence when comparing bandwidth limits and software filters. Includes a filter comparison record.

Published · 5 min read

Quick answer

A bandwidth limit can suppress useful signal detail along with noise. Save the original acquisition and record whether filtering happened before digitization or in software. Removing a display filter is not the same as recovering detail excluded during acquisition.

Download the filter comparison record
Blank unbranded oscilloscope beside an orange translucent panel and metal spheres of different sizes.
Concept illustration; not a real measurement, product interface or vehicle test setup.

A cleaner trace is not automatically a more complete record. A bandwidth limit reduces higher-frequency content, which may include both unwanted noise and details relevant to the fault. Decide what the test needs to preserve before enabling it, and record the filter state with every capture.

Ask what the capture must answer

Write the diagnostic question before changing the display. Are you comparing a slow level, looking for a short disturbance, or examining an edge? A setting useful for the first question may hide information needed for the others. Follow the vehicle test procedure and the scope manufacturer's guidance for the particular measurement.

A filter does not know which part of a waveform belongs to the complaint. Calling an irregularity noise is an interpretation that needs evidence. Do not make it disappear first and use the cleaner result as proof that the circuit is healthy.

Identify where filtering happens

An analog bandwidth limit acts before digitization. Its effect becomes part of the acquired record; turning the option off later does not restore the original input from that saved capture. A new acquisition is needed to compare with the limit disabled.

Software filtering acts on acquired samples. Some systems allow it to be removed from a saved native record, but confirm how the exact instrument stores and exports its data. A screenshot or processed export should not be assumed to contain a recoverable original. Keep the native acquisition when available and retain a clearly identified unprocessed view.

Filter names, cutoff values and available modes vary. Do not copy another technician's cutoff simply because their trace looks good. The required signal detail, probe and instrument capabilities determine whether a setting is suitable.

Make the comparison controlled

Save the initial acquisition and its settings before making changes. Check the test point, reference, probe scaling, coupling, time window and sampling settings. The probe attenuation guide covers scaling; the aliasing guide explains why sampling is a separate concern.

For a hardware-filter comparison, acquire another record under comparable vehicle conditions. Record any condition that changed between captures. Differences between two runs cannot automatically be assigned to filtering if the vehicle state changed too.

For a software-filter comparison on the same retained data, label the original and processed views. Check whether displayed measurements use the processed trace. A changed numerical result after processing needs that context, not an unexplained replacement value in the repair order.

Fictional handoff: a clean picture with an unanswered question

A technician saves a smooth-looking supply trace with an acquisition bandwidth limit enabled. The complaint is an intermittent reset, and the next technician asks whether a short disturbance was present. The saved image cannot settle that question merely because it looks clean.

The handoff identifies the acquisition limit and preserves the original file. The next test plan calls for a suitable capture capable of observing the event of interest, under the vehicle and instrument procedures. If the symptom does not recur, the record says so. It does not convert a different observation window into proof that the first setting concealed a particular fault.

Keep a filter comparison record

Attach the following information to the captures so another technician can understand the comparison:

  • Vehicle condition, symptom and diagnostic question.
  • Scope, probe, test point and measurement reference.
  • Acquisition bandwidth limit and software filter settings, separately.
  • Native capture filenames and which view is original or processed.
  • Time window, sampling settings and trigger condition.
  • Differences observed and any changed vehicle conditions.
  • What the comparison supports, what it cannot establish, and the next test.

Use the downloadable record above to keep those details together. STEP is in Early Access. Request early access to discuss organizing diagnostic evidence and next tests in your shop. This guide does not imply automatic waveform processing or oscilloscope integration by STEP.

Continue with STEP

Keep the evidence and the next test together

STEP is being built for guided diagnostic work with vehicle context, sources and completed checks. Join early access and share the workflow your shop needs.

Request Early Access