You might have encountered the terms “OBD” or “OBDII” when exploring connected vehicles and devices like the Geotab GO. These are integral parts of a car’s internal computer system, with a history that’s more intricate than many realize. This article provides a comprehensive overview of OBDII and a timeline of its evolution, answering the key question: what year did OBD2 come out?
See also:
History of GPS satellites and commercial GPS tracking
The Geotab GO saved my RV vacation
Understanding OBD: On-Board Diagnostics
On-board diagnostics (OBD) is essentially a vehicle’s self-diagnostic and reporting system designed for automotive technicians. It empowers technicians to access crucial subsystem information, allowing for performance monitoring and effective repair analysis.
OBD has become the standard protocol across the majority of light-duty vehicles for accessing vehicle diagnostic data. This information originates from engine control units (ECUs), often called engine control modules, which act as the “brain” or computer of the vehicle.
The Significance of OBD in Modern Vehicles
OBD’s importance is amplified within telematics and fleet management, as it enables the measurement and management of vehicle health and driving behavior.
Thanks to OBD, fleet managers gain valuable capabilities:
- Trend Tracking: Monitor wear patterns to identify vehicle parts that degrade prematurely.
- Proactive Diagnostics: Instantly pinpoint vehicle issues before major failures occur, shifting from reactive to proactive maintenance.
- Driving Behavior Analysis: Measure and analyze driving habits, speed, idling times, and numerous other parameters.
Locating the OBDII Port in Your Vehicle
In most passenger vehicles, the OBDII port is typically situated beneath the dashboard on the driver’s side. Depending on the vehicle type, the port may feature a 16-pin, 6-pin, or 9-pin configuration.
For those interested in connecting a Geotab GO device to their OBD port, detailed instructions are available in “How to install a Geotab GO vehicle tracking device.”
OBD vs. OBDII: Key Differences
OBDII is simply the second generation, an evolution of the original OBD or OBD I. A primary distinction lies in their connection methods. OBD I was initially connected externally to the car’s console, while OBDII is integrated directly into the vehicle itself. OBD was the standard until OBDII’s development in the early 1990s.
For a deeper dive into the value and security aspects of the OBD port, the white paper “Preserving privacy and security in the connected vehicle: The OBD port on the road ahead” offers valuable insights.
The Development Timeline: History of OBDII and its Emergence
The history of on-board diagnostics dates back to the 1960s. Several key organizations played pivotal roles in establishing the standard, including the California Air Resources Board (CARB), the Society of Automotive Engineers (SAE), the International Organization for Standardization (ISO), and the Environmental Protection Agency (EPA).
Before standardization efforts, vehicle manufacturers developed proprietary systems. Diagnostic tools from each manufacturer, and sometimes even across different models from the same manufacturer, had unique connector types, electronic interface requirements, and custom codes for reporting issues.
Key Milestones in OBD History:
1968: Volkswagen pioneers the first OBD computer system equipped with scanning capability.
1978: Datsun introduces a basic OBD system, though with limited and non-standardized functionalities.
1979: The Society of Automotive Engineers (SAE) proposes a standardized diagnostic connector and a set of diagnostic test signals, marking a step towards uniformity.
1980: General Motors (GM) rolls out a proprietary interface and protocol capable of delivering engine diagnostics via an RS-232 interface, or more simply, by activating the Check Engine Light.
1988: Standardization of on-board diagnostics gains momentum in the late 1980s, following the 1988 SAE recommendation advocating for a standard connector and diagnostic procedures.
1991: California becomes the first state to mandate some form of basic on-board diagnostics for all vehicles, known as OBD I.
1994: California takes a decisive step by mandating OBD as recommended by SAE for all vehicles sold in the state starting in 1996 – this is when OBDII was officially mandated in California. This mandate was largely driven by the need for consistent emissions testing across all vehicles. OBDII incorporated a series of standardized diagnostic trouble codes (DTCs).
1996: OBD-II becomes mandatory for all cars manufactured and sold in the United States. This is the pivotal year OBD2 came out as a nationwide standard in the US automotive industry.
2001: EOBD (European version of OBD) becomes mandatory for all gasoline vehicles within the European Union (EU).
2003: EOBD expands to become mandatory for all diesel vehicles in the EU.
2008: Starting in 2008, all vehicles in the US are required to implement OBDII through a Controller Area Network as specified by ISO 15765-4, further standardizing the communication protocol.
Data Accessibility via OBDII
OBDII provides access to crucial status information and Diagnostic Trouble Codes (DTCs) for:
- Powertrain: Encompassing engine and transmission systems.
- Emission Control Systems: Monitoring components related to vehicle emissions.
Furthermore, OBD II allows access to essential vehicle identification information:
- Vehicle Identification Number (VIN)
- Calibration Identification Number
- Ignition counter
- Emissions Control System counters
When a vehicle requires servicing, mechanics can connect a scanning tool to the OBD port to read trouble codes and accurately diagnose issues. This capability allows for precise malfunction identification, rapid vehicle inspection, and timely repairs before minor issues escalate.
Examples of OBDII Data Modes and Trouble Codes:
Mode 1 (Vehicle Information):
- Pid 12 — Engine RPM
- Pid 13 — Vehicle Speed
Mode 3 (Trouble Codes: P = Powertrain, C = Chassis, B = Body, U = Network):
- P0201 — Injector circuit malfunction – Cylinder 1
- P0217 — Engine over temperature condition
- P0219 — Engine overspeed condition
- C0128 — Low brake fluid circuit
- C0710 — Steering position malfunction
- B1671 — Battery Module Voltage Out Of Range
- U2021 — Invalid/ fault data received
A comprehensive list of standard diagnostic trouble codes is available for more detailed information.
OBD and Telematics Integration
The OBDII port is fundamental to the functionality of telematics devices. It enables these devices to seamlessly process vital vehicle information such as engine revolutions, vehicle speed, fault codes, and fuel consumption. Telematics devices utilize this data to determine trip details, instances of over-revving, speeding, excessive idling, fuel efficiency, and more. This wealth of information is then transmitted to a software interface, empowering fleet managers to effectively monitor vehicle usage and performance.
Considering the diversity of OBD protocols, it’s important to note that not all telematics solutions are universally compatible with all vehicle types. Geotab telematics overcomes this challenge through advanced data normalization, translating vehicle diagnostic codes across various makes, models, and even electric vehicles.
See also: Data normalization and why it matters
The OBD-II port facilitates quick and straightforward connection of fleet tracking solutions like Geotab, often achievable in under five minutes.
For vehicles lacking a standard OBDII port, adapters are readily available to ensure compatibility. Regardless of the connection method, the installation process remains user-friendly and typically does not require specialized tools or professional assistance.
WWH-OBD: Expanding Diagnostic Capabilities
WWH-OBD, or World Wide Harmonized on-board diagnostics, represents an international standard for vehicle diagnostics. Implemented by the United Nations as part of the Global Technical Regulations (GTR) mandate, WWH-OBD enhances vehicle data monitoring, encompassing emissions output and detailed engine fault codes.
Advantages of WWH-OBD
The shift towards WWH-OBD offers several technical advantages:
Enhanced Data Type Access
Current OBDII PIDs within Mode 1 are limited to one byte, restricting the availability to 255 unique data types. WWH-OBD allows for the expansion of PIDs, potentially extending to other OBD-II modes through UDS modes. This adaptation unlocks access to a broader range of data and allows for future scalability.
More Granular Fault Data
WWH-OBD significantly improves the detail within fault data. OBDII currently uses a two-byte diagnostic trouble code (DTC). In contrast, Unified Diagnostic Services (UDS) in WWH-OBD expands DTCs to three bytes, with the third byte indicating the specific failure “mode.” This enhancement provides more precise fault information. For example, multiple OBDII codes related to the Ambient Air Temperature Sensor Circuit can be consolidated into a single WWH-OBD code with distinct failure modes.
WWH-OBD also provides additional fault context, including severity/class and status. Severity indicates the urgency of addressing the fault, while the class categorizes the fault according to GTR specifications. The status indicates whether the fault is pending, confirmed, or if testing is complete within the current driving cycle.
In essence, WWH-OBD builds upon the OBD II framework to deliver richer and more detailed diagnostic information.
Geotab’s WWH-OBD Support
Geotab has proactively integrated the WWH protocol into its firmware. Utilizing a sophisticated protocol detection system, Geotab devices intelligently identify whether OBD-II or WWH-OBD is available on a vehicle, and in some cases, support both.
Geotab continuously refines its firmware to maximize the data insights provided to customers. Support for 3-byte DTC information is already implemented, and ongoing efforts focus on enriching fault data. Geotab prioritizes rapid integration of new data, whether from OBDII or WWH-OBD, and promptly deploys firmware updates over the cloud, ensuring customers consistently benefit from the latest advancements.
The Evolution Beyond OBDII
The initial 10 standard modes within OBDII, designed for emission standard diagnostics, have become insufficient for modern vehicle data needs.
Over time, various UDS modes have been developed to expand data availability. Vehicle manufacturers utilize proprietary PIDs and implement them through supplementary UDS modes to access data beyond OBDII requirements, such as odometer readings and seatbelt usage.
UDS encompasses over 20 additional modes beyond the standard 10 OBDII modes, significantly increasing data availability. WWH-OBD bridges this gap by integrating UDS modes with OBDII, enhancing diagnostic data while maintaining a standardized framework for broader compatibility and understanding.
Conclusion: The Enduring Importance of OBD
In the expanding landscape of IoT, the OBD port retains its critical role in vehicle health, safety, and sustainability. While the proliferation of connected vehicle devices grows, data reporting, tracking capabilities, compatibility, and security can vary considerably.
Given the multitude of OBD protocols, comprehensive telematics solutions are essential to effectively interpret and translate diverse vehicle diagnostic codes. Robust solutions should accommodate a wide range of vehicle types and diagnostic languages.
To guide your selection of a GPS vehicle tracking device, refer to “Not All OBD Plug-In Fleet Management Devices Are Made Equal.”
Furthermore, prioritizing the cybersecurity of OBDII-connected third-party devices is paramount. Best practices for telematics cybersecurity in fleet tracking are outlined in these “15 security recommendations.”
