You may have come across the terms “OBD” or “OBDII” when reading about connected vehicles and car diagnostic tools. These features are integral parts of modern car computer systems and have a history that is perhaps not widely known. This article provides a comprehensive overview of OBDII and the evolution of this crucial automotive technology, focusing on what OBD2 means when you see it referenced with scanners.
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. An OBD system allows technicians to access subsystem information to monitor vehicle performance and diagnose repair needs efficiently.
OBD is the standardized protocol used in most light-duty vehicles to retrieve vehicle diagnostic information. This information is generated by the Engine Control Units (ECUs) or engine control modules within a vehicle. Think of these ECUs as the computers or the “brain” of your car.
Why is OBD Important?
OBD is a vital component in vehicle maintenance and understanding your car’s health. It’s particularly important for vehicle owners and mechanics because it allows for quicker and more accurate diagnoses of potential issues.
Thanks to OBD, vehicle owners and technicians can:
- Identify potential problems early by reading diagnostic trouble codes.
- Understand the severity and nature of issues indicated by the check engine light.
- Access real-time data about vehicle performance for troubleshooting.
- Ensure vehicles are running efficiently and meeting emissions standards.
For fleet management, the benefits are even more pronounced:
- Track wear and tear trends to identify parts that degrade faster than others across a fleet.
- Instantly diagnose vehicle problems proactively, enabling preventative maintenance rather than reactive repairs.
- Measure driving behavior, including speed, idling time, and other performance metrics.
Locating the OBDII Port
In a typical passenger vehicle, the OBDII port is usually 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 configuration, which is the most common, or sometimes 6 or 9 pins in older or specialized vehicles. Consult your vehicle’s manual if you’re unsure of the exact location.
OBD vs. OBDII: What’s the Difference?
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 directly within the vehicle itself. OBD was utilized until OBDII was developed in the early 1990s.
The key differences lie in standardization and capability. OBD-I was largely manufacturer-specific, meaning each car maker might have had their own diagnostic connectors, protocols, and trouble codes. OBD-II brought standardization to these aspects, making diagnostics more universal and easier to perform across different makes and models. OBDII also significantly expanded the amount of data and diagnostic information available compared to OBD-I.
The History of OBDII Development
The history of on-board diagnostics stretches back to the 1960s. Several organizations played a foundational role in establishing 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).
It’s important to recognize that prior to standardization, vehicle manufacturers developed their own proprietary systems. Each manufacturer’s tools (and sometimes even models from the same manufacturer) had unique connector types and electronic interface requirements. They also used custom codes to report problems, making vehicle repair and diagnostics a much more complex task.
Key Milestones in OBD History
1968 — Volkswagen introduced the first computer-based OBD system with scan capability.
1978 — Datsun (now Nissan) 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 — Standardization of on-board diagnostics began in the late 1980s following the 1988 SAE recommendation, calling for a standard connector and set of diagnostics.
1991 — The state of California mandated that all vehicles have some form of basic on-board diagnostics. This became known as OBD I.
1994 — 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 set of standardized Diagnostic Trouble Codes (DTCs).
1996 — OBD-II became mandatory for all cars manufactured in the United States.
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 — Starting in 2008, all vehicles in the United States were required to implement OBDII via a Controller Area Network as specified in ISO standard 15765-4.
What Data Can You Access with OBDII?
OBDII provides access to both 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:
- Vehicle Identification Number (VIN)
- Calibration Identification Number
- Ignition counter
- Emission control system counters
When you take your car to a repair shop for a check-up, a mechanic can connect to the OBD port with a scan tool, read the fault codes, and pinpoint the problem. This means mechanics can accurately diagnose issues, quickly inspect the vehicle, and fix any faults before they escalate into major problems. This is what “Que Significa Obd2 En Un Escaner” is all about – understanding the diagnostic information a scanner retrieves via OBD2.
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 Overtemp 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
OBD and Telematics
The presence of OBDII enables telematics devices to seamlessly 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 times, over-revving, speeding, excessive idling, fuel usage, etc. All this information is then uploaded to a software interface, allowing fleet management teams to monitor vehicle usage and performance effectively.
With the multitude of OBD protocols, not all telematics solutions are designed to work with every type of vehicle on the road today. Geotab telematics overcomes this challenge by translating diagnostic codes from different makes and models, and even electric vehicles.
Using the OBD-II port, you can quickly and easily connect a fleet tracking solution to your vehicle. In the case of Geotab, setup can be completed in under five minutes.
If your vehicle or truck doesn’t have a standard OBDII port, an adapter can be used instead. In either case, the installation process is fast and doesn’t require any special tools or professional installer assistance.
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. WWH-OBD expands upon OBDII and includes monitoring vehicle data such as emissions output and engine fault codes with greater detail and standardization globally.
Advantages of WWH-OBD
Moving to WWH-OBD offers several technical advantages:
Access to More Data Types
Currently, the PIDs (Parameter IDs) in OBDII used in Mode 1 are only one byte, meaning only up to 255 unique data types are available. Expanding PIDs, as done in WWH-OBD through Unified Diagnostic Services (UDS) modes, opens up the potential for significantly more data availability. Adopting WWH standards allows for richer data and provides scalability for future expansion.
More Detailed Fault Information
Another key advantage of WWH-OBD is the expanded information contained within a fault code. Currently, OBDII uses a two-byte Diagnostic Trouble Code (DTC) to indicate when a fault has occurred (e.g., P0070 indicates that the ambient air temperature sensor “A” has a general electrical fault).
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-OBD, these are all 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 more fault-related information such as severity/class and status. Severity indicates how quickly the fault should be addressed, while the fault class indicates which group the fault belongs to according to GTR specifications. Additionally, fault status indicates if a fault is pending, confirmed, or if the test for this fault has been completed in the current driving cycle.
In summary, WWH-OBD expands the current OBDII framework to offer even richer diagnostic information to the user.
Geotab Supports WWH-OBD
Geotab has already implemented the WWH protocol in our firmware. Geotab employs a sophisticated protocol detection system, where we safely examine what is available on the vehicle to determine whether OBD-II or WWH-OBD is available (in some cases, both are).
At Geotab, we are continuously improving our firmware to further enhance the information our customers receive. We have already begun supporting 3-byte DTC information and continue to add more detail about vehicle-generated faults. When new information becomes available through OBDII or WWH-OBD (such as a new PID or fault data), or if a new protocol is implemented in vehicles, Geotab prioritizes quickly and accurately adding it to the firmware. We then immediately push the new firmware to our devices over-the-air, ensuring our customers always get the most benefit from their devices.
Growth Beyond OBDII
OBDII contains 10 standard modes to obtain the diagnostic information required for emissions standards. The challenge is that these 10 modes have become insufficient for the increasing complexity of vehicle systems.
Over the years since OBDII implementation, several UDS modes have been developed to enrich available data. Each vehicle manufacturer uses their own PIDs and implements them using additional UDS modes. Information not required through OBDII data (such as odometer readings and seat belt usage) became available through UDS modes.
The reality is that UDS contains more than 20 additional modes beyond the current 10 standard modes available through OBDII, meaning UDS has significantly more information available. This is where WWH-OBD steps in, aiming to incorporate UDS modes with OBDII to enrich the diagnostic data available, while still maintaining a standardized process.
Conclusion
In the ever-expanding world of IoT, the OBD port remains critically important for vehicle health, safety, and sustainability. While the number and variety of connected devices for vehicles are increasing, not all devices provide and track the same information. Furthermore, compatibility and security can vary from device to device.
With the multitude of OBD protocols, it’s crucial to choose telematics solutions that are designed to work across a wide range of vehicles and understand and translate a comprehensive set of vehicle diagnostic codes. Understanding “que significa obd2 en un escaner” is just the beginning – the world of vehicle diagnostics is constantly evolving, and staying informed is key to maximizing vehicle performance and longevity.
