You might have come across terms like “OBD” or “OBDII” when exploring connected vehicles and devices like Geotab GO. These functionalities are integral parts of your car’s onboard computer system, and they have a history that’s more interesting than you might think. This article provides an in-depth overview of OBD2 and a timeline of its evolution, tailored for the English-speaking audience.
Decoding OBD: On-Board Diagnostics Explained
On-Board Diagnostics (OBD) refers to the automotive electronic system that offers vehicle self-diagnosis and reporting capabilities to repair technicians. Essentially, OBD allows mechanics to tap into subsystem information to monitor performance and pinpoint repair needs efficiently.
OBD is the standardized protocol employed in most light-duty vehicles to retrieve diagnostic information. This crucial data is generated by the Engine Control Units (ECUs), often called engine control modules or vehicle “brains.” These ECUs manage and monitor various aspects of your vehicle’s operation.
Why OBD2 Matters: The Benefits Unveiled
OBD is a cornerstone of modern telematics and fleet management, providing essential data for assessing vehicle health and driving behavior. Its importance stems from the actionable insights it provides.
Thanks to OBD, fleets and individual car owners can:
- Track Wear Trends: Identify patterns in component wear and tear to understand which parts degrade faster, facilitating predictive maintenance.
- Proactive Diagnostics: Instantly diagnose vehicle issues before they escalate into major problems, enabling a proactive maintenance approach.
- Monitor Driving Behavior: Measure driving habits, including speed, idling time, and more, to promote safer and more efficient driving.
Locating the OBD2 Port: Your Access Point
In a typical passenger vehicle, the OBD2 port is conveniently located 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. The 16-pin connector is the most common standard for OBD2.
OBD vs. OBD2: Understanding the Evolution
Simply put, OBD2 is the second generation of OBD, or OBD I. The original OBD I systems were often external add-ons, while OBD2 is seamlessly integrated into the vehicle’s architecture. OBD I was utilized until OBD2 was developed and mandated in the early to mid-1990s.
The Journey of OBD2: A Historical Perspective
The history of on-board diagnostics dates back to the 1960s. Several organizations played pivotal roles in establishing the standards we know today, 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).
It’s crucial to remember that before standardization, vehicle manufacturers developed proprietary systems. Diagnostic tools for each manufacturer, and sometimes even different models from the same manufacturer, had unique connector types, electronic interface requirements, and custom trouble codes. This lack of uniformity made vehicle diagnostics complex and inefficient.
Key Milestones in OBD History: A Timeline
1968 — Volkswagen pioneers the first computer-based OBD system with scanning capabilities.
1978 — Datsun introduces a basic OBD system with limited, non-standardized capabilities.
1979 — The Society of Automotive Engineers (SAE) recommends a standardized diagnostic connector and a uniform set of diagnostic test signals.
1980 — General Motors (GM) develops a proprietary interface and protocol capable of providing engine diagnostics through an RS-232 interface or, more simply, by flashing the check engine light.
1988 — Standardization of on-board diagnostics gains momentum following the 1988 SAE recommendation, advocating for a standard connector and diagnostic protocols.
1991 — The state of California mandates that all vehicles have some form of basic on-board diagnostics, known as OBD I.
1994 — California mandates OBD compliance for all vehicles sold in the state from 1996 onwards, based on SAE recommendations, now termed OBDII. This was to facilitate widespread emissions testing. OBDII included a set of standardized Diagnostic Trouble Codes (DTCs).
1996 — OBD-II becomes mandatory for all cars manufactured in the United States. This marked a significant step towards standardized vehicle diagnostics nationwide.
2001 — EOBD (European version of OBD) becomes mandatory for all gasoline vehicles in the European Union, extending standardized diagnostics across Europe.
2003 — EOBD is extended to become mandatory for all diesel vehicles in the EU, further solidifying its role in European vehicle regulations.
2008 — Starting in 2008, all vehicles in the United States are required to implement OBDII via a Controller Area Network (CAN), as specified in ISO standard 15765-4, enhancing data communication speeds and reliability.
OBD2 Data Access: What Information Can You Retrieve?
OBD2 provides access to both status information and Diagnostic Trouble Codes (DTCs) for critical vehicle systems:
- Powertrain: Engine and transmission performance and health.
- Emissions Control Systems: Monitoring the systems designed to reduce vehicle emissions.
Furthermore, vital vehicle information accessible through OBD2 includes:
- Vehicle Identification Number (VIN): Unique identifier of the vehicle.
- Calibration Identification Number: Software version identification for the ECU.
- Ignition Counter: Tracks the number of engine start cycles.
- Emissions Control System Counters: Monitors the performance and usage of emissions-related components.
When you take your car for servicing, a mechanic connects a scan tool to the OBD port to read fault codes and identify problems. This capability allows mechanics to accurately diagnose issues, quickly inspect vehicles, and address malfunctions before they become major concerns.
Examples of OBD2 Data:
Mode 1 (Vehicle Information – Showing Parameter IDs or PIDs):
- Pid 12 — Engine RPM (Revolutions Per Minute)
- Pid 13 — Vehicle Speed
Mode 3 (Trouble Codes – Indicating Fault Area: P= Powertrain, C= Chassis, B= Body, U= Network):
- P0201 — Injector Circuit Malfunction – Cylinder 1
- P0217 — Engine Overtemperature Condition
- P0219 — Engine Overspeed Condition
- C0128 — Low Brake Fluid Circuit
- C0710 — Steering Position Malfunction
- B1671 — Battery Module Voltage Out of Range
- U2021 — Invalid/Faulty Data Received
OBD and Telematics: Connecting Vehicles to the Cloud
The presence of OBD2 enables telematics devices to seamlessly process vital vehicle information such as engine RPM, vehicle speed, trouble codes, fuel consumption, and much more. A telematics device utilizes this data to determine trip start and end times, instances of over-revving, speeding, excessive idling, fuel usage, etc. All this information is then uploaded to a software interface, empowering fleet management teams to monitor vehicle usage and performance effectively.
Given the variety of OBD protocols, not all telematics solutions are designed to be universally compatible with every vehicle type on the road today. Geotab telematics overcomes this challenge by intelligently translating diagnostic codes across different makes and models, including electric vehicles.
With the standardized OBD-II port, connecting a fleet tracking solution to your vehicle is quick and straightforward. For instance, Geotab devices can be set up in under five minutes, minimizing downtime and maximizing operational efficiency.
If your older vehicle or truck lacks a standard OBDII port, adapters are available to bridge the gap. In any case, the installation process remains rapid and doesn’t necessitate specialized tools or professional installer assistance.
WWH-OBD: Taking Diagnostics Global
WWH-OBD stands for World Wide Harmonized On-Board Diagnostics. It’s an international standard for vehicle diagnostics developed by the United Nations as part of the Global Technical Regulation (GTR) mandate. WWH-OBD enhances vehicle data monitoring, including emissions output and engine fault codes, aiming for greater consistency and detail worldwide.
Advantages of WWH-OBD: Enhanced Diagnostic Capabilities
Moving to WWH-OBD offers several technical advantages:
Expanded Data Access
Current OBDII Parameter IDs (PIDs) in Mode 1 are limited to one byte, restricting the availability to 255 unique data types. WWH-OBD expands PIDs and applies these expansions to other OBD-II modes transitioned to WWH through Unified Diagnostic Services (UDS) modes. Adopting WWH standards unlocks access to more extensive data sets and provides scalability for future diagnostic needs.
More Granular Fault Data
Another key benefit of WWH is the enriched information provided within fault codes. OBDII currently uses a two-byte Diagnostic Trouble Code (DTC) to signal a fault (e.g., P0070 indicates a general electrical fault with the ambient air temperature sensor “A”).
Unified Diagnostic Services (UDS) extends the DTC from two bytes to three bytes. The third byte specifies the “failure mode.” This failure mode is analogous to the Failure Mode Indicator (FMI) used in the J1939 protocol. For example, OBDII might list multiple codes for similar sensor issues:
- 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
With WWH-OBD, these are consolidated under a single code, P0070, with five different failure modes indicated in the third byte of the DTC. For instance, P0071 now becomes P0070-1C, providing more specific fault details with fewer overall codes.
WWH also provides additional fault information, including severity/class and status. Severity indicates the urgency for addressing the fault, while the fault class categorizes the fault according to GTR specifications. Fault status indicates whether the fault is pending, confirmed, or if testing for the fault in the current driving cycle is complete.
In essence, WWH-OBD significantly expands the current OBDII framework to deliver richer diagnostic information to users.
Geotab’s WWH-OBD Compatibility
Geotab has already integrated the WWH protocol into our firmware. Geotab employs a sophisticated protocol detection system that securely examines vehicle communication to determine if OBD-II or WWH-OBD (and in some cases, both) are available.
At Geotab, we are committed to continuous firmware enhancements to maximize the data available to our customers. We’ve already begun supporting 3-byte DTC information and are continuously adding more detailed fault information generated by vehicles. When new information becomes accessible via OBDII or WWH-OBD (such as new PIDs or fault data), or when a new protocol is implemented in vehicles, Geotab prioritizes rapid and accurate integration into our firmware. We then immediately deploy these firmware updates to our devices over-the-air, ensuring our customers always benefit from the most comprehensive and up-to-date data insights.
Expanding Beyond OBDII: The Role of UDS
OBDII includes 10 standard modes to obtain the diagnostic information required for emissions standards. However, these 10 modes have become insufficient for accessing the breadth of data modern vehicles offer.
Since the implementation of OBDII, several UDS (Unified Diagnostic Services) modes have been developed to enrich available data. Vehicle manufacturers utilize proprietary PIDs and implement them through these additional UDS modes. Information not initially accessible through OBDII data, like odometer readings and seat belt usage, became available through UDS modes.
UDS offers over 20 additional modes beyond the standard 10 modes in OBDII, significantly expanding diagnostic data potential. WWH-OBD seeks to integrate UDS modes with OBDII, enriching diagnostic data while maintaining a standardized process.
Conclusion: OBD2’s Enduring Importance
In our increasingly connected world driven by the IoT (Internet of Things), the OBD port remains crucial for vehicle health, safety, and sustainability. While the number and variety of connected devices for vehicles are growing, not all devices provide and track the same information. Furthermore, compatibility and security can vary significantly between devices.
With the multitude of OBD protocols, it’s vital to recognize that not all telematics solutions are universally compatible. Effective telematics solutions must be capable of understanding and translating a comprehensive range of vehicle diagnostic codes, ensuring seamless data integration and reliable insights for vehicle owners and fleet operators alike.
