Mode $06 Diagnostics: Reading Raw Diagnostic Test Results Before DTCs Trigger

What Is OBD2 Mode $06?

Standard OBD2 scan tools typically interact with the vehicle using Mode $01 (live parameter data) and Mode $03 (stored diagnostic trouble codes). However, the vehicle's powertrain control module performs dozens of continuous and non-continuous self-tests behind the scenes every time you drive. The raw engineering results of these internal diagnostic tests are stored in Mode $06.

Mode $06 is the vehicle's diagnostic workbench. While a standard code reader will report "No trouble codes found" simply because a fault has not yet exceeded the strict two-trip threshold required to turn on the Check Engine Light, Mode $06 reveals the exact numerical values measured during the latest test cycle alongside the manufacturer's calibrated minimum and maximum pass/fail limits.

By reviewing Mode $06 data with OBDAssistant, you can identify a deteriorating component—such as an ignition coil experiencing intermittent misfires, an oxygen sensor losing response speed, or a catalytic converter losing chemical conversion efficiency—weeks before the fault becomes severe enough to illuminate the dashboard MIL.

Decoding Test IDs (TID) and Component IDs (CID)

Historically, Mode $06 data was notoriously difficult for mechanics to interpret because early vehicles output raw hexadecimal numbers without standard text definitions. For example, a scanner might display TID $0B CID $01 VAL: 002A MAX: 0032 without explaining what was being tested.

On CAN-bus compliant vehicles (2008 and newer in North America and Europe), Mode $06 is standardized under ISO 15765-4 and SAE J1979. In this standardized format:

• OBDMID (OBD Monitor ID): Defines the exact vehicle system being tested (e.g., MID $A2 for Cylinder 1 Misfire Monitor, MID $21 for Catalyst Monitor Bank 1, MID $3B for EVAP System Monitor).
• TID (Test ID): Identifies the specific physical measurement algorithm executed (e.g., peak-to-peak voltage, transition time in milliseconds, or pressure decay rate in Pascals).
• Test Value: The raw measured physical reading during the latest diagnostic trip.
• Min / Max Limits: The pass/fail boundaries programmed into the engine calibration software. If the measured test value exceeds the maximum limit or falls below the minimum limit, the monitor fails.

Mode $06 Telemetry Reference Table

Here are typical Mode $06 monitor benchmarks for common powertrain subsystems:

How Technicians Use Mode $06 to Solve Intermittent Misfires

The most frequent trade application of Mode $06 is diagnosing elusive, intermittent engine misfires that produce a noticeable hesitation or jerk during acceleration, but do not set a permanent P0300 or cylinder-specific code like P0301.

1. Access Cylinder Misfire Monitors: Connect OBDAssistant and navigate to Mode $06 Diagnostic Monitors. Select Misfire Monitor (MID $A2 through MID $A8 for Cylinders 1 through 8).
2. Inspect Current Driving Cycle Counters: Review the raw misfire counts logged during the current 1,000-revolution evaluation window. If Cylinder 3 reports 42 misfire counts while all other cylinders report 0, but the threshold to illuminate the Check Engine Light is 50 counts, you have caught the failing component before the ECU triggered a MIL.
3. Execute Swap Verification: Swap the ignition coil from Cylinder 3 to Cylinder 1. Clear the Mode $06 buffer, take the vehicle on a 10-minute road test, and re-query Mode $06. If the misfire count shifts to Cylinder 1, the ignition coil is bad. If the misfire remains on Cylinder 3, inspect the spark plug, fuel injector, or cylinder mechanical compression.
4. Verify EVAP & Catalyst Monitors: Mode $06 is equally crucial when performing pre-inspection emissions testing or verifying repairs for P0420 and P0442 without waiting days for the vehicle to complete full drive cycles.