How OBD2 works

What problem was OBD2 built to solve

Before the mid 1990s, every automaker used its own diagnostic connector, its own code numbers and its own scan tool. A codes reader built for one brand was useless on another, and emissions inspectors had no consistent way to check whether a car's pollution controls were working.

The Environmental Protection Agency and the Society of Automotive Engineers solved this by mandating a single standard: On Board Diagnostics, second generation, or OBD2. Every gasoline vehicle sold in the United States from the 1996 model year forward must implement it, and the European Union followed with its own equivalent, EOBD, starting in 2001 for gasoline and 2003 to 2004 for diesel.

What does the standard actually require

OBD2 does not standardize how a car's computer works internally. Each manufacturer still writes its own engine control software and wires its own sensors. What OBD2 standardizes is the interface: the physical connector shape and pin layout, the electrical signaling protocol, the trouble code numbering format, and a defined list of data values called parameter IDs, or PIDs, that any compliant scan tool can request.

That is why a fifteen dollar generic code reader can pull a P0301 misfire code from a Honda, a Ford and a Chevrolet alike. The code format is shared even when the underlying fix is completely different on each platform.

• A single 16 pin connector, typically within reach of the driver's seat
• A shared trouble code format: one letter, four digits, for example P0301
• A required list of monitored emissions systems, called readiness monitors
• A defined set of live data PIDs every vehicle must expose
• Mode 6 test results for internal component self tests

How the car's computer decides to set a code

The powertrain control module, or PCM, continuously compares sensor readings against expected ranges. When a reading falls outside those ranges for long enough, and often only after the failure repeats across more than one drive cycle, the PCM stores a diagnostic trouble code, records a freeze frame snapshot of conditions at that moment, and in most cases lights the malfunction indicator lamp, the check engine light, on the dashboard.

This is a threshold and pattern based system, not an instant trigger. A single momentary glitch usually will not set a code. A repeatable fault that the PCM sees across a defined number of trips will.

Which protocol is actually running under the connector

Five electrical signaling protocols have been used under the OBD2 standard since 1996, and knowing which one a given vehicle uses explains why some scanners will not talk to some cars. Since 2008, every vehicle sold in the United States has been required to use Controller Area Network, or CAN, which is why virtually every scanner made in the last decade only needs to support CAN to cover the modern fleet.

What a scan tool is actually doing when it plugs in

A scan tool is a translator, not a diagnostic brain. It sends a request over the connector asking the PCM for stored codes, live data or test results, the PCM answers in the standardized format, and the tool decodes that answer into readable text. The tool did not diagnose anything on its own. It only retrieved information the car's computer had already recorded.

This matters because two different scanners reading the same car will report the same underlying data. Differences you see between tools are almost always differences in how much of that data each tool chooses to display, not differences in what the car is telling them.