Introduction to the OBD II Standard

On-board diagnostics (OBD) is a computer-based self-diagnostic, monitoring, and reporting system built into automobiles to monitor the performance of the various engine components and emission system components.

It is used to implement vehicle diagnostics communication for diagnosis and repair of vehicle sub-systems through communication with Electronic Control Units (ECU). ECUs monitor and control the sub-systems of a vehicle. Common ECUs include Engine Control Module (ECM), Transmission Control Module (TCM), Electronic Brake Control Module (EBCM), etc. Thus OBD helps to detect and control engine failures, performance issues and fight vehicle emission.

Emission Control Regulations and OBD Requirements

The US federal emission standards for engines and vehicles are established by the US Environmental Protection Agency (EPA). The EPA emission standards for regulating engine emissions and air quality in general, is based on the Clean Air Act (1970), which is most recently amended in 1990. California is the only state that has the authority to adopt its own emission regulations. Other states have the option to either implement the federal emission standards or adopt California requirements (CAA Section 177).

During the early 1980’s, manufacturers started using electronic monitoring systems to control engine functions, fuel feed, ignition systems and emission systems, diagnose problems and alert users. This is called Engine/Electronic Control Unit (ECU) or Module (ECM).

OBD is the language of ECU, and OBD regulations ensure compliance with Californian and federal emission standards. This is achieved by setting OBD requirements to diagnose and monitor the vehicle emission system components such as catalytic convertors and to alert the driver/operator upon detecting any problems.

From 1994 onwards, EPA regulations require presence of OBD systems in light duty vehicles (LDV) and light duty trucks (LDT). OBD-II, an enhanced capability OBD standard computer system is mandatory for vehicle models from 1996 onwards. Since 2005, OBD has become mandatory for heavy duty vehicles (HDV) also.

The Evolution of OBD

OBD systems provide access to the status of various vehicle sub systems. This information can be utilized by the vehicle owner, driver, repair technician or testing authority to test and evaluate the condition and performance of the vehicle. The feedback provided by early OBD systems (1980s) were simple illumination or malfunction indicator lights on the vehicle dashboard. It was not sufficient for identifying the nature of the problem.

OBD has evolved since that and now the latest standard named OBD-II (1994), the successor of OBD-I and OBD-1.5, uses a standard digital communications port to provide real-time vehicle data along with a standardized series of Diagnostic Trouble Codes (DTC). This allows the user to identify the nature of the problem and enables him to correct the malfunctions of the vehicle.

OBD-II not only controls engine functions, but also monitors other vehicle components like chassis, body, accessory devices like mirrors, wipers etc and also the diagnostic control network of the vehicle. It also follows the California Air Resources Board (CARB) guidelines for data storage and accessibility to be provided to the external scan tools. Thus OBD-II is a protocol for vehicle diagnostics communication.

The OBD-II Standard

The ISO 15031 standard specifies a protocol for communication between a vehicle (through the OBD port/connector) and en external diagnostic equipment for emissions related diagnostics. The OBD-II standard is a set of specifications and services based on the ISO 15031 standard and specify the type of OBD diagnostic connector, the electrical signaling protocols and the messaging format. It also specifies a list of vehicle parameters to be monitored and also information about how to encode the data associated with these parameters during transmission and storage.

From the OBD port fitted in the vehicle, and through the OBD diagnostic connector, we can access vehicle parameters like speed, engine data, emission data etc. The OBD-II standard defines DTCs (Diagnostic Trouble Codes) as well as other diagnostic information that is usually passed through a gateway to the OBD II port. This standard defines a protocol for communicating engine related information with a generic scan tool, and allows for reporting of information by the vehicle, as well as requests from the scan tool and responses from the vehicle with specific diagnostic information.

For this diagnostic communication, the physical medium or signaling protocol will be like the CAN (Controller Area Network) automotive protocol. The OBD-II standardization has simplified diagnosis of emission related vehicle sub-systems by the usage of emission-related codes and data through the CAN bus.

The OBD-II Port or Data Link Connector (DLC)

It is a multi-pin (commonly 16-pin) diagnostic connection port in vehicles to implement vehicle diagnostics communication using the OBD-II protocol. An external scanning device like emission tester can connect to the vehicle ECUs through the OBD-II port or DLC and can access real-time data streams and on-board diagnostics results. The OBD-II DLC is the main connector through which all sub systems are diagnosed, tuned and reprogrammed.

The OBD-II Diagnostic Connector

The 2 types of diagnostic connectors defined by the SAE J1962 specification are called Type A and Type B. Both of them are female, 16-pin (2 X 8) D-shaped connectors having a groove between the 2 rows of pins. Type A is used for vehicles with 12V supply voltage while Type B is used with 24V vehicles.

Diagnostic Trouble Codes (DTC)

DTC codes are used to identify an issue or error, from which unit of the vehicle the issue is coming from, which sub system is involved with the issue, etc. Manufacturers can implement their specific OBD-II custom data parameters that include real-time data requests and trouble codes.

These codes have the format: XXXXX

The first digit identifies the vehicle unit concerned with the error code.

Examples:

• Pxxxx – powertrain
• Bxxxx – body
• Cxxxx – Chassis
• Uxxxx – class 2 network

Second digit specifies whether the code is government required or manufacturer-unique.

Third digit indicates the vehicle subsystem:

Examples:

• xx3xx – ignition system
• xx4xx – emissions system
• xx7xx and xx8xx – transmission system

Fourth and fifth digits show the specific failure code.

Examples of some DTC Codes:

• P0112 Intake Air Temperature Circuit Low Input
• P0197 Engine Oil Temperature Sensor Low
• P0410 Secondary Air Injection System Malfunction
• P0710 Transmission Fluid Temperature Sensor Circuit Malfunction

Summary

Apart from vehicle on-board diagnostics and emission control, OBD-II connectors can be utilized by other tools to access OBD functions. These applications range from consumer appliances to highly sophisticated vehicle telematics services that perform fleet tracking, fuel efficiency monitoring, automated drive assistance etc. Manufacturers can monitor DTC codes to identify vehicle malfunctioning and details of the issue and can take remedial measures. Thus OBD-II specification is of high benefit not only to federal emission control regulations, but also to growth and development of automotive industry.