Beyond P-codes — B, C, and U codes, and why your scanner can’t see them

Here's a rite of passage: the ABS light (or the airbag light) comes on, you plug in the little code reader you keep in the glovebox, and it says no codes found. The car is not lying to you, and the reader isn't broken. They're just not speaking to the same computers. Your car stores fault codes in four families. Your reader can only see one of them.

The four families (SAE J2012)

Every diagnostic trouble code follows the SAE J2012 format: five characters, where the first letter names the family — the part of the car reporting the fault. The second character tells you whether the code is generic (defined by the standard, same meaning on every car — typically a 0) or manufacturer-specific (defined by the carmaker — typically a 1). The remaining characters narrow it down to a subsystem and the specific fault. Learn the four letters and a code number stops being alphabet soup.

P — Powertrain: the codes you already know

Engine and transmission: misfires, fuel trim, EVAP, catalysts, sensors. This is the family the federal OBD-II mandate covers, because these are the emissions-relevant faults — and it's the family a basic reader can see. If your check-engine light is on, the code starts with P (or occasionally U, when the engine computer itself can't be reached).

B — Body: airbags, comfort, and the cabin

Body modules run the stuff that isn't the drivetrain or the brakes: the airbag/SRS system, HVAC, lighting, power seats and windows, door locks, and security. An airbag light is a B-code story — for example B0001, a fault in the driver's airbag deployment circuit. A generic reader plugged into a car with the airbag light on will cheerfully report “no codes found,” because it never asked the body modules.

C — Chassis: brakes, steering, and stability

Chassis codes live in the ABS, traction and stability control, electric power steering, and electronic suspension modules. The classic example is a wheel-speed sensor fault like C0035 (left front wheel speed sensor circuit) — one bad sensor signal, and the ABS and stability systems that depend on it light up the dash and partially shut down. The engine runs perfectly; a P-code reader sees nothing.

U — Network: modules that can't talk

Modern cars are dozens of computers on a shared network (the CAN bus). U-codes report communication failures between them — U0100, “lost communication with the engine control module,” is the famous one. U-codes often aren't a failed part at all: low battery voltage, a bad ground, or wiring damage can make healthy modules go silent, which is why a pile of U-codes plus random others usually means “check power and grounds first.”

So why does the cheap reader only see P?

Because that's all the law ever required it to see. The OBD-II standard guarantees access to the generic emissions-related diagnostics — the powertrain data every car must expose in the same way, so an inspector (or a $30 reader) can talk to any make. That's the generic protocol, and it's genuinely useful: it's the whole check-engine-light world.

Everything else — ABS, airbags, body modules, steering, the network itself — is reached through manufacturer-enhanced diagnostics: the carmaker's own deeper access to its other modules. A basic reader doesn't speak it, so to that reader, those modules and their codes simply don't exist. “No codes found” really means “no P-codes found.” Same reason the free scan at the parts counter usually reads P only: they're handing you the same generic read, and it's an honest answer to a narrower question than the one your dashboard is asking.

What does read the rest?

The practical playbook

  1. Let the light tell you the family. Check-engine light → P. ABS / traction / stability light → C. Airbag light → B (SRS). Several unrelated lights at once, or modules acting haunted → suspect U, voltage, and grounds.
  2. Match the scan to the light. If the glowing light isn't the check-engine light, a generic P-scan — yours or the parts store's — cannot answer it. You need a C/B-capable scan: your own mid-tier or make-specific tool, an independent shop, or the dealer.
  3. Write the codes down exactly — letter, digits, and which module reported them — before anyone clears anything. A cleared code that isn't recorded is a diagnosis thrown away.
  4. Look the code up before buying anything. Every family is in the full code index; the Fix Index ranks the likely causes once you know what you're chasing.

Pending, stored, permanent: three kinds of P-code

Within the P family, the same fault can appear in three states, and scanners list them separately:

One connected note: wheel-speed and tire-pressure faults straddle the P/C line — a sensor that stops reporting can set chassis codes and light up more than one system. If a cold snap just lit your dash, start with the cold-morning TPMS verdict before assuming the worst, and the warning lights hub will tell you what each light is actually claiming.