You may have come across the terms “OBD” or “OBDII” when reading about connected vehicles and devices. These features are integral to your car’s on-board computers and have a history that is perhaps not widely known. In this article, we provide a comprehensive overview of OBDII and a timeline of its development, explaining the true OBD2 meaning and its significance in modern vehicles.
What is OBD (On-Board Diagnostics)?
On-Board Diagnostics (OBD) refers to the automotive electronic system that provides vehicle self-diagnosis and reporting capabilities for repair technicians. An OBD system allows technicians to access subsystem information to monitor performance and diagnose repair needs. Understanding the OBD2 meaning starts with grasping its fundamental purpose: to give insights into a vehicle’s health.
OBD is the standard protocol used in most light-duty vehicles to retrieve vehicle diagnostic information. This information is generated by Engine Control Units (ECUs), or engine control modules, within a vehicle. Think of them as the computers or the brain of the vehicle. The evolution and standardization of these systems are key to understanding the full OBD2 meaning.
Why is OBD So Important?
OBD is a crucial component of telematics and fleet management, enabling the measurement and management of vehicle health and driving behavior. The importance of OBD2 meaning extends to various practical applications, especially for businesses operating vehicle fleets.
Thanks to OBD, fleets can:
- Track wear and tear trends and identify vehicle parts that degrade faster than others.
- Instantly diagnose vehicle problems before they escalate, supporting proactive rather than reactive maintenance management.
- Measure driving behavior, speed, idling time, and much more, all thanks to the data accessible through understanding the OBD2 meaning.
Where is the OBDII Port Located?
In a typical passenger vehicle, the OBDII port is located on the underside of the dashboard on the driver’s side of the car. Depending on the vehicle type, the port may have a 16-pin, 6-pin, or 9-pin configuration. Knowing the location of this port is essential for anyone wanting to leverage the OBD2 meaning for vehicle diagnostics.
What is the Difference Between OBD and OBDII?
Simply put, OBDII is the second generation of OBD, or OBD I. OBD I was initially connected externally to a car’s console, whereas OBDII is now integrated within the vehicle itself. The original OBD was in use until OBDII was developed in the early 1990s. The enhanced capabilities and standardization are central to the OBD2 meaning.
History of OBDII
The history of on-board diagnostics dates back to the 1960s. Several organizations laid the groundwork for the standard, 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). Understanding this history provides context to the OBD2 meaning and its current form.
It’s important to note that prior to standardization, manufacturers created their own systems. Each manufacturer’s tools (and sometimes models from the same manufacturer) had their own type of connector and electronic interface requirements. They also used their own custom codes to report issues. The push for standardization was vital in shaping the OBD2 meaning and accessibility we know today.
Key Milestones in OBD History
1968 — Volkswagen introduced the first computer-based OBD system with scanning capability.
1978 — Datsun introduced a simple OBD system with limited, non-standardized capabilities.
1979 — The Society of Automotive Engineers (SAE) recommended a standardized diagnostic connector and a set of diagnostic test signals.
1980 — GM introduced 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 — On-board diagnostics standardization arrived in the late 1980s following the 1988 SAE recommendation, which called for a standard connector and set of diagnostics. This was a crucial step in defining the OBD2 meaning as a unified standard.
1991 — The state of California mandated that all vehicles have some form of basic on-board diagnostics. This is known as OBD I.
1994 — The state of California mandated that all vehicles sold in the state from 1996 onwards must have OBD as recommended by SAE, now termed OBDII, to enable widespread emissions testing. OBDII included a series of standardized Diagnostic Trouble Codes (DTCs). This mandate significantly solidified the OBD2 meaning and its role in vehicle maintenance.
1996 — OBD-II became mandatory for all cars manufactured in the United States. This marked a definitive point in the widespread adoption and understanding of OBD2 meaning.
2001 — EOBD (the European version of OBD) became mandatory for all gasoline vehicles in the European Union.
2003 — EOBD became mandatory for all diesel vehicles in the EU.
2008 — From 2008 onwards, all vehicles in the United States are required to implement OBDII via a Controller Area Network, as specified in ISO standard 15765-4. This advanced the technical specifications underpinning the OBD2 meaning.
What Data Can Be Accessed from OBDII?
OBDII provides access to status information and Diagnostic Trouble Codes (DTCs) for:
- Powertrain (engine and transmission)
- Emission control systems
In addition, the following vehicle information can be accessed via OBDII, further enriching the OBD2 meaning in terms of data accessibility:
- Vehicle Identification Number (VIN)
- Calibration Identification number
- Ignition counter
- Emission control system counters
When a car is taken to a service center for a check-up, a mechanic can connect to the OBD port with a scan tool, read the fault codes, and pinpoint the issue. This means mechanics can accurately diagnose faults, inspect the vehicle quickly, and fix any issues before they become serious problems. This diagnostic capability is a cornerstone of the practical OBD2 meaning.
Examples:
Mode 1 (Vehicle Information):
- Pid 12 — Engine RPM
- Pid 13 — Vehicle Speed
Mode 3 (Fault Codes: P= Powertrain, C= Chassis, B= Body, U= Network):
- P0201 — Injector Circuit Malfunction – Cylinder 1
- P0217 — Engine Overtemperature Condition
- P0219 — Engine Overspeed Condition
- C0128 — Brake Fluid Low Circuit
- C0710 — Steering Position Malfunction
- B1671 — Battery Module Voltage Out of Range
- U2021 — Data Received Invalid/Error
OBD and Telematics
The presence of OBDII allows telematics devices to silently process information such as engine RPM, vehicle speed, fault codes, fuel consumption, and much more. The telematics device can use this information to determine trip start and end, over-revving, speeding, excessive idling, fuel usage, etc. All this information is uploaded to a software interface and enables the fleet management team to monitor vehicle usage and performance. This integration with telematics expands the practical OBD2 meaning beyond just diagnostics.
With the multitude of OBD protocols, not all telematics solutions are designed to work with every type of vehicle currently available. Geotab telematics overcomes this challenge by translating diagnostic codes from different makes and models, and even electric vehicles. This broad compatibility enhances the real-world OBD2 meaning for diverse vehicle types.
With the OBD-II port, a fleet tracking solution can be connected to your vehicle quickly and easily. In the case of Geotab, it can be set up in under five minutes. The ease of installation is a significant advantage in leveraging the OBD2 meaning for fleet management.
If your vehicle or truck does not have a standard OBDII port, an adapter can be used instead. In any case, the installation process is quick and does not require any special tools or the help of a professional installer.
What is WWH-OBD?
WWH-OBD stands for World Wide Harmonized On-Board Diagnostics. It is an international standard used for vehicle diagnostics, implemented by the United Nations as part of the Global Technical Regulation (GTR) mandate, which includes monitoring vehicle data such as emissions output and engine fault codes. WWH-OBD represents an evolution in the OBD2 meaning, aiming for global harmonization.
Advantages of WWH-OBD
Below are the advantages of moving to WWH in more technical terms:
Access to More Data Types
Currently, OBDII Parameter IDs (PIDs) used in Mode 1 are only one byte, meaning only up to 255 unique data types are available. The expansion of PIDs could also be applied to other OBD-II modes that have moved to WWH via UDS modes. Adopting WWH standards allows for more data and offers room for future expansion, enriching the potential OBD2 meaning.
More Detailed Fault Data
Another advantage of WWH is the expansion of the information contained within a fault. Currently, OBDII uses a two-byte Diagnostic Trouble Code (DTC) to indicate when a fault has occurred (e.g. P0070 indicates the ambient air temperature sensor “A” has a general electrical fault). WWH-OBD enhances the granularity and depth of OBD2 meaning in fault diagnostics.
Unified Diagnostic Services (UDS) expands the 2-byte DTC into a 3-byte DTC, where the third byte indicates the “failure mode.” This failure mode is similar to the Failure Mode Indicator (FMI) used in the J1939 protocol. For example, previously in OBDII, you might have the following five faults:
- 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, all of these are consolidated into one code P0070, with 5 different failure modes indicated in the third byte of the DTC. For example, P0071 now becomes P0070-1C. This refined fault reporting is a significant advancement in the OBD2 meaning for technicians.
WWH also offers more fault information such as severity/class and status. Severity will indicate how soon the fault needs to be reviewed, while the fault class will indicate which group the fault belongs to as per GTR specifications. Additionally, the fault status will indicate if it is pending, confirmed, or if the test for this fault has been completed in the current driving cycle. These enhancements contribute to a more comprehensive OBD2 meaning in fault management.
In summary, WWH-OBD expands upon the current OBDII framework to offer even more diagnostic information to the user, further clarifying and extending the OBD2 meaning.
Geotab Supports WWH-OBD
Geotab has already implemented the WWH protocol in our firmware. Geotab employs a complex protocol detection system, where we safely probe what is available on the vehicle, to find out if OBD-II or WWH is available (in some cases, both are). Geotab’s support for WWH-OBD underscores the evolving OBD2 meaning and its future.
At Geotab, we are constantly improving our firmware to further expand the information our customers obtain. We have already started to support the 3-byte DTC information and continue to add more fault information being generated in vehicles. When new information becomes available via OBDII or WWH (such as a new PID or fault data), or if a new protocol is implemented in the vehicle, Geotab prioritizes quickly and accurately adding it to the firmware. We then immediately send the new firmware to our units over the cloud so our customers get the most benefit from their devices at all times. This proactive approach ensures Geotab users always benefit from the latest advancements in OBD2 meaning and diagnostic capabilities.
Growth Beyond OBDII
OBDII contains 10 standard modes for getting the diagnostic information required for emissions standards. The problem is that these 10 modes have not been sufficient. The limitations of the initial OBDII standards highlight the ongoing evolution of the OBD2 meaning.
Over the years since OBDII implementation, several UDS modes have been developed to enrich the data available. Each vehicle manufacturer uses their own PIDs and implements them via additional UDS modes. Information that was not required via OBDII data (such as odometer and seat belt usage) became available via UDS modes. The expansion beyond the original OBDII scope is critical to understanding the contemporary OBD2 meaning.
The reality is that UDS contains more than 20 additional modes, on top of the current 10 standard modes available via OBDII, meaning UDS has more information available. But that is where WWH-OBD comes in, which seeks to incorporate UDS modes with OBDII to enrich the data available for diagnostics, while still maintaining a standardized process. WWH-OBD is a key part of the future OBD2 meaning, incorporating broader data access.
Conclusion
In the growing world of IoT, the OBD port remains important for vehicle health, safety, and sustainability. Although the number and variety of connected devices for vehicles is increasing, not all devices give and track the same information. Furthermore, compatibility and security can vary from device to device. The enduring relevance of OBD ports reinforces the ongoing OBD2 meaning in the connected vehicle landscape.
With the multitude of OBD protocols, not all telematics solutions are designed to work with every type of vehicle currently available. Good telematics solutions should be able to understand and translate a comprehensive set of vehicle diagnostic codes. This capability is essential to fully realize the practical OBD2 meaning for fleet management and vehicle maintenance.
