2025-04-28

# Glossary of ODB II terminology

AI response

OBD-II stands for On-Board Diagnostics II, a system that monitors a vehicle's engine and emissions systems. It uses a standardized set of alphanumeric codes, known as Diagnostic Trouble Codes (DTCs) or fault codes, to communicate detected issues to the driver. These codes are categorized by system (powertrain, body, chassis, network), and a P0 code will always illuminate the check engine light. 

## Key Terms in OBD-II:

* OBD-II: On-Board Diagnostics II, a standard for monitoring vehicle systems. 
* DTC (Diagnostic Trouble Code): A standardized alphanumeric code indicating a fault in a vehicle system, often used to describe a problem. 
* P Code: Powertrain system code (engine and transmission). 
* B Code: Body system code. 
* C Code: Chassis system code. 
* U Code: Network and wiring system code. 
* Check Engine Light (CEL): A dashboard indicator that illuminates when a fault code is detected by the OBD-II system. 
* Scan Tool: A device used to read and interpret OBD-II codes. 
* Freeze Frame: Data captured at the time a fault code is set, including sensor readings. 
* Live Data: Real-time data from various vehicle sensors, such as engine speed, fuel trim, and coolant temperature. 
* Mode: A command within the OBD-II protocol, like requesting live data or freeze frames. 

## Understanding DTCs:

DTCs are typically 5 characters long, with the first character indicating the system (P, B, C, or U).
The next two characters specify the general area of the system, and the last two characters are a unique code for a specific issue.
For example, P0420 indicates a Catalyst System Efficiency Below Threshold on Bank 1. 

### How OBD-II Works:

The vehicle's engine control unit (ECU) monitors various systems and sensors. 
If a problem is detected, the ECU will store a DTC and may also illuminate the CEL. 
A scan tool can be used to access the stored DTCs and freeze frames. 
The scan tool can also be used to request live data from the vehicle's sensors. 
This information can be used to diagnose and repair the problem. 


J1939 is the “language” that ECUs use to communicate with each other, and the CAN bus is the “communication highway” that J1939 uses to transmit its message.

SAE J1939 is a CAN-based communication protocol primarily used in heavy-duty vehicles, trucks, and other commercial vehicles. It provides a standardized way for Electronic Control Units (ECUs) to communicate with each other over a network, enabling data sharing, diagnostics, and control functions











# References

* [kvaser.com](https://kvaser.com/about-can/can-standards/introduction-to-obd-ii/automotive-obd-ii-dictionary/) [and, dated 2013](https://www.totalcardiagnostics.com/support/Knowledgebase/Article/View/24/6/obd-ii-acronyms-and-jargon)
* [DTCs - J1939 protocol common DTCs](https://whiparound.com/dtc-codes/)
* [J1939, open standard for networking and communication in the commercial vehicle sector.](https://www.vector.com/at/en/know-how/protocols/sae-j1939/#)
* [List of P codes](https://club.autodoc.co.uk/obd-codes/all) [and here](https://rodsshop.org/full-list-of-odb-codes/)
* [ODB 2 connector pinout](https://www.flexihub.com/oobd2-pinout/)


Copyright (C)  2025 Dave Pawson
    Permission is granted to copy, distribute and/or modify this document
    under the terms of the GNU Free Documentation License, Version 1.3
    or any later version published by the Free Software Foundation;
    with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
    A copy of the license is included in the section entitled "GNU
    Free Documentation License".