You may have come across the terms “OBD” or “OBDII” when reading about connected vehicles and telematics devices. These features are part of your car’s onboard computer system and have a history that might surprise you. This article provides a detailed overview of OBD2 and explores its evolution, answering the key question: Obd2 Para Que Sirve? or, in English, what is OBD2 used for?
Understanding 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. Essentially, OBD systems allow mechanics and vehicle owners to access the health information of a car’s subsystems, monitor performance, and diagnose repair needs.
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 referred to as the “brain” or computer of your vehicle.
Why is OBD2 So Important?
OBD2 is a cornerstone of modern vehicle maintenance, telematics, and fleet management. Its importance stems from its ability to provide valuable insights into vehicle operation and health.
Thanks to OBD2, individuals and fleet operators can:
- Track Wear and Tear: Identify patterns in component degradation to understand which parts are wearing out faster than expected.
- Enable Proactive Vehicle Management: Instantly diagnose potential vehicle issues before they escalate, facilitating a proactive rather than reactive maintenance approach.
- Measure Driving Behavior: Monitor driving habits, including speed, idling time, and harsh driving events, to improve safety and efficiency.
- Enhance Vehicle Health Monitoring: Gain a comprehensive view of a vehicle’s condition, leading to better maintenance schedules and reduced downtime.
OBD vs. OBDII: What’s the Difference?
Simply put, OBDII is the second generation of OBD, or OBD I. The original OBD was often an external connection to a car’s console, whereas OBDII is integrated directly into the vehicle itself. OBD I was utilized until OBDII was developed in the early 1990s, marking a significant advancement in vehicle diagnostics.
A Brief History of OBDII Development
The story of on-board diagnostics began in the 1960s, with various organizations playing pivotal roles 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).
Prior to standardization, each vehicle manufacturer developed proprietary systems. This meant diagnostic tools and procedures were not universal. Each manufacturer, and sometimes even different models from the same manufacturer, had unique connector types, electronic interface requirements, and custom codes for reporting problems. This lack of uniformity made vehicle diagnostics complex and inefficient.
Key Milestones in OBD History
1968 — Volkswagen introduces the first computer-based OBD system with scanning capabilities.
1978 — Datsun presents a basic OBD system with limited, non-standardized capabilities.
1979 — The Society of Automotive Engineers (SAE) recommends a standardized diagnostic connector and a set of diagnostic test signals.
1980 — GM launches 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 after the 1988 SAE recommendation, advocating for a standard connector and diagnostic set.
1991 — The state of California mandates that all vehicles must incorporate some form of basic on-board diagnostics, known as OBD I.
1994 — California mandates OBD compliance according to SAE recommendations, termed OBDII, for all vehicles sold in the state from 1996 onwards to facilitate widespread emissions testing. OBDII includes a set of standardized Diagnostic Trouble Codes (DTCs).
1996 — OBD-II becomes mandatory for all cars manufactured in the United States.
2001 — EOBD (European version of OBD) becomes mandatory for all gasoline vehicles in the European Union.
2003 — EOBD becomes mandatory for all diesel vehicles in the EU.
2008 — Starting in 2008, all vehicles in the United States are required to implement OBDII via a Controller Area Network, as specified in ISO standard 15765-4.
What Data Can You Access Through OBD2?
OBD2 provides access to a wealth of information regarding vehicle status and Diagnostic Trouble Codes (DTCs) for:
- Powertrain (Engine and Transmission)
- Emission Control Systems
Furthermore, the following vehicle information is accessible via OBD2:
- Vehicle Identification Number (VIN)
- Calibration Identification Number
- Ignition Counter
- Emission Control System Counters
When you take your car for servicing, a mechanic connects a scan tool to the OBDII port to read fault codes and pinpoint issues. This allows for accurate diagnostics, efficient vehicle inspections, and timely repairs, preventing minor problems from becoming major failures.
Examples of OBD2 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 Overtemperature Condition
- P0219 — Engine Overspeed Condition
- C0128 — Brake Fluid Low Circuit
- C0710 — Steering Position Malfunction
- B1671 — Battery Module Voltage Out of Range
- U2021 — Invalid/Faulty Data Received
OBD2 and Telematics Integration
The prevalence of OBDII enables telematics devices to seamlessly process critical vehicle data such as engine RPM, vehicle speed, fault codes, fuel consumption, and much more. Telematics systems leverage this information to determine trip start and end times, instances of over-revving, speeding, excessive idling, fuel usage, and other key performance indicators. This data is then uploaded to a software interface, empowering fleet management teams to monitor vehicle usage and performance effectively.
Given the multitude of OBD protocols, not all telematics solutions are universally compatible with every vehicle type. Geotab telematics overcomes this challenge by intelligently translating diagnostic codes across different makes and models, including electric vehicles.
Connecting a fleet tracking solution to your vehicle via the OBD-II port is typically quick and straightforward. For instance, Geotab devices can be set up in under five minutes. For vehicles lacking a standard OBDII port, adapters are available to ensure compatibility, maintaining a simple and tool-free installation process that doesn’t require professional assistance.
What is WWH-OBD?
WWH-OBD stands for World Wide Harmonized On-Board Diagnostics. It is an international standard for vehicle diagnostics developed by the United Nations as part of the Global Technical Regulation (GTR) mandate. WWH-OBD aims to standardize and enhance vehicle diagnostics, encompassing the monitoring of vehicle data like emissions output and engine fault codes on a global scale.
Advantages of WWH-OBD
Transitioning to WWH-OBD offers several technical advantages:
Expanded Data Access
Current OBDII Parameter IDs (PIDs) used in Mode 1 are limited to one byte, restricting the availability to only 255 unique data types. WWH-OBD expands PIDs and can also be applied to other OBD-II modes transitioned to WWH through Unified Diagnostic Services (UDS) modes. Adopting WWH standards allows for more extensive data sets and future scalability.
More Detailed Fault Information
Another key benefit of WWH-OBD is the enhanced fault information. OBDII currently uses a 2-byte Diagnostic Trouble Code (DTC) to indicate a fault (e.g., P0070 for Ambient Air Temperature Sensor “A” Circuit Malfunction).
Unified Diagnostic Services (UDS) expands the 2-byte DTC to a 3-byte DTC, with the third byte indicating the “failure mode.” This failure mode is similar to the Failure Mode Indicator (FMI) used in the J1939 protocol. For example, OBDII might list separate codes for:
- 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 5 different failure modes indicated in the third byte of the DTC. For instance, P0071 now becomes P0070-1C.
WWH-OBD also provides additional fault details like severity/class and status. Severity indicates the urgency of addressing the fault, while the fault class categorizes the fault according to GTR specifications. The fault status indicates whether the fault is pending, confirmed, or if testing for the fault is complete in the current driving cycle.
In summary, WWH-OBD significantly extends the current OBDII framework to provide users with richer diagnostic information.
Geotab’s WWH-OBD Support
Geotab has already implemented the WWH-OBD protocol in our firmware. Geotab utilizes a sophisticated protocol detection system to safely analyze vehicle communication and determine whether OBD-II or WWH-OBD (or sometimes both) is available.
Geotab continuously enhances its firmware to provide customers with increasingly comprehensive data. Support for 3-byte DTC information is already in place, and ongoing efforts are focused on incorporating more detailed fault information generated by vehicles. When new data becomes accessible via OBDII or WWH-OBD (such as new PIDs or fault data), or when new protocols are implemented in vehicles, Geotab prioritizes rapid and accurate integration into our firmware. These firmware updates are then immediately deployed to devices over-the-air, ensuring customers always benefit from the latest advancements in vehicle diagnostics.
Expanding Beyond OBDII Limitations
OBDII includes 10 standard modes to access the diagnostic information required for emissions standards. However, these 10 modes have proven insufficient for the growing complexity of vehicle systems.
Since the introduction of OBDII, various UDS modes have been developed to enrich available data. Vehicle manufacturers utilize proprietary PIDs and implement them through additional UDS modes. Information not initially accessible through OBDII data (like odometer readings and seat belt usage) has become available through UDS modes.
UDS encompasses over 20 additional modes beyond the 10 standard OBDII modes, offering a significantly larger pool of diagnostic data. WWH-OBD bridges this gap by integrating UDS modes with OBDII, aiming to standardize and enhance the diagnostic data available while maintaining a consistent process.
Conclusion
In our increasingly connected world, the OBD port remains a vital component for vehicle health, safety, and sustainability. While the number and variety of connected devices for vehicles continue to grow, the information provided and tracked can vary significantly. Compatibility and security can also differ across devices.
Given the diverse landscape of OBD protocols, not all telematics solutions are engineered to function with every vehicle type. Effective telematics solutions, like Geotab, must be capable of interpreting and translating a comprehensive range of vehicle diagnostic codes to provide truly valuable insights and ensure broad vehicle compatibility.
