You might have encountered the terms “OBD” and “OBDII” when exploring connected vehicles and devices like the Geotab GO. These are integral components of your car’s internal computer system, with a history that’s richer than many realize. This article provides a detailed overview of OBDII and traces its evolution.
Related Articles:
History of GPS satellites and commercial GPS tracking
The Geotab GO saved my RV vacation
Understanding On-Board Diagnostics (OBD)
On-board diagnostics (OBD) is essentially your vehicle’s self-assessment system. It’s an electronic system in automobiles that offers vehicle self-diagnosis and reporting capabilities, primarily designed for repair technicians. An OBD system grants technicians access to vital subsystem information, enabling them to monitor performance and pinpoint repair needs effectively.
OBD serves as the universal protocol for accessing vehicle diagnostic data in the majority of light-duty vehicles. This data is generated by engine control units (ECUs), sometimes referred to as engine control modules. Think of ECUs as the brain or central computer of your car.
The Significance of OBD in Modern Vehicles
OBD is a cornerstone of telematics and fleet management, playing a crucial role in assessing and managing vehicle health and driving behavior.
Leveraging OBD, fleet managers gain significant advantages:
- Trend Analysis: Track wear patterns in vehicle components to predict and manage maintenance schedules proactively.
- Proactive Diagnostics: Instantly identify potential vehicle issues before they escalate, shifting from reactive to proactive maintenance.
- Driving Behavior Insights: Measure and analyze driving habits, speed, idling time, and other key performance indicators.
Locating the OBDII Port in Your Vehicle
In most passenger cars, the OBDII port is typically situated on the underside of the dashboard on the driver’s side. Depending on the vehicle model, the port may feature a 16-pin, 6-pin, or 9-pin configuration.
If you’re interested in connecting a Geotab GO device to your vehicle’s OBD port, you can find step-by-step instructions in this guide: How to install a Geotab GO vehicle tracking device.
OBD vs. OBDII: Key Differences
OBDII is essentially the evolved second generation of OBD, or OBD I. The original OBD I was externally connected to a car’s console, while OBDII is seamlessly integrated within the vehicle itself. OBD I was the standard until OBDII emerged in the early 1990s.
For a deeper dive into the value of the OBD port, explore this white paper: Preserving privacy and security in the connected vehicle: The OBD port on the road ahead.
A Journey Through OBDII History
The concept of on-board diagnostics dates back to the 1960s. Several key organizations paved the way for its standardization, 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 and electronic interface requirements. They also employed custom codes to report vehicle problems.
Key Milestones in OBD Development:
1968 — Volkswagen pioneers the first OBD computer system equipped with scanning capabilities.
1978 — Datsun introduces a basic OBD system, albeit with limited and non-standardized functionalities.
1979 — The Society of Automotive Engineers (SAE) proposes a standardized diagnostic connector and a uniform set of diagnostic test signals.
1980 — GM develops a proprietary interface and protocol enabling engine diagnostics through an RS-232 interface or a simpler Check Engine Light flashing method.
1988 — The push for OBD standardization gains momentum in the late 1980s, following the 1988 SAE recommendation for a standard connector and diagnostic parameters.
1991 — California mandates basic on-board diagnostics for all vehicles, marking the era of OBD I.
1994 — California sets a new standard, requiring all vehicles sold in the state from 1996 onwards to incorporate SAE-recommended OBD, now known as OBDII. This initiative was driven by the need for comprehensive emissions testing. OBDII included standardized Diagnostic Trouble Codes (DTCs).
1996 — OBD-II becomes a mandatory feature for all cars manufactured in the United States.
2001 — EOBD (European version of OBD) becomes compulsory for all gasoline vehicles within the European Union (EU).
2003 — EOBD expands to include all diesel vehicles in the EU.
2008 — Starting in 2008, all vehicles in the US are required to implement OBDII via a Controller Area Network as defined by ISO 15765-4.
Data Accessibility via OBDII
OBDII offers access to status information and Diagnostic Trouble Codes (DTCs) for critical vehicle systems:
- Powertrain: Engine and transmission performance data.
- Emission Control Systems: Monitoring of components related to vehicle emissions.
Furthermore, OBD II provides access to essential vehicle identification and operational information:
- Vehicle Identification Number (VIN)
- Calibration Identification Number
- Ignition Counter
- Emissions Control System Counters
When your car requires servicing, mechanics can connect a scanning tool to the OBD port to read trouble codes and accurately diagnose issues. This capability allows for quicker vehicle inspections and efficient repairs, preventing minor malfunctions from becoming major problems.
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
For a more extensive list of codes, refer to this comprehensive list of standard diagnostic trouble codes.
OBD and Telematics Integration
The OBDII port is instrumental in enabling telematics devices to seamlessly gather data, including engine revolutions, vehicle speed, fault codes, and fuel consumption. Telematics devices utilize this information to determine trip details, instances of over-revving, speeding, excessive idling, and fuel efficiency. This data is then transmitted to a software interface, allowing fleet managers to effectively monitor vehicle usage and performance.
Given the variety of OBD protocols, not all telematics solutions are universally compatible. Geotab telematics addresses this challenge by effectively translating vehicle diagnostic codes across diverse makes, models, and even electric vehicles.
See also: Data normalization and why it matters
The OBD-II port facilitates a swift and straightforward connection for fleet tracking solutions like Geotab, which can be set up in under five minutes.
For vehicles lacking a standard OBDII port, adapters are available to ensure compatibility. Regardless, the installation process remains quick and user-friendly, requiring no specialized tools or professional installation services.
Exploring WWH-OBD
WWH-OBD, or World Wide Harmonized on-board diagnostics, is an international standard for vehicle diagnostics. It is mandated by the United Nations as part of the Global Technical Regulations (GTR), encompassing vehicle data monitoring such as emissions output and engine fault codes.
Advantages of Adopting WWH-OBD Standards
The transition to WWH-OBD offers several technical benefits:
Enhanced Data Type Accessibility
Current OBDII PIDs in Mode 1 are limited to one byte, restricting the number of unique data types to 255. Expanding PIDs, applicable to other OBD-II modes ported to WWH via UDS modes, will allow for a greater volume of data and future scalability.
More Granular Fault Data
WWH-OBD expands fault information. OBDII currently uses a two-byte Diagnostic Trouble Code (DTC). For example, P0070 indicates a general electrical failure in the Ambient Air Temperature Sensor “A”.
Unified Diagnostic Services (UDS) extends the DTC to three bytes, with the third byte indicating the failure “mode,” similar to the Failure Mode Indicator (FMI) in the J1939 protocol. For example, OBDII might list multiple fault codes for the ambient air temperature sensor:
- P0070 Ambient Air Temperature Sensor Circuit
- P0071 Ambient Air Temperature Sensor Range/Performance
- P0072 Ambient Air Temperature Sensor Circuit Low Input
- P0073 Ambient Air Temperature Sensor Circuit High Input
- P0074 Ambient Air Temperature Sensor Circuit Intermittent
WWH-OBD consolidates these into a single P0070 code, with five failure modes detailed in the third DTC byte. For example, P0071 becomes P0070-1C.
WWH-OBD also provides additional fault details like severity/class and status. Severity indicates the urgency of addressing the fault, while class categorizes the fault according to GTR specifications. Fault status indicates if it’s pending, confirmed, or if testing is complete in the current driving cycle.
In essence, WWH-OBD enhances the OBDII framework, providing richer diagnostic insights.
Geotab’s WWH-OBD Support
Geotab has already integrated the WWH-OBD protocol into our firmware. Our system employs a sophisticated protocol detection mechanism to identify whether OBD-II or WWH-OBD is available on a vehicle (sometimes both).
At Geotab, we are committed to continuous firmware improvement to enhance the value our customers receive. We have begun supporting 3-byte DTC information and are continually expanding fault data details. When new data becomes available through OBDII or WWH-OBD, or when new vehicle protocols emerge, Geotab prioritizes rapid and accurate firmware updates, delivered over-the-air to ensure our customers always benefit from the latest advancements.
Evolution Beyond OBDII
OBDII includes 10 standard modes to meet emission diagnostic requirements. However, these modes have proven insufficient over time.
Numerous UDS modes have been developed since OBDII’s inception to enrich available data. Vehicle manufacturers utilize proprietary Parameter IDs (PIDs) and implement them via supplementary UDS modes. Data not mandated by OBDII, such as odometer readings and seatbelt usage, became accessible through UDS modes.
UDS encompasses over 20 additional modes beyond OBDII’s standard 10, offering a broader data spectrum. WWH-OBD bridges this gap by integrating UDS modes with OBDII, enhancing diagnostic data while maintaining a standardized framework.
Conclusion: The Enduring Role of the OBD Port
In the expanding landscape of IoT, the OBD port remains vital for vehicle health, safety, and sustainability. While the array of connected vehicle devices grows, data reporting and tracking capabilities, compatibility, and security remain inconsistent.
Given the diversity of OBD protocols, universal compatibility among telematics solutions is not guaranteed. Effective telematics solutions, like Geotab, are designed to interpret and translate a wide range of vehicle diagnostic codes.
To learn more about selecting a GPS vehicle tracking device, read: Not All OBD Plug-In Fleet Management Devices Are Made Equal.
Furthermore, ensuring the security of third-party devices connected to the OBDII port is paramount. Explore cybersecurity best practices for fleet tracking telematics in these 15 security recommendations.
