A ten-dollar ELM327 adapter, this page, and your browser talks straight to the car — fault codes explained, live gauges, VIN. No app, no server, no $150 diagnostic fee for a code number.
Plug the adapter into the port under the dash, ignition on — then pick your connection. No adapter yet? The demo runs the whole flow on a canned car.
Job number one: the orange light came on during a motorway drive and the garage's earliest slot was Thursday. Four days of imagining gearbox surgery. Thursday's verdict took the mechanic ninety seconds: plugged a reader in, said "loose fuel cap, forty quid for the diagnostic," and clicked the light off. Forty quid to be told a number a ten-dollar dongle reads, translated by a lookup table older than my driving licence. The protocol is public. The port is under every dashboard by law. Browsers can open serial ports now. There was no missing piece except a page that put them together — so here's the page, and may your Thursday-dread be ninety seconds long too.
— the cap gets hand-tightened with ceremony now, twice
the same conversation a handheld scanner has
the honesty panel, bolted on
the questions the bay actually gets
Almost certainly classic Bluetooth, not BLE — browsers can only reach the LE kind. The listing will say "4.0" or "BLE" if it's the right sort; USB adapters dodge the whole question and cost the same.
A passenger can, happily — the live readout polls continuously. The driver's job is driving; mount the device or hand it over.
Ignition on (engine can be off but key to run), adapter seated firmly, and give it one retry — auto-detect occasionally needs a second run. Ancient pre-1996 cars simply don't have OBD2, and a few EVs decline the standard queries.
For generic engine codes, live basics and the VIN — same data, same protocol. Dealer tools add manufacturer modules, actuator tests and coding this page doesn't pretend to do. Think of it as the difference between reading the patient's chart and performing surgery: the chart is free now.
That'll be a permanent code, and it's working as designed. Since roughly 2010 cars keep a second, sealed copy of an emissions fault that no scan tool can erase — not this page, not the garage's, not the dealer's. The car itself deletes it, once it has run its own checks over several drives and satisfied itself the fault is genuinely gone. It exists precisely to stop anyone clearing codes in the car park on the way to an inspection. Fix the fault, drive it a week, and it goes on its own.
Press emissions readiness and the car tells you directly. It runs a set of self-checks as you drive — catalyst, oxygen sensors, EVAP and so on — and each is either finished or still running. Most programmes allow one unfinished (two on 1996–2000 cars), though the rule varies by where you are, and a lit lamp fails on its own regardless. If several are still running, the usual cause is that somebody cleared the codes recently: a week of ordinary mixed driving normally finishes them off.
The marks behind the readiness panel. Readiness says whether each self-check finished; test results show what each check actually measured, and the pass window the car judged it against — press it on the demo car and you'll see the catalyst scoring 900 against a 0–800 window, which is the P0420 in numbers. Each test speaks its own units, so this page shows the raw figures rather than guessing conversions: what matters is whether the value sits inside its window, which is exactly how the car decides. Older pre-CAN cars keep these results in manufacturer code, and the page says so instead of decoding them wrongly.
Because it's the most-Googled fault code on earth, so the demo may as well teach it: catalyst efficiency low, usually an oxygen sensor or a tired catalytic converter, rarely urgent, worth diagnosing before parts-cannon-ing.
longer reads, greasy thumbprints included
what changed, newest first