Was this article helpful?
OBD codes and the emissions test: what actually fails you
Most emissions-test failures on modern cars are not about exhaust gas at all. They are about the lamp being lit and the monitors not being ready — both checkable in your driveway.
On a modern car the emissions portion of a roadworthiness test is largely an interrogation of the OBD system rather than a measurement of the exhaust. Understanding what the tester’s tool asks for means you can ask the same questions yourself the week before.
The three things being checked
1. Is the malfunction indicator lamp working?
The tester watches the dashboard during the ignition-on self-test. The check engine light must illuminate with ignition on, then extinguish once the engine runs.
A bulb that never lights is a fail. This catches the old trick of removing the bulb to hide a fault, and it also catches an innocent blown LED.
2. Is the lamp lit with the engine running?
If it is, that is a fail on most modern test regimes regardless of what the code is or how clean the exhaust measures. The lamp itself is the criterion.
3. Are the readiness monitors complete?
This is the one that catches people out, and it is not about anything being broken.
The readiness trap
Each emissions-related system has a self-test — a monitor. Monitors report “ready” once they have run to completion, and “not ready” if they have not.
Testers typically allow one or two incomplete monitors, sometimes none depending on the vehicle age and the regime. Beyond that: fail.
Clearing codes resets every monitor to not-ready. So the classic sequence is:
- The light comes on a week before the test.
- The owner clears the code. The light goes out.
- They drive straight to the test station.
- The car fails — not on emissions, but on readiness.
The car may be in perfect condition. It simply cannot prove it yet. Detail: OBD readiness monitors explained and, on Ford-family cars, P1000.
Disconnecting the battery does exactly the same thing, which catches people who have just had a battery replaced.
Getting the monitors ready
Monitors complete only when their entry conditions are met. A generic cycle that satisfies most of them:
- Cold start after standing overnight — required, not optional.
- Idle two to three minutes.
- Steady 40 mph cruise for five minutes.
- Coast down without braking from 40 to about 20 mph in gear.
- Motorway cruise for five to ten minutes.
- Repeat over two or three days of normal driving.
Keep the tank between a quarter and three quarters full throughout — the EVAP monitor will not run outside that window, and EVAP is the monitor that most often stays stubbornly incomplete. Step-by-step: OBD drive cycle.
Which codes are emissions-related
Not every stored code affects the test, but the lamp does not distinguish — if it is lit, you fail.
Codes that commonly cause trouble:
- Catalyst efficiency — P0420, P0430.
- EVAP leaks — P0442, P0455, P0456.
- Oxygen sensors — P0131 and P0132, P0133.
- Mixture — P0171 and P0174.
- Misfire — P0300 and cylinder-specific ones.
- EGR — P0404.
- DPF on diesels — P2002 and P2463.
Diesels get measured as well
Diesel testing usually includes an opacity measurement, which is a genuine physical test rather than a data query. A blocked or removed DPF fails it outright, and a car with a gutted filter also tends to store P2002, which lights the lamp.
Removing a DPF is illegal on a road car in most jurisdictions and is checked visually in an increasing number of test regimes. See exhaust modification and emissions.
Tampering is detectable
Test equipment reads the calibration ID and calibration verification number through Mode 09. A remap that changed emissions calibration can be visible there. Related: ECU remap detection through OBD.
Emulators that spoof a missing sensor are similarly detectable, because the plausibility checks the ECU runs are hard to fake convincingly across all conditions.
The week before: a checklist
- Read stored and pending codes. A pending code today is a lit lamp tomorrow.
- Check every monitor reads ready.
- Confirm the lamp illuminates at ignition-on and goes out when running.
- Keep the tank around half full.
- Do not clear anything.
- Fix genuine faults, then drive a week before booking.
Broader preparation: technical inspection preparation.
If you already failed on readiness
Nothing is broken. Drive the cycle above for two or three days, verify the monitors, and retest. There is no shortcut — the monitors run on the car’s schedule, not yours.
Try it on the free tier of the app — pair an ELM327 adapter and read the readiness list the week before your appointment. Two minutes in the driveway is considerably cheaper than a failed test and a second booking.
Read next
Comments …
Loading…