OBD-II Fault Codes Explained: What P, B, C and U Codes Mean

Introduction

When a check-engine light appears, an OBD-II scan can reveal a code such as P0300, P0420 or U0100. These codes are not a complete diagnosis, but they give you a useful starting point. The first letter identifies the vehicle system involved, while the numbers provide more detail about the fault.

What do the four OBD-II code letters mean?

P codes: Powertrain

P codes relate to the powertrain, including the engine, transmission, fuel system and emissions controls. Common examples include P0300 for random or multiple-cylinder misfires, P0420 for catalyst efficiency below the expected threshold, and P0171 for a system running too lean on one bank.

B codes: Body

B codes cover body systems such as airbags, seat-belt systems, power windows, central locking, climate control and other interior electronics. These faults may not turn on the check-engine light, so a basic engine-only reader may not find them.

C codes: Chassis

C codes relate to chassis systems, including ABS, steering, suspension and tyre-pressure monitoring. A C code may point to a wheel-speed sensor, wiring issue or communication problem, but the exact meaning depends on the vehicle manufacturer and system.

U codes: Network and communication

U codes indicate that control modules are having trouble communicating over the vehicle network. For example, U0100 commonly refers to lost communication with the engine control module. Low battery voltage, damaged wiring, poor connections or a failed module can all cause communication faults.

Generic and manufacturer-specific codes

The second character helps show whether a code is generic or manufacturer-specific. Codes beginning with P0, B0, C0 or U0 generally follow an industry-wide definition. Codes using a different second digit may require manufacturer-specific information and a scan tool with broader vehicle coverage.

A simple OBD-II reader may access generic powertrain codes, while a full-system diagnostic scanner can often communicate with ABS, airbag, transmission, body and other modules. Tools such as the LAUNCH X431 PRO3 V+, LAUNCH X431 PROS Elite and Thinkcar Expert 191 are designed for deeper, multi-system diagnosis.

How to read an OBD-II code properly

1. Record the exact code. Write down every stored and pending code before clearing anything.
2. Check the description and vehicle context. The same code can have different likely causes depending on the make, model, engine and mileage.
3. Review live data. Look at relevant readings such as engine temperature, fuel trims, oxygen-sensor data, battery voltage and engine speed.
4. Check freeze-frame information. Freeze-frame data shows the conditions present when the code was stored, which can help with intermittent faults.
5. Inspect simple causes first. Check connectors, wiring, fuses, fluid levels, vacuum hoses and battery condition before replacing expensive parts.

Should you clear the code?

Clearing a code only removes the stored warning from the vehicle memory. It does not repair the cause. If the fault remains, the code will return, and clearing it can also erase useful freeze-frame information.

After a repair, clear the code and complete the vehicle's required drive cycle. Then rescan the vehicle and check whether the fault has returned and whether the emissions monitors have completed. If the vehicle is being prepared for a WOF, remember that recently cleared codes may leave monitors incomplete.

When do you need a professional scan tool?

A basic reader can be useful for checking a straightforward engine fault. A full-system tool is the better choice when the warning involves ABS, airbags, transmission, TPMS or communication faults, or when you need live data, special functions or bi-directional tests.

For DIY owners, a wireless tool such as the XTOOL Anyscan A30X can make multi-vehicle checks more convenient. For workshops and trade users, a tool such as the XTOOL XT70W or a LAUNCH X431 platform can provide wider system access and advanced diagnostic functions.

Final takeaway

The letter in an OBD-II code is your first clue: P means powertrain, B means body, C means chassis and U means network communication. Use the code as a starting point, confirm it with live data and vehicle-specific information, and diagnose the underlying cause before replacing parts or clearing the warning.