You might have encountered terms like “OBD” and “OBDII,” especially when exploring connected vehicles and devices like the Geotab GO. These systems are integral to a car’s on-board computer, and their history is richer than many realize. This article delves into the history of OBDII, focusing on When Did Obdii Start and tracing its evolution to its current form.
See also:
History of GPS satellites and commercial GPS tracking
The Geotab GO saved my RV vacation
Understanding OBD: The Basics of On-Board Diagnostics
On-board diagnostics (OBD) is essentially an automotive electronic system designed to enable vehicles to self-diagnose and report issues. This capability is invaluable for repair technicians, providing them with access to crucial subsystem information. By using OBD, technicians can effectively monitor vehicle performance and pinpoint repair needs with greater accuracy.
OBD has become the standardized protocol across the majority of light-duty vehicles for accessing vehicle diagnostic data. This information is generated by engine control units (ECUs), often referred to as engine control modules, which act as the vehicle’s central processing units or computers.
The Significance of OBD in Modern Vehicles
OBD’s importance extends deeply into telematics and fleet management, becoming indispensable for assessing and managing vehicle health and driving behavior.
With OBD systems, fleets gain significant advantages:
- Predictive Maintenance: Track wear patterns to identify vehicle components that are degrading faster than expected, facilitating timely replacements.
- Proactive Problem Diagnosis: Instantly identify potential vehicle issues before they escalate, enabling proactive maintenance strategies.
- Comprehensive Performance Monitoring: Measure and analyze driving behavior, including speed, idling time, and various other critical parameters.
Locating the OBDII Port in Your Vehicle
For most passenger vehicles, the OBDII port is typically located beneath the dashboard on the driver’s side. The exact configuration of the port can vary based on vehicle type, potentially featuring 16-pin, 6-pin, or 9-pin setups.
If you’re interested in connecting a Geotab GO device to your vehicle’s OBD port, further guidance is available in How to install a Geotab GO vehicle tracking device.
OBD vs. OBDII: What’s the Real Difference?
OBDII is essentially the second generation, an evolution of the original OBD (OBD I). The primary distinction lies in their integration and sophistication. OBD I was typically an external add-on to a car’s console, while OBDII is designed as an integrated component within the vehicle itself. OBD I systems were prevalent until the introduction of OBDII in the early 1990s.
For a deeper understanding of the OBD port’s value, the white paper Preserving privacy and security in the connected vehicle: The OBD port on the road ahead provides valuable insights.
Tracing the History: When Did OBDII Actually Start?
The history of on-board diagnostics dates back to the 1960s, with numerous organizations laying the groundwork for the standards we know today. Key players in this development 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).
Prior to standardization, vehicle manufacturers operated independently, developing proprietary systems. This meant diagnostic tools varied significantly, with each manufacturer (and sometimes even different models from the same manufacturer) using unique connector types, electronic interface requirements, and custom codes for reporting issues. This lack of uniformity highlighted the critical need for a standardized approach to vehicle diagnostics.
Key Milestones in OBD History: A Timeline to OBDII
Let’s explore the key milestones in the development of OBD systems, leading to the standardization of OBDII and answering the question “when did OBDII start?”:
1968: Volkswagen takes the first step by introducing the first OBD computer system with scanning capability. This marked the beginning of automated vehicle diagnostics.
1978: Datsun follows suit, implementing a simple OBD system, though with limited and non-standardized capabilities. This shows the growing industry recognition of the need for on-board diagnostics.
1979: The Society of Automotive Engineers (SAE) recognizes the need for standardization and recommends a standardized diagnostic connector and a set of diagnostic test signals. This was a crucial step towards industry-wide compatibility.
1980: General Motors (GM) develops a proprietary interface and protocol that provides engine diagnostics via an RS-232 interface, or more simply, through flashing the Check Engine Light. This demonstrates early attempts at practical diagnostic outputs, even if not yet standardized.
1988: Standardization begins to take shape in the late 1980s, building upon the 1988 SAE recommendation for a standard connector and diagnostic set. This laid the groundwork for OBD standardization.
1991: The state of California mandates basic on-board diagnostics for all vehicles sold in the state. This regulation, known as OBD I, was a significant push towards implementing diagnostic systems.
1994: California takes a decisive step by mandating that all vehicles sold in the state from 1996 onwards must incorporate OBD as recommended by SAE – now known as OBDII. This mandate, driven by the need for consistent emissions testing, is a direct answer to when did OBDII start becoming a requirement. OBDII included standardized diagnostic trouble codes (DTCs), streamlining fault identification.
1996: OBD-II becomes mandatory for all cars manufactured in the United States. This marks the nationwide adoption of OBDII, solidifying its place as the standard for vehicle diagnostics.
2001: The European version of OBD, EOBD, becomes mandatory for all gasoline vehicles in the European Union (EU). This extends the reach of standardized diagnostics beyond North America.
2003: EOBD expands to become mandatory for all diesel vehicles in the EU. This further broadens the application of standardized on-board diagnostics in Europe.
2008: In the US, all vehicles are required to implement OBDII via a Controller Area Network as specified by ISO 15765-4. This update enhances the communication protocol used by OBDII systems, reflecting advancements in vehicle technology.
This timeline clearly illustrates that OBDII started its mandatory journey in 1996 in the United States, following the California mandate in 1994 that set the stage for its nationwide adoption.
OBDII Data Access: What Information Can You Retrieve?
OBDII offers access to a wealth of status information and Diagnostic Trouble Codes (DTCs), primarily focusing on:
- Powertrain: Covering engine and transmission systems.
- Emission Control Systems: Monitoring components critical for environmental compliance.
Beyond these primary areas, OBDII also provides access to essential vehicle identification and system data, including:
- 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, retrieve trouble codes, and accurately diagnose issues. This capability ensures efficient vehicle inspections and allows for timely repairs, preventing minor malfunctions from becoming major problems.
Examples of OBDII Data:
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 comprehensive list of diagnostic trouble codes, refer to this list of standard diagnostic trouble codes.
OBD and Telematics: A Powerful Combination
The OBDII port is fundamental to the functionality of telematics devices. These devices leverage the OBDII connection to silently gather data such as engine revolutions, vehicle speed, fault codes, and fuel consumption. This information is then processed to determine trip details, instances of over-revving, speeding, excessive idling, fuel efficiency, and more. The collected data is transmitted to a software interface, enabling fleet managers to effectively monitor vehicle usage and performance.
Geotab telematics solutions are designed to overcome the challenges posed by diverse OBD protocols across vehicle makes and models, including electric vehicles. Geotab achieves this by normalizing the vehicle diagnostic codes, ensuring compatibility and consistent data interpretation.
See also: Data normalization and why it matters
Connecting a fleet tracking solution via the OBD-II port is typically quick and straightforward. For instance, Geotab devices can be set up in under five minutes.
Even for vehicles lacking a standard OBDII port, adapters can be used to facilitate connection, ensuring a rapid installation process without requiring specialized tools or professional assistance.
WWH-OBD: The Future of Vehicle Diagnostics
WWH-OBD, or World Wide Harmonized on-board diagnostics, represents the next evolution in vehicle diagnostics. It is an international standard established by the United Nations as part of the Global Technical Regulations (GTR) mandate. WWH-OBD aims to standardize and enhance vehicle data monitoring, including emissions output and engine fault codes, on a global scale.
Advantages of WWH-OBD: Enhanced Diagnostic Capabilities
Moving towards WWH-OBD offers several key advantages, particularly in terms of technical capabilities:
Expanded Data Type Access
Current OBDII PIDs in Mode 1 are limited to one byte, restricting the number of unique data types to 255. WWH-OBD allows for the expansion of PIDs, and this extensibility can be applied to other OBD-II modes transitioned to WWH via UDS modes. Adopting WWH standards paves the way for accessing more data and provides scalability for future diagnostic needs.
More Granular Fault Data
WWH-OBD significantly improves the detail level of 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 failure “mode,” similar to the failure mode indicator (FMI) used in the J1939 protocol. This enhancement consolidates multiple OBDII fault codes into a single WWH-OBD code with distinct failure modes.
For example, multiple OBDII codes related to the Ambient Air Temperature Sensor Circuit (like P0070, P0071, P0072, P0073, P0074) are consolidated in WWH-OBD into a single code (e.g., P0070) with different failure modes indicated in the third byte (e.g., P0071 becomes P0070-1C).
WWH-OBD also enriches fault information with severity/class and status indicators. Severity indicates the urgency of addressing the fault, while class categorizes the fault according to GTR specifications. Fault status indicates whether it is pending, confirmed, or if testing is complete within the current driving cycle.
In essence, WWH-OBD builds upon the OBDII framework, offering users significantly more diagnostic information.
Geotab’s Commitment to WWH-OBD Support
Geotab has proactively integrated the WWH protocol into its firmware. Geotab’s system intelligently detects and analyzes vehicle communication protocols to determine if OBD-II or WWH-OBD (or both) are available, ensuring comprehensive compatibility.
Geotab continuously refines its firmware to enhance the data insights provided to customers. Support for 3-byte DTC information is already implemented, with ongoing efforts to incorporate more detailed fault data. Geotab prioritizes rapidly integrating new data and protocols—whether new PIDs, fault data from OBDII or WWH-OBD, or entirely new protocols—into its firmware. These firmware updates are seamlessly delivered over-the-air, ensuring Geotab customers always benefit from the latest diagnostic advancements.
Expanding Diagnostic Horizons Beyond OBDII
While OBDII established 10 standard modes for essential emission-related diagnostics, these have become insufficient for modern vehicle diagnostic needs.
Over time, various UDS modes have been developed to augment the data available beyond OBDII standards. Vehicle manufacturers utilize proprietary PIDs and implement them through additional UDS modes to access data not mandated by OBDII, such as odometer readings and seatbelt usage.
UDS encompasses over 20 additional modes beyond the standard 10 in OBDII, offering a vastly richer data pool. WWH-OBD aims to bridge this gap by integrating UDS modes with OBDII, enhancing diagnostic data availability while maintaining a standardized framework.
Conclusion: The Enduring Relevance of OBD and OBDII
In the expanding landscape of IoT, the OBD port remains a critical component for vehicle health, safety, and sustainability. Despite the proliferation of connected vehicle devices, data reporting, tracking capabilities, compatibility, and security remain inconsistent across different devices.
Given the multitude of OBD protocols, telematics solutions must be capable of working with a wide range of vehicle types. Effective telematics solutions, like Geotab, are designed to interpret and translate a comprehensive array of vehicle diagnostic codes, ensuring broad compatibility and reliable data.
To learn more about selecting the right GPS vehicle tracking device, refer to: Not All OBD Plug-In Fleet Management Devices Are Made Equal.
Furthermore, ensuring the cybersecurity of third-party devices connected to the OBDII port is paramount. For insights into telematics cybersecurity best practices for fleet tracking, explore these 15 security recommendations.
