You might have heard about OBD or OBDII, especially when looking into vehicle technology and devices like the Geotab GO. These systems are part of your car’s computer system and have a fascinating history. Let’s dive into the story of OBDII and trace its development.
Read more:
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 car’s self-check system. It’s an electronic system in vehicles that can diagnose issues and report them to repair technicians. Think of it as a way for your car to talk about its health. OBD gives mechanics access to information about various subsystems, allowing them to monitor performance and pinpoint repair needs.
OBD is the common language used in most cars and light trucks to get diagnostic information. This information comes from the engine control units (ECUs), which are like the car’s brain or computer, managing different functions.
Why OBD Matters
OBD is crucial for modern vehicle management, including telematics and fleet operations. It provides valuable data for understanding vehicle health and driving behavior.
Thanks to OBD, fleet managers and vehicle owners can:
- Monitor wear and tear patterns on vehicle parts.
- Get early warnings about potential vehicle problems, enabling proactive maintenance.
- Track driving habits, speed, idling time, and much more for performance analysis.
Finding the OBDII Port
In most cars, the OBDII port is located under the dashboard on the driver’s side. It’s usually easy to access. Depending on the vehicle, the port can have different pin configurations, such as 16-pin, 6-pin, or 9-pin.
If you’re interested in connecting a device like a Geotab GO for vehicle tracking, you can learn more about the process in this guide: How to install a Geotab GO vehicle tracking device.
OBD vs. OBDII: What’s the Difference?
OBDII is simply the next generation of OBD, or OBD I. The main difference is that OBD I systems were often external to the car’s main computer, while OBDII is integrated into the vehicle’s system. OBD I was the standard until OBDII was developed in the early 1990s.
For deeper insights into the importance of the OBD port, check out this white paper: Preserving privacy and security in the connected vehicle: The OBD port on the road ahead.
The Evolution of OBDII: A Timeline
The story of on-board diagnostics began in the 1960s. Several organizations played a key role in establishing 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, car manufacturers had their own unique diagnostic systems. This meant tools and connectors varied between brands, and even sometimes between different models from the same brand. Each used their own specific codes to report problems.
Key Moments in OBD History:
1968 — Volkswagen introduced the first OBD computer system with scanning capabilities.
1978 — Datsun created a basic OBD system, although it had limited and non-standardized features.
1979 — The Society of Automotive Engineers (SAE) proposed a standard diagnostic connector and a set of diagnostic test signals for all manufacturers to follow.
1980 — GM developed its own interface and protocol that could provide engine diagnostics through an RS-232 interface, or more simply, by flashing the Check Engine Light.
1988 — Standardization efforts for on-board diagnostics gained momentum after the 1988 SAE recommendation for a universal connector and diagnostic standards.
1991 — California became the first state to require all vehicles to have some form of basic on-board diagnostics, known as OBD I.
1994 — California mandated OBDII for all vehicles sold in the state starting in 1996. This was based on SAE recommendations and driven by the need for consistent emissions testing. OBDII included standardized diagnostic trouble codes (DTCs) for easier problem identification.
1996 — OBD-II became mandatory for all cars manufactured in the United States. This was the year OBD2 truly became the standard across the US automotive industry.
2001 — EOBD, the European version of OBD, became mandatory for all gasoline vehicles in the European Union (EU).
2003 — EOBD extended to become mandatory for all diesel vehicles in the EU.
2008 — In the US, OBDII requirements evolved further. Starting in 2008, all vehicles were required to implement OBDII using a Controller Area Network as specified by ISO 15765-4, improving data communication speed and reliability.
What Kind of Data Does OBDII Provide?
OBDII gives access to a range of status information and Diagnostic Trouble Codes (DTCs) related to:
- Powertrain systems (engine and transmission)
- Emission Control Systems
In addition, you can retrieve other important vehicle information through OBDII, such as:
- Vehicle Identification Number (VIN)
- Calibration Identification Number
- Ignition counter
- Emissions Control System counters
When you take your car to a mechanic, they can connect a scan tool to the OBD port. This tool reads the trouble codes, helping them quickly diagnose problems. This means faster and more accurate diagnoses, allowing for quicker repairs and preventing minor issues from becoming major headaches.
Examples of OBDII Data:
Mode 1 (Vehicle Information):
- Pid 12 — Engine RPM (Revolutions Per Minute)
- Pid 13 — Vehicle Speed
Mode 3 (Trouble Codes: Codes start with P for Powertrain, C for Chassis, B for Body, U for 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 comprehensive list of codes, you can refer to this list of standard diagnostic trouble codes.
OBD and Telematics Systems
The OBDII port is fundamental to how telematics devices work. These devices use the OBDII connection to gather information silently, such as engine speed, vehicle speed, fault codes, and fuel consumption. Telematics devices analyze this data to determine things like trip start and end times, instances of over-revving or speeding, excessive idling, and fuel efficiency. This information is then sent to a software platform, allowing fleet managers and vehicle owners to monitor vehicle usage and performance effectively.
While OBD protocols are widespread, not all telematics solutions are compatible with every vehicle type. Geotab telematics addresses this challenge by being able to interpret diagnostic codes from a wide range of makes and models, including electric vehicles.
Related reading: Data normalization and why it matters
Using the OBD-II port makes installing a fleet tracking solution straightforward. For example, Geotab devices can be set up in under five minutes.
If a vehicle doesn’t have a standard OBDII port, adapters are available to ensure compatibility. Installation is generally quick and easy, requiring no specialized tools or professional help.
Exploring WWH-OBD
WWH-OBD, or World Wide Harmonized on-board diagnostics, is an international standard for vehicle diagnostics. It’s part of the United Nations’ Global Technical Regulations (GTR), focusing on monitoring vehicle data like emissions and engine fault codes on a global scale.
Advantages of WWH-OBD
Moving towards WWH-OBD offers several technical benefits:
More Data Variety
Current OBDII PIDs in Mode 1 use only one byte, limiting the number of unique data types to 255. WWH-OBD allows for expansion of PIDs, and this can extend to other OBD-II modes through UDS (Unified Diagnostic Services) modes. Adopting WWH standards means access to more data and scalability for future needs.
Enhanced Fault Data
WWH-OBD also improves the detail within fault data. OBDII uses a two-byte diagnostic trouble code (DTC). For example, P0070 indicates a general electrical issue with the Ambient Air Temperature Sensor “A”.
Unified Diagnostic Services (UDS) expands the DTC to three bytes. The third byte specifies the “failure mode,” similar to the failure mode indicator (FMI) in the J1939 protocol. For example, in OBDII, you might see separate codes like:
- 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 in the third byte. P0071, for instance, becomes P0070-1C.
WWH also provides more fault information like severity/class and status. Severity indicates the urgency of checking the fault, while class categorizes the fault according to GTR specifications. The status shows if the fault is pending, confirmed, or if the test is completed in the current driving cycle.
In short, WWH-OBD builds upon OBD II to provide richer diagnostic information.
Geotab’s WWH-OBD Support
Geotab firmware already supports the WWH protocol. Our system intelligently detects the vehicle protocol, identifying whether OBD-II or WWH is available (and sometimes both).
Geotab is committed to continuous firmware improvement to give customers the best possible data. We support 3-byte DTC information and are constantly adding more fault data. When new data becomes available through OBDII or WWH, or when new vehicle protocols emerge, Geotab prioritizes incorporating them into our firmware. Updates are then delivered over-the-air to our devices, ensuring customers always benefit from the latest advancements.
Beyond OBDII: Expansion and the Future
OBDII includes 10 standard modes for emissions-related diagnostics. However, these modes have become insufficient for the increasing complexity of vehicle systems.
UDS modes have evolved to expand available data beyond OBDII’s limitations. Car manufacturers use proprietary PIDs (parameter IDs) and implement them through extra UDS modes. Information not covered by OBDII, like odometer readings and seatbelt usage, became accessible through UDS.
UDS offers over 20 additional modes compared to OBDII’s 10, significantly increasing available data. WWH-OBD aims to integrate UDS modes with OBDII, enhancing diagnostic data while maintaining a standardized approach.
Conclusion: OBD’s Enduring Role
In our increasingly connected world, the OBD port remains vital for vehicle health, safety, and environmental sustainability. While the number of connected vehicle devices grows, they don’t all track the same information, and compatibility and security can vary.
Given the variety of OBD protocols, it’s essential to choose telematics solutions that can effectively handle a wide range of vehicle diagnostic codes. Robust telematics systems should be able to interpret and standardize this diverse data.
To learn more about selecting a GPS vehicle tracking device, read: Not All OBD Plug-In Fleet Management Devices Are Made Equal.
Also, security is paramount when using third-party OBDII devices. For cybersecurity best practices in fleet tracking telematics, review these 15 security recommendations.
