Diagnostics & Drivability (OBD-II) · SKILL AREA 1 OF 8

OBD-II Modes

OBD-II is the standardized self-diagnostic system every gasoline vehicle sold in the US has carried since 1996.

0 of 8 concepts cleared
At a glance — know these cold
  • Mode $02 (freeze frame) captures RPM, load, coolant temp, fuel trims, and other parameters at the exact moment a code was set. This is invaluable for reproducing the failure condition during diagnosis — the vehicle tells you WHERE it was operating when it failed.
  • Generic OBD-II is the legally-mandated subset (mostly emissions). Enhanced data (accessed via manufacturer-specific protocols or advanced scan tools) reveals transmission, chassis, body, and thousands more manufacturer parameters. Diagnosing modern vehicles beyond emissions requires enhanced scan tool access.
  • OBD-II monitors run automatically when specific drive conditions are met. Readiness status shows whether they've completed since the last code clear or battery disconnect. Failed emissions test may reflect not-ready monitors, not actual failures. Many states require monitors to be 'ready' before an emissions test.
  • Small EVAP leaks are hard to find without a smoke machine. Gas cap is a first check (loose or bad gasket). Then smoke pressurizes the system to find visible smoke escape. Purge and vent valves, canister, hoses, and fuel tank connections are all common leak points. Some vehicles have specific TSBs for common leak locations.
  • OBD-II requires most codes to occur on two consecutive drive cycles before triggering the check engine light and being 'confirmed'. Pending codes are early warnings — useful for catching intermittent issues before they trigger a full code. Some scan tools show them as 'monitor status' or 'pending DTCs'.
  • Mode $06 exposes the raw test data OBD-II monitors use. For example, catalyst efficiency ratios, misfire counts per 200 revolutions, EVAP leak test pressures. When a monitor is 'not ready' or a code is intermittent, Mode $06 shows the underlying values — enabling pinpoint diagnosis.
  • After clearing codes, monitor readiness resets to 'not ready'. Specific drive conditions (varying speeds, temperatures, cruise times) are required to run each monitor. If a monitor isn't run, states won't pass the vehicle. Manufacturer service data specifies each vehicle's drive cycle.
  • P0420 sets when catalyst efficiency drops below spec. Mode $06 shows the actual ratio measured. A rating of 0.05 (barely above 0.02 threshold, for example) means the cat is on its way out. A rating deep in fail range (like 0.001) means completely failed. This detail informs the repair discussion.
Diagnostics & Drivability (OBD-II) training photo
Scan tool on the fender in the field — reading codes before touching a single part.

Knowing what each mode of data offers — and what it can't tell you — is the difference between a tech who reads a code and replaces a part, and a diagnostician who lets the vehicle tell its own story.

The modes that matter: freeze frame and Mode $06

When the ECU sets a trouble code, it doesn't just store the code — Mode $02, the freeze frame, captures a snapshot of engine parameters at the exact moment the fault occurred: RPM, engine load, coolant temperature, fuel trims, vehicle speed, and more. This is your reproduction recipe. If the freeze frame shows the code set at 2,400 RPM, 65 percent load, and full operating temperature, you now know exactly where to drive the vehicle to make the fault happen again. The car is telling you where it was operating when it failed — use that instead of guessing.

Mode $06 goes a level deeper. It exposes the raw test results the OBD-II monitors actually use to decide pass or fail, along with the pass/fail limits: catalyst efficiency ratios, misfire counts per 200 revolutions, EVAP leak test pressures. This is invaluable for marginal or intermittent failures. Take an intermittent P0420 catalyst code: Mode $06 shows the actual efficiency ratio the ECU calculated during the catalyst monitor's test. If the measured ratio sits barely above the failure threshold — say 0.05 against a 0.02 threshold — the converter is degrading but not fully dead, and you can advise the customer on repair timing. A ratio deep in the fail range, like 0.001, means the cat is completely gone. That detail changes the whole repair conversation.

Generic vs. enhanced data

Generic OBD-II is the legally mandated subset of diagnostic data, and it is almost entirely emissions-related — the PIDs and codes every scan tool can read on every vehicle. Manufacturer-enhanced data is everything else: ABS, airbag, transmission, body electrical, and thousands of manufacturer-specific PIDs accessed through manufacturer protocols or capable aftermarket scan tools. If you're diagnosing anything beyond emissions on a modern vehicle — a shift complaint, a body electrical gremlin, a chassis fault — you need enhanced scan tool access. A generic code reader simply cannot see those systems.

Pending codes, confirmed codes, and monitor readiness

OBD-II requires most faults to occur on two consecutive drive cycles before the check engine light illuminates. A fault detected on the first drive cycle is stored as a pending code — no CEL yet. If it repeats on the next drive cycle, it becomes a confirmed code and the light comes on. Pending codes are early warnings, and they're gold for catching intermittent problems before they mature into a full complaint. Always check for them.

Monitor readiness is a separate concept that trips up a lot of techs. The OBD-II system runs a series of self-tests — monitors for the O2 sensors, catalyst, EVAP system, and others — automatically, but only when specific drive conditions are met. Readiness status tells you whether each monitor has completed since the last code clear or battery disconnect. This matters because clearing codes resets all monitors to not-ready, and most states require monitors to show ready before the vehicle can pass an emissions inspection. So after you clear codes following a repair, the vehicle must complete a drive cycle — a specific sequence of speeds, temperatures, and cruise times published in the manufacturer's service data — before it can be emissions tested. A vehicle that fails inspection for not-ready monitors hasn't failed anything; the tests just haven't run yet.

Applying it: chasing an EVAP small leak

A P0442 (EVAP small leak) is a good example of letting the system guide you. Start with the gas cap — verify it's tight and the gasket seals, since that's the cheapest possible fix. But don't stop there and don't blindly replace it. Small EVAP leaks are usually impossible to locate by eye or ear, so the professional tool is a smoke machine: pressurize the EVAP system with smoke and look for where it escapes. Common leak points are the purge and vent valves, the charcoal canister, hoses, and fuel tank connections. Check TSBs too — many vehicles have documented, model-specific leak locations that can save you an hour of hunting.

📋 OBD-II service modes quick reference
ModeNameWhat you use it for
$01Current dataLive PIDs — trims, sensor values, monitor status
$02Freeze frameSnapshot of conditions when the code set — your reproduction recipe
$03Stored codesConfirmed DTCs that turned the CEL on
$06On-board test resultsRaw monitor pass/fail values — catalyst ratios, misfire counts, EVAP pressures
$07Pending codesFaults seen on one drive cycle, not yet confirmed — early warnings
$09Vehicle informationVIN and calibration IDs — verify software before condemning hardware
$0APermanent codesCannot be cleared with a scan tool; only self-clear after the monitor re-runs and passes

Mode $06 data labeling varies by manufacturer — use a scan tool that translates the test IDs, and verify limits against service data.

🔩 Pre-repair data capture — before you clear anything
  1. Read and record every stored and pending code from every module, in the order reported. The code list plus its history is evidence you cannot get back after a clear.
  2. Pull the freeze frame for each stored code and note RPM, load, coolant temp, vehicle speed, and fuel trims. That is the operating point where the fault lives — and where you must test to reproduce it.
  3. Record Mode $06 results for the monitors related to your codes. A value sitting just past its limit means a marginal, intermittent failure; a value far past the limit means a component that is completely gone.
  4. Check monitor readiness status. Monitors showing incomplete tell you which self-tests have not run — and a full set of not-ready monitors is a clue that someone recently cleared codes or disconnected the battery to hide evidence.
  5. Test drive at the freeze-frame conditions with live data graphing to reproduce the fault. A fault you can reproduce on demand is a fault you can prove fixed later.
  6. Only after all of that is documented do you clear codes — and only when the diagnosis calls for it.
⚠️ Comeback killers
  • Clearing codes at the start of diagnosis 'to see what comes back.' You just erased the freeze frame and Mode $06 history, reset every monitor to not-ready, and turned a documented fault into a guessing game. Capture everything first.
  • Treating a pending code as not a real problem. Pending means the fault already happened once and the ECU is waiting for confirmation — it is the cheapest diagnostic lead you will ever get, especially on intermittents.
  • Releasing a vehicle for emissions testing right after clearing codes. Every monitor resets to not-ready and the car fails the inspection for incomplete monitors — it needs a full drive cycle first, and the customer needs to know that before they leave.
  • Declaring 'no codes found' on an ABS, transmission, or body complaint using a generic code reader. Generic OBD-II sees emissions data only; those systems need enhanced scan tool access, and the codes were there the whole time.
🔧 Shop tip Before you clear any codes, record everything: stored codes, pending codes, freeze frame, and Mode $06 results. Once you hit clear, that evidence is gone forever — and you may need it when the customer comes back.
✅ Check yourself
A customer's P0420 is intermittent. Mode $06 shows the catalyst monitor result just barely past the failure threshold. What do you tell them?

The converter is marginal — degrading, but not dead. It fails the monitor some drive cycles and passes others, which is exactly why the code is intermittent. The honest advice is that the catalyst is on its way out and the code will become permanent; they can plan the repair rather than being surprised by it. A result deep past the threshold would instead mean the cat is completely done.

A vehicle fails a state emissions inspection for 'monitors not ready' with no codes stored. What actually happened, and what is the fix?

Nothing failed. Codes were recently cleared or the battery was disconnected, which reset all monitors to incomplete, and the self-tests have not re-run yet. The fix is a proper drive cycle — the manufacturer's published sequence of speeds, temperatures, and cruise times — until the required monitors show ready, then retest.

Freeze frame for a P0171 lean code shows 2,600 RPM, 70 percent load, full operating temperature. Where do you do your testing?

At those conditions — under load at mid-RPM, not idling in the bay. The freeze frame says the lean condition exists at high airflow, which points away from a vacuum leak (worst at idle) and toward fuel delivery: pump volume, filter restriction, or injector capacity. Testing at idle would likely show nothing wrong.

WORK THE CALL 3 decisions

A customer's P0420 is intermittent. Mode $06 shows the catalyst monitor result just barely past the failure threshold. What do you tell them?

Know this cold? Get certified in Diagnostics and Drivability and show it on your listing. See what drivers pay for this work in our catalytic converter replacement cost and fuel pump replacement cost guides.

🇲🇽 Lee esta lección en español