You might have encountered the terms OBD or OBDII, especially when exploring connected vehicles and devices like the Geotab GO. These are integral parts of your car’s internal computer system, with a history that’s quite interesting. This article offers a detailed overview of OBDII and traces its evolution.
See also:
History of GPS satellites and commercial GPS tracking
The Geotab GO saved my RV vacation
Understanding OBD: On-Board Diagnostics Explained
On-board diagnostics (OBD) is essentially the electronic system within your vehicle that performs self-diagnosis and reporting. It’s designed to give repair technicians access to your car’s subsystem information, which is crucial for monitoring performance and pinpointing repair needs.
Think of OBD as a universal language for vehicle diagnostics. It’s the standard protocol used in the majority of light-duty vehicles to pull out diagnostic data. This valuable information is generated by engine control units (ECUs), sometimes referred to as engine control modules. ECUs are essentially the brains or computers of your vehicle, constantly monitoring various systems.
Why is the OBD System So Vital?
OBD is not just for mechanics; it’s a cornerstone of modern telematics and fleet management. It empowers vehicle owners and fleet operators to effectively measure and manage vehicle health and driving behavior.
Thanks to OBD, fleets and individuals can achieve significant benefits:
- Track Wear Trends: Identify patterns in vehicle component wear, allowing for predictive maintenance and preventing unexpected breakdowns.
- Proactive Vehicle Diagnostics: Instantly diagnose potential vehicle issues before they escalate, shifting from reactive repairs to a proactive management approach.
- Driving Behavior Monitoring: Measure and analyze driving habits, including speed, idling time, and more, to improve safety and efficiency.
Locating Your OBDII Port: Where to Find It
In most standard passenger cars, the OBDII port is typically located beneath the dashboard on the driver’s side. You’ll usually find it in the area under the steering wheel column. Depending on the vehicle type, the port configuration can vary, featuring 16-pin, 6-pin, or 9-pin layouts. However, the 16-pin configuration is the most common for OBDII in passenger vehicles.
Diagram showing the typical location of the OBDII port inside a vehicle's cabin
If you’re planning to connect a Geotab GO device or any other OBDII device to your car, knowing the port’s location is the first step. For guidance on installing a Geotab GO device, you can refer to this helpful article: How to install a Geotab GO vehicle tracking device.
OBD vs. OBDII: Understanding the Key Differences
OBDII is essentially the evolution of the original OBD, representing the second generation of on-board diagnostic systems. The primary distinction lies in their integration and capabilities. OBD-I systems were often external, requiring connections to the car’s console, while OBDII is integrated directly into the vehicle’s internal systems. OBD-I was the standard until OBDII was developed and implemented in the early 1990s.
For a deeper dive into the importance and value of the OBD port in today’s connected world, this white paper provides valuable insights: Preserving privacy and security in the connected vehicle: The OBD port on the road ahead.
A Look into the History of OBDII
The journey of on-board diagnostics began in the 1960s, driven by the need for better vehicle emission control and diagnostics. Several key organizations played a pivotal role in shaping the standards we use 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 independently, developing their own proprietary systems. This meant diagnostic tools were not universal; each manufacturer, and sometimes even different models from the same manufacturer, had unique connector types, electronic interface requirements, and custom trouble codes.
Key Milestones in OBD History:
- 1968 — Volkswagen pioneers the first OBD computer system equipped with scanning capabilities.
- 1978 — Datsun introduces a basic OBD system, although with limited and non-standardized features.
- 1979 — The Society of Automotive Engineers (SAE) advocates for a standardized diagnostic connector and a uniform set of diagnostic test signals.
- 1980 — General Motors (GM) develops a proprietary interface and protocol that enables engine diagnostics through an RS-232 interface or, more simply, by triggering the Check Engine Light.
- 1988 — Standardization efforts gain momentum in the late 1980s, building upon the 1988 SAE recommendation for a standard connector and diagnostic procedures.
- 1991 — California mandates basic on-board diagnostics for all vehicles sold in the state, marking the era of OBD-I.
- 1994 — California sets a new standard, requiring all vehicles sold in the state from 1996 onwards to incorporate OBD as recommended by SAE – now known as OBDII. This mandate was largely motivated by the need for consistent emissions testing across all vehicles. OBDII brought with it a standardized set of diagnostic trouble codes (DTCs).
- 1996 — OBD-II becomes a mandatory requirement for all vehicles manufactured in the United States.
- 2001 — EOBD, the European counterpart of OBD, becomes mandatory for all gasoline vehicles within the European Union (EU).
- 2003 — EOBD is extended to become mandatory for all diesel vehicles in the EU.
- 2008 — A significant update in the US requires all vehicles from 2008 onwards to implement OBDII via a Controller Area Network, as specified by ISO 15765-4. This enhanced the communication speed and capabilities of OBDII systems.
What Kind of Data Can You Access Through OBDII?
The OBDII system provides access to a wealth of status information and Diagnostic Trouble Codes (DTCs) related to critical vehicle systems, primarily:
- Powertrain: Covering the engine and transmission systems.
- Emission Control Systems: Monitoring components crucial for reducing vehicle emissions.
In addition to these, OBDII also allows access to essential vehicle identification and operational data, including:
- Vehicle Identification Number (VIN): A unique identifier for your vehicle.
- Calibration Identification Number: Software and calibration information for the vehicle’s computer systems.
- Ignition Counter: Tracks the number of ignition cycles.
- Emissions Control System Counters: Monitors the performance and status of emission control components.
A mechanic or technician connecting a diagnostic tool to a vehicle's OBDII port to extract data.
When you take your car for servicing, mechanics use scanning tools to connect to the OBD port. This allows them to read trouble codes, quickly diagnose issues, and address malfunctions before they turn into major problems. This capability ensures efficient vehicle maintenance and repair.
Examples of OBDII Data Parameters
Mode 1 (Vehicle Information): This mode provides real-time data parameters.
- Pid 12 — Engine RPM (Revolutions Per Minute)
- Pid 13 — Vehicle Speed
Mode 3 (Trouble Codes: DTCs are categorized by system: P = Powertrain, C = Chassis, B = Body, U = Network): This mode reports stored diagnostic trouble codes.
- 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, you can consult this list of standard diagnostic trouble codes.
OBD and Telematics: Powering Connected Fleets
The OBDII port is fundamental to the functionality of telematics devices. It enables these devices to seamlessly gather and process critical vehicle data, such as engine RPM, vehicle speed, fault codes, and fuel consumption. Telematics devices use this information to calculate trip details (start and end times), detect driving behavior issues like over-revving and speeding, monitor idling time, and track fuel usage, among other metrics.
All this collected data is then transmitted to a software interface, providing fleet managers with real-time insights into vehicle usage and performance. This connectivity enhances fleet management efficiency, safety, and cost-effectiveness.
However, it’s important to note that with the wide array of OBD protocols in use, not all telematics solutions are universally compatible with every vehicle type. Geotab telematics addresses this challenge by employing sophisticated data normalization techniques. This allows Geotab devices to effectively translate vehicle diagnostic codes from a diverse range of makes and models, including electric vehicles.
See also: Data normalization and why it matters
The OBD-II port simplifies the integration of fleet tracking solutions into vehicles. For instance, Geotab devices are designed for quick and easy setup, often achievable in under five minutes.
In cases where a vehicle or truck lacks a standard OBDII port, adapters can be utilized to ensure compatibility. Regardless, the installation process remains straightforward, requiring no specialized tools or professional installation services.
WWH-OBD: The Next Generation of Diagnostics
WWH-OBD, which stands for World Wide Harmonized on-board diagnostics, represents the future of vehicle diagnostics. It’s an international standard developed under the United Nations’ Global Technical Regulations (GTR) mandate. WWH-OBD aims to standardize and enhance vehicle data monitoring, particularly in areas like emissions output and engine fault codes, across different regions and manufacturers.
Advantages of WWH-OBD: Enhanced Diagnostic Capabilities
Transitioning towards WWH-OBD offers several technical advantages, making it a significant step forward in vehicle diagnostics:
Expanded Data Type Access
Current OBDII Parameter IDs (PIDs) in Mode 1 are limited to one byte, restricting the number of unique data types to 255. WWH-OBD expands the potential for data access. The expansion of PIDs can also be applied to other OBD-II modes that are incorporated into WWH through Unified Diagnostic Services (UDS) modes. Adopting WWH standards opens the door to a greater volume of data and allows for future scalability and expansion of diagnostic parameters.
More Detailed Fault Data
Another key improvement with WWH-OBD is the enhanced detail in 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) in WWH-OBD extends the DTC to three bytes. The third byte specifies the “failure mode,” similar to the failure mode indicator (FMI) used in the J1939 protocol for heavy-duty vehicles.
For example, in OBDII, you might encounter several distinct 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 different failure modes differentiated by the third byte of the DTC. For instance, P0071 becomes P0070-1C, providing a more streamlined and detailed diagnostic approach.
WWH-OBD also provides additional fault information, 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 if the fault is pending, confirmed, or if the diagnostic test for that fault has been completed within the current driving cycle.
In essence, WWH-OBD builds upon the OBDII framework, offering richer diagnostic information and a more nuanced understanding of vehicle issues.
Geotab’s Commitment to WWH-OBD Support
Geotab is at the forefront of adopting advanced diagnostic standards and has already integrated the WWH protocol into its firmware. Geotab’s system intelligently detects the vehicle’s diagnostic capabilities, discerning whether OBDII or WWH-OBD (or sometimes both) are available.
Geotab continuously refines its firmware to maximize the diagnostic data available to its customers. Support for 3-byte DTC information is already implemented, and efforts are ongoing to incorporate even more detailed fault data. When new data parameters or fault information becomes accessible through OBDII or WWH-OBD, or when new vehicle protocols emerge, Geotab prioritizes rapid and accurate integration into its firmware. These firmware updates are then seamlessly delivered over-the-air to Geotab devices, ensuring users always benefit from the latest diagnostic advancements.
Expanding Beyond OBDII: The Future of Vehicle Diagnostics
While OBDII includes 10 standard modes for essential emission-related diagnostics, these have become insufficient for the increasing complexity of modern vehicles.
To address this, various UDS (Unified Diagnostic Services) modes have been developed since the introduction of OBDII to broaden the scope of available data. Vehicle manufacturers utilize proprietary PIDs (Parameter IDs) and implement them through additional UDS modes. Data not mandated by OBDII standards, such as odometer readings and seatbelt usage, has become accessible through UDS modes.
UDS encompasses over 20 additional modes beyond the 10 standard OBDII modes, significantly expanding diagnostic data availability. WWH-OBD seeks to integrate UDS modes with OBDII, enriching diagnostic capabilities while maintaining a standardized framework for vehicle diagnostics.
Conclusion: The Enduring Importance of the OBDII Port
In our increasingly interconnected world of IoT, the OBD port remains a vital component for ensuring vehicle health, safety, and sustainability. Despite the growing number and variety of connected vehicle devices, not all are created equal in terms of data reporting and tracking capabilities. Compatibility and security are also critical considerations.
Given the multitude of OBD protocols, it’s essential to choose telematics solutions that are designed to work with a wide range of vehicle types. Effective telematics solutions, like Geotab, are capable of interpreting and normalizing a comprehensive set of vehicle diagnostic codes, ensuring broad compatibility and reliable data.
To learn more about selecting the right GPS vehicle tracking device for your needs, read: Not All OBD Plug-In Fleet Management Devices Are Made Equal.
Furthermore, verifying the security of any third-party devices connected to the OBDII port is paramount. For best practices in telematics cybersecurity for fleet tracking, refer to these 15 security recommendations.
