Mode $06 provides onboard monitor test results where the vehicle and scanner support them. Correctly identified and decoded results can add context, but a failed result alone does not identify the component to replace.
Know which test you are looking at
A result may include a monitor or test identifier, component identifier, measured value and limits. Labels, scaling and supported tests vary by vehicle generation and scanner implementation.
Some scanners translate the results into readable descriptions; others expose hexadecimal IDs or raw values. A plausible label does not remove the need to check the definition against reliable service information.
Check the timing and the limits
Determine whether the monitor has actually run and which operating window the result represents. Stored monitor results are not always continuous live data. A zero or unavailable result is not automatically a pass.
Compare the measured value with the limit for that particular test and unit. Some tests have upper limits, lower limits or both. A value that seems close to a limit does not, by itself, establish how long a part will last.
Read one result all the way through
Start with the test identity, its units, its limits and whether it has completed. For a fictional test that passes at or below an upper limit of 100 units, a decoded result of 60 is within the limit; 120 exceeds it. Those numbers teach the comparison only. They are not a catalyst, oxygen-sensor or misfire specification.
Before applying the same logic to your scanner, check:
- Is this the correct monitor and component for the vehicle?
- Are the value and limits decoded in the same units?
- Does the test use an upper limit, a lower limit or a permitted range?
- Has the test completed, and does this record belong to the operating period you need to assess?
If the label, scaling or timing cannot be verified, save the screen and mark the result unresolved. Do not replace a part on the strength of a red status label or a raw number you cannot interpret. Continue with codes, symptoms and a vehicle-specific diagnostic procedure.
Be careful with misfire interpretation
On some vehicles, Mode $06 includes useful cylinder-related misfire information. On others, enhanced manufacturer PIDs provide a clearer view. Do not assume every scan tool will display universal live misfire counters on every engine.
Connect the result with the symptoms, freeze frame and controlled tests. A high count can direct attention to a cylinder but does not distinguish ignition, fuel and mechanical causes by itself. Before comparing two screens, identify whether each value is a current-cycle count, a previous-cycle record, an average or a rate over a defined number of revolutions. Do not subtract unlike records or call a larger raw count a worsening misfire without comparable observation windows.
Use it to support verification
Once a repair is completed, correctly decoded monitor results can help demonstrate that the relevant test passed after it had an opportunity to run. They should agree with the vehicle's behavior and other scan information.
Record the identifiers, units, limits, completion status and reporting window with the value. If a stored failure remains after a repair, establish whether the relevant monitor has run again before calling it a repeat failure. If it has not rerun, report verification as incomplete. A later result must be matched to the same test definition before it becomes a useful before/after comparison.
References & scope
These background references explain selected concepts. The diagnostic sequence is an original, general educational guide; it is not a reproduced factory procedure. Confirm specifications, test limits, cylinder layout and circuit details in the service information for the actual vehicle.
- Innova: overview of OBD data modes, including live data, freeze frame and monitor results
- Innova: example of vehicle-specific scanner coverage requirements
- Ford: example of vehicle-specific Mode $06 test identifiers and limits (2024–2025 gasoline OBD summary).
This is general education, not a vehicle-specific repair procedure or hands-on test. Read the editorial policy.