Other meanings of On-board diagnostics
Automotive Technology
On-board diagnostics (OBD) is a vehicle self-diagnostic system that monitors engine and emissions performance and reports faults through standardized diagnostic interfaces. Modern OBD systems, particularly those compliant with the OBD-II standard, allow technicians and drivers to retrieve standardized trouble codes that identify malfunctions in the powertrain, emissions controls, and other monitored systems.
On-board diagnostics emerged from the need to monitor emissions-control components after the US Clean Air Act amendments of 1970. California's Air Resources Board (CARB) mandated the first generation, OBD-I, in 1988, requiring basic monitoring of the fuel system and oxygen sensors.1 OBD-I used proprietary connectors and protocols that varied by manufacturer, making diagnosis difficult outside dealerships.
OBD-II, introduced in the mid-1990s, standardized the diagnostic connector, the communication protocols, and the format of diagnostic trouble codes (DTCs). The Society of Automotive Engineers (SAE) developed the J1962 connector specification and the J2012 DTC format, while the International Organization for Standardization (ISO) defined the underlying communication protocols such as ISO 9141 and ISO 14230.2 The US Environmental Protection Agency (EPA) required all 1996 and later light-duty vehicles sold in the United States to comply with OBD-II.1
OBD-II systems continuously monitor the powertrain, emissions controls, and related components while the vehicle operates. The engine control unit (ECU) runs self-tests, called monitors, that compare sensor readings and actuator responses against expected values. When a fault is detected, the ECU stores a diagnostic trouble code and illuminates the malfunction indicator lamp (MIL), commonly called the check engine light.
DTCs follow a standardized five-character format: a letter indicating the system (P for powertrain, B for body, C for chassis, U for network), followed by four digits that specify the subsystem and the particular fault. Technicians retrieve these codes through the SAE J1962 connector, typically located under the dashboard on the driver's side, using a scan tool or a smartphone paired with a Bluetooth adapter.3 The system also provides live sensor data, freeze-frame data captured at the moment of a fault, and readiness status for emissions testing.
OBD-II serves as the backbone of vehicle emissions inspection programs in many jurisdictions. During an inspection, a tester connects to the vehicle's diagnostic port and verifies that the MIL is off, that no emissions-related DTCs are stored, and that the readiness monitors have completed their self-tests. This approach replaced tailpipe testing in many regions because it is faster and detects faults that might not appear during a brief idle test.
Beyond inspection, OBD data has been used to identify widespread emissions cheating. In 2015, the US EPA cited Volkswagen for installing software that detected when a vehicle was undergoing emissions testing and altered engine calibration to reduce NOx output, while allowing higher emissions during normal driving.4 The scandal prompted stricter scrutiny of OBD data and led to regulatory changes in both the US and the European Union.
OBD-II supports five distinct communication protocols, and a single vehicle may use more than one. The protocols include SAE J1850 PWM, SAE J1850 VPW, ISO 9141-2, ISO 14230-4 (KWP2000), and ISO 15765-4 (CAN).2 The Controller Area Network (CAN) protocol became mandatory for all 2008 model year vehicles in the US, simplifying the hardware required for scan tools.
Heavy-duty trucks and buses use a separate standard, SAE J1939, which is based on CAN but uses different message formats and connector types than light-duty OBD-II.5 The European Union adopted EOBD, a variant of OBD-II, for gasoline vehicles in 2000 and for diesel vehicles in 2003. Some manufacturers have also implemented enhanced manufacturer-specific codes beyond the standardized set, which require proprietary scan tools to interpret fully.3
OBD-II has been mandatory on all US light-duty vehicles since 1996; the CAN protocol became the sole permitted communication standard for 2008 and later model years.
Help improve the encyclopedia. Reports go straight to the site manager.