You might have encountered terms like “OBD” or “OBD2” when exploring connected vehicles and devices like the Geotab GO. These features are integral to a car’s on-board computer system, with a development history that’s not widely known. This article delves into the history of OBD2 and provides a timeline of its evolution, focusing on when OBD2 officially started and its significance in modern vehicles.
Understanding OBD: The Basics of On-Board Diagnostics
On-Board Diagnostics (OBD) is essentially a vehicle’s self-diagnostic and reporting system, designed to assist repair technicians. An OBD system provides access to vital subsystem information, enabling performance monitoring and efficient analysis of repair needs.
OBD has become the standard protocol in the majority of light-duty vehicles for retrieving vehicle diagnostic data. This information is generated by Engine Control Units (ECUs), often referred to as the “brain” or computer of the vehicle.
The Importance of OBD in Modern Vehicles
OBD plays a crucial role in telematics and fleet management by enabling the measurement and management of vehicle health and driving behavior.
Thanks to OBD systems, fleets can achieve significant benefits, including:
- Tracking wear patterns to identify vehicle parts that are degrading faster than expected.
- Proactive diagnosis of vehicle problems, allowing for preventative maintenance rather than reactive repairs.
- Measurement of driving behavior metrics such as speed, idling time, and more, promoting safer and more efficient driving practices.
Locating the OBD2 Port in Your Vehicle
In most passenger vehicles, the OBD2 port is typically found beneath the dashboard on the driver’s side. Depending on the vehicle type, the port may have a 16-pin, 6-pin, or 9-pin configuration.
If you’re interested in connecting a device like a Geotab GO to your vehicle’s OBD port, further instructions can be found in resources like “How to install a Geotab GO vehicle tracking device.”
OBD vs. OBD2: What’s the Key Difference?
OBD2 is simply the second generation, an evolution of the original OBD (OBD I). The primary difference lies in integration and standardization. OBD I was often an external add-on, connected to the car’s console, while OBD2 is integrated directly into the vehicle’s system. OBD I was the standard until OBD2 was developed in the early 1990s.
For a deeper understanding of the value and implications 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 Historical Timeline of OBD2 Development
The journey of on-board diagnostics began in the 1960s, with several organizations playing pivotal roles in shaping the standards we know today. These include 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, vehicle manufacturers operated with proprietary systems. Diagnostic tools, connector types, electronic interface requirements, and problem reporting codes were unique to each manufacturer, and sometimes even varied between models from the same manufacturer.
Key Milestones in OBD History:
1968 — Volkswagen took the lead by introducing the first OBD computer system equipped with scanning capabilities.
1978 — Datsun followed suit with a basic OBD system, although it had limited and non-standardized features.
1979 — The Society of Automotive Engineers (SAE) made a significant recommendation for a standardized diagnostic connector and a set of diagnostic test signals, pushing for uniformity across the industry.
1980 — General Motors (GM) introduced a proprietary interface and protocol that could provide engine diagnostics through an RS-232 interface, or more simply, by flashing the Check Engine Light, marking a step towards user-friendly diagnostics.
1988 — Standardization efforts gained momentum, culminating in the late 1980s with the 1988 SAE recommendation for a standard connector and diagnostic procedures, paving the way for OBD standardization.
1991 — California became the first state to mandate basic on-board diagnostics for all vehicles, leading to the era of OBD I. This was a crucial step towards emission control and vehicle health monitoring.
1994 — California further mandated that all vehicles sold in the state from 1996 onwards must incorporate OBD as recommended by SAE — which became known as OBD2. This mandate was driven by the need for consistent and comprehensive emissions testing. OBD2 included standardized Diagnostic Trouble Codes (DTCs), detailed in resources like “standardized diagnostic trouble codes (DTCs).” This year, 1994, is pivotal as it set the stage for the widespread adoption of OBD2.
1996 — OBD-II became mandatory for all cars manufactured for sale in the United States. This marked the official start of OBD2 as a nationwide standard, significantly impacting vehicle diagnostics and repair.
2001 — EOBD, the European counterpart of OBD, became mandatory for all gasoline vehicles in the European Union (EU), extending the reach of standardized on-board diagnostics globally.
2003 — EOBD regulations were expanded to include all diesel vehicles in the EU, further solidifying the importance of standardized diagnostics for all types of vehicles.
2008 — A further refinement in the US mandated that starting in 2008, all vehicles must implement OBD2 through a Controller Area Network as specified by ISO 15765-4, enhancing the communication protocol and data transmission capabilities of OBD systems.
Data Accessibility via OBD2
OBD2 provides access to critical status information and Diagnostic Trouble Codes (DTCs) related to:
- Powertrain: Covering engine and transmission performance.
- Emission Control Systems: Monitoring components crucial for reducing vehicle emissions.
In addition, OBD2 systems allow access to key vehicle identification and operational data, such as:
- Vehicle Identification Number (VIN)
- Calibration Identification Number
- Ignition counter
- Emissions Control System counters
When a vehicle requires servicing, mechanics utilize scanning tools to connect to the OBD port, read trouble codes, and accurately diagnose issues. This capability enables quick vehicle inspections and precise repairs, addressing malfunctions before they escalate into major problems.
Examples of OBD2 Data
Mode 1 (Vehicle Information):
- Pid 12 — Engine RPM (Revolutions Per Minute)
- 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
For a more extensive list of diagnostic codes, resources like “list of standard diagnostic trouble codes” are readily available.
OBD and Telematics: A Powerful Combination
The OBD2 port is instrumental in enabling telematics applications. It allows telematics devices to seamlessly gather data such as engine revolutions, vehicle speed, fault codes, and fuel usage. This information is then processed to determine trip details, driving behavior (like over-revving or speeding), excessive idling, and fuel consumption. The data is subsequently uploaded to a software interface, providing fleet managers with comprehensive insights into vehicle usage and performance.
Geotab telematics solutions are designed to handle the complexities of various OBD protocols, translating diagnostic codes from different vehicle makes, models, and even electric vehicles, overcoming compatibility challenges. Learn more about this in “Data normalization and why it matters.”
Connecting a fleet tracking solution via the OBD-II port is a quick and straightforward process. For instance, Geotab devices can be “set up in under five minutes.”
For vehicles lacking a standard OBD2 port, adapters are available to ensure compatibility. In either case, installation is user-friendly and doesn’t require specialized tools or professional assistance.
WWH-OBD: The Future of Vehicle Diagnostics
WWH-OBD, or World Wide Harmonized On-Board Diagnostics, represents the next step in vehicle diagnostics standardization. It is an international standard under the United Nations’ Global Technical Regulations (GTR), aimed at harmonizing vehicle data monitoring, including emissions and engine fault codes, across different regions.
Advantages of WWH-OBD: Enhanced Diagnostic Capabilities
Moving towards WWH-OBD offers several technical advantages:
Expanded Data Type Access
Current OBD2 PIDs in Mode 1 are limited to one byte, restricting the unique data types to 255. WWH-OBD allows for the expansion of PIDs, potentially extending to other OBD-II modes via Unified Diagnostic Services (UDS) modes, offering more data and future scalability.
More Detailed Fault Data
WWH-OBD enhances fault data detail by expanding the Diagnostic Trouble Code (DTC) from two bytes in OBD2 to three bytes. The third byte indicates the “failure mode,” similar to the Failure Mode Indicator (FMI) in the J1939 protocol. This allows for more specific fault identification. For example, multiple OBD2 codes related to the Ambient Air Temperature Sensor can be consolidated into a single WWH-OBD code with different failure modes indicated, like P0070-1C, which specifies a particular failure type for the P0070 code.
WWH-OBD also provides additional fault information, such as severity, class (according to GTR specifications), and status (pending, confirmed, or test completion in the current driving cycle), offering a more comprehensive diagnostic picture.
In essence, WWH-OBD builds upon the OBD2 framework, delivering richer diagnostic insights.
Geotab’s Commitment to WWH-OBD and Beyond
Geotab has proactively integrated the WWH-OBD protocol into its firmware. Geotab’s sophisticated protocol detection system intelligently identifies whether a vehicle supports OBD2, WWH-OBD, or both.
Geotab continuously refines its firmware to enhance the data available to customers. Support for 3-byte DTC information and ongoing additions of fault data illustrate this commitment. Geotab prioritizes incorporating new data (PIDs, fault data) and protocols into its firmware, ensuring rapid over-the-cloud updates to devices, so customers always benefit from the latest advancements in vehicle diagnostics.
Beyond OBD2: The Evolution of Vehicle Data
While OBD2 standardized 10 modes for essential emission-related diagnostics, the increasing demand for more vehicle data has driven the development of additional UDS modes. Vehicle manufacturers utilize proprietary PIDs and implement them through these extra UDS modes to access data beyond OBD2 requirements, such as odometer readings and seatbelt usage.
UDS encompasses over 20 modes beyond the standard 10 in OBD2, offering a wealth of additional information. WWH-OBD bridges this gap by integrating UDS modes with OBD2, aiming to standardize and enrich diagnostic data availability while maintaining a unified process.
Conclusion: The Enduring Importance of OBD
In the expanding landscape of IoT, the OBD port remains a cornerstone for vehicle health, safety, and sustainability. Despite the growing variety of connected vehicle devices, OBD systems offer a standardized and crucial pathway to access vehicle diagnostics.
Given the multitude of OBD protocols, selecting telematics solutions that can effectively interpret and translate a broad range of vehicle diagnostic codes is essential. Robust telematics solutions are designed to address this complexity, ensuring comprehensive vehicle data interpretation.
To guide your choice in GPS vehicle tracking devices, refer to “Not All OBD Plug-In Fleet Management Devices Are Made Equal.”
Furthermore, ensuring the cybersecurity of any third-party device connected to the OBD2 port is paramount. For insights into telematics cybersecurity best practices, explore these “15 security recommendations.”
