OBD-II

OBD-II
Name	OBD-II
Caption	Generic 16-pin diagnostic connector and scan tool
Invented	1996 (US mandate)
Inventor	Society of Automotive Engineers (SAE), California Air Resources Board (CARB), Environmental Protection Agency (EPA)
Used in	Light vehicles, trucks, motorcycles
Standards	SAE J1962, SAE J1979, ISO 15765-4, ISO 9141-2

OBD-II OBD-II is a standardized automotive onboard diagnostics specification for monitoring vehicle emissions control systems and reporting powertrain faults. It mandates a common physical connector, standardized diagnostic trouble codes, and protocols for data parameter access, enabling technicians and owners to read fault conditions and live sensor data. The system links vehicle electronics from manufacturers such as Ford Motor Company, General Motors, Toyota, Honda Motor Company, and Volkswagen Group to regulatory frameworks established by bodies like the California Air Resources Board and the United States Environmental Protection Agency.

Overview

OBD-II provides a uniform interface to the vehicle's engine control unit and related modules using a 16-pin connector and standardized messages defined by organizations including the Society of Automotive Engineers and the International Organization for Standardization. Major automobile manufacturers such as BMW, Mercedes-Benz, Hyundai, Nissan Motor Company, and Fiat Chrysler Automobiles implement OBD-II-compatible systems to comply with mandates from regulatory agencies such as the European Commission and the United States Congress. The system supports diagnostic trouble codes, parameter IDs, and emission-related monitors to assist repair technicians, aftermarket toolmakers like Bosch, Snap-on, Autel, and software authors.

History and Development

Early onboard diagnostics evolved in response to emission scandals and regulatory efforts led by entities including the California Air Resources Board and the United States Environmental Protection Agency. Predecessors such as manufacturer-specific systems from Delphi Automotive and proprietary protocols used by Continental AG gave way to a standardized OBD-II requirement in the mid-1990s following rulemaking by regulators and technical committees from the Society of Automotive Engineers. Automakers including Chrysler, General Motors, and Ford Motor Company coordinated with suppliers like Valeo and Denso Corporation to integrate electronic control units capable of storing standardized fault codes and real-time data parameters.

Standards and Protocols

OBD-II encompasses several standards and protocols. The physical connector specification is SAE J1962, while message content for diagnostic queries is specified in SAE J1979. Communications over Controller Area Network are defined by ISO 15765-4 (CAN), with alternatives such as ISO 9141-2 and SAE J1850 PWM/VPW used historically by manufacturers like Chrysler and General Motors. European and international layers interact with standards from the International Organization for Standardization and regional regulations from the European Union. Automotive cybersecurity and data link management are increasingly considered within standards bodies such as SAE International and consortia like the Automotive Open System Architecture.

Diagnostic Trouble Codes and Data Parameters

Diagnostic trouble codes (DTCs) are five-character standardized identifiers (a letter plus four digits) categorized by systems and subsystems; many stem from conventions adopted by organizations like the Society of Automotive Engineers. Parameter IDs (PIDs) defined in SAE J1979 expose live sensor data such as engine RPM, vehicle speed, oxygen sensor voltages, and fuel trim. Repair databases maintained by institutions like Mitchell International and educational bodies such as The Automotive Service Association use DTC mappings to guide troubleshooting. Manufacturers sometimes extend the standard with proprietary codes and manufacturer-specific PIDs used by Ferrari, Porsche AG, and Tesla, Inc..

Connector and Pinout

The standardized 16-pin diagnostic connector, specified by SAE J1962, is typically located under the dashboard and follows a defined pinout. Pins provide power, ground, and communication lines for protocols like CAN High/Low, K-Line (ISO 9141-2), and J1850 signal lines. Tool vendors such as Snap-on and Bosch produce cable adapters and breakout boxes compatible with the pinout. Vehicle service manuals from manufacturers like Subaru Corporation and Mazda Motor Corporation document connector locations and pin assignments.

Readiness Monitors and Emissions Testing

Readiness monitors are self-tests for emission control components mandated by regulators including the California Air Resources Board and the United States Environmental Protection Agency to ensure systems such as catalytic converters, evaporative emission controls, and oxygen sensors are functioning. Inspection programs administered by state agencies and municipalities rely on OBD-II readiness states and DTC absence rather than tailpipe testing in many jurisdictions influenced by policies from the European Commission and legal frameworks from United States Congress legislation. Vehicle history services and inspection stations from networks like Monarch Vehicle Services and regional DMV offices reference readiness results during compliance checks.

Tools, Scanners, and Software

Aftermarket and professional scan tools range from simple code readers by companies like Actron to advanced diagnostic stations from Snap-on and Bosch. Open-source and commercial software such as projects endorsed by Automotive Aftermarket Suppliers Association members interface via ELM327-based adapters and Bluetooth/Wi-Fi dongles. Fleet management platforms from vendors like Verizon Connect and telematics providers such as Geotab leverage OBD-II data streams for maintenance scheduling, driver scoring, and asset tracking.

Security and Privacy Concerns

As vehicles integrate telematics and connected services from companies including AT&T, Verizon Communications, Apple Inc., and Google LLC, OBD-II access raises security and privacy issues. Researchers at institutions such as Carnegie Mellon University and University of California, San Diego have demonstrated attack vectors exploiting diagnostic interfaces to influence vehicle systems. Industry responses involve secure gateways, authentication measures championed by organizations like SAE International and consortia including the AUTOSAR partnership, and regulatory scrutiny from agencies like the National Highway Traffic Safety Administration to protect vehicle data and occupant safety.

Category:Automotive diagnostics