How to Read an OBD-II Fault Code: What P0, P1, P2, P3 and U-Codes Mean

An apprentice plugs in a scan tool, gets a P0301, and reads it out like the job is done: “misfire on cylinder 1.” It isn’t. That five-character code is a starting point, not a diagnosis, and workshops that treat it as the final word end up swapping coil packs and injectors that were never the problem.

Break the code into its parts

Every OBD-II code has the same skeleton: one letter, one digit, then three more digits. Learn to read each part on its own before you look anything up.

• The letter tells you the system. P is powertrain (engine and transmission), B is body (airbags, climate, lighting), C is chassis (ABS, steering, suspension), U is network (communication between modules).
• The first digit tells you whether the code is generic (SAE-defined, the same across every manufacturer) or manufacturer-specific. A 0 in that position means generic: P0301 means the same thing on a Ford as it does on a Fiat. A 1 means manufacturer-specific: the code exists in that brand’s own list and the definition can be completely different from one maker to another.
• The second digit narrows the subsystem. In powertrain codes, 1 and 2 usually point to fuel and air metering, 3 to ignition or misfire, 4 to auxiliary emission controls, 5 to speed and idle control, 6 to computer output circuits, 7 and 8 to transmission.
• The last two digits identify the specific fault within that subsystem.

Worked examples

P0301: P (powertrain), 0 (generic), 3 (ignition/misfire group), 01 (cylinder 1 specifically). Compare that with P0171, which is P (powertrain), 0 (generic), 1 (fuel and air metering), 71 (system too lean, bank 1). Same letter, same generic flag, completely different subsystem because of the second digit.

Now a manufacturer-specific one: P1613 on a VAG diesel isn’t in the generic SAE list at all, it needs the brand’s own code table, which is exactly why the same four digits after “P1” can mean something totally different on a Vauxhall than on a Peugeot.

P2 and P3 codes, and U-codes

P2xxx codes are also SAE-generic but were added later, covering things the original P0/P1 scheme didn’t have room for: direct injection fuel trim, secondary air, hybrid-specific faults. P3xxx is a mixed bag, some generic, some manufacturer-specific, mostly used for hybrid and direct ignition systems. U0xxx codes are network faults: U0100 for lost communication with the ECM, U0121 for lost communication with the ABS module. These matter because a U-code often means the fault isn’t in the component at all, it’s in the wiring or the module raising the code.

Why this matters on the bench

A generic code (second character 0) means you can trust a generic repair database or a general explanation. A manufacturer-specific code needs the OEM’s own definition, guessing from a generic description sends you chasing the wrong circuit. This is where a lot of wasted hours come from: someone reads “P1” and assumes it means something rare, when actually it just means “look this one up properly instead of relying on memory.”

Before you condemn a part, check the freeze frame data alongside the code, and confirm whether it’s stored as a hard fault or an intermittent one. A code tells you where the ECU noticed a problem. It doesn’t tell you why, and it definitely doesn’t tell you which of three possible causes is the actual one sitting in front of you.

If a code doesn’t match anything in a generic list, it’s worth checking whether the ECU variant fitted matches what’s expected, sometimes a code shows up because of a mismatch after a repair rather than an original fault. For background on identifying the ECU itself, see our guide on how to read ECU label numbers, and for more diagnostic write-ups browse the Fault Codes & Diagnostics category.