What Is Automotive Diagnostics? | Under The Hood, Explained

Automotive diagnostics is the onboard self-diagnosis and reporting system that lets repair tools read emission-related data through the OBD-II port.

For the full breakdown, see our best Auto Diagnostic Device guide.

When the check engine light glows, the car has already finished the first step of what automotive diagnostics really is: it detected a fault, logged a code, and saved the conditions around it. The second step happens when a scan tool plugs into the vehicle and asks for that data over a standardized port. In the U.S., that port and the language spoken through it trace back to OBD-II, required for 1996 and later model-year vehicles.

What Automotive Diagnostics Actually Covers

Automotive diagnostics is built around emission-related faults, not every subsystem in the car. The rules that define it require passenger cars and light- and medium-duty trucks to support a minimum set of diagnostic information that generic off-board test equipment can read — which is why an inexpensive code reader works on most vehicles without special dealer software.

Those diagnostic modes are why the check engine light finally means something. Instead of staring at a glowing icon, a driver can read the exact code behind it, look up what the code describes, and decide whether it’s a loose gas cap or a serious sensor failure.

That minimum set includes things like:

• Current sensor and monitor data, such as oxygen sensor readings and fuel system status
• Stored diagnostic trouble codes that indicate a detected fault
• Freeze-frame data, a snapshot of conditions when the fault was recorded
• Readiness status, which tells whether emissions monitors have run since the last code clear

None of this happens at random. The standards define diagnostic test modes and request/response messages that vehicle manufacturers and test tools must use, including rules for how a vehicle should behave when data isn’t available and timing requirements between a request and its response.

The practical payoff is real: emissions monitors run constantly, and the readiness information a scan tool reads is the same data states use to decide whether a vehicle passes an OBD-based smog check. That’s also why generic scan tools are so capable — the U.S. mandate guarantees access to this minimum set, so no manufacturer can lock the basic data behind a dealer-only tool.

How Does A Scanner Get The Data?

A scan tool asks, and the vehicle answers: automotive diagnostics runs on request/response messages exchanged over the vehicle’s data link, with the vehicle acting as the responder.

The original standard behind that exchange is SAE’s legacy J1979 standard, which SAE says was developed to meet U.S. OBD requirements for 1996 and later model-year vehicles. It covers the older data links found on many vehicles still on the road: SAE J1850, ISO 9141-2, ISO 14230-4, and ISO 15765-4.

A newer companion standard, SAE J1979-2, issued in 2021, defines the latest diagnostic services for OBDonUDS, the newer protocol used for emissions OBD, and extends coverage to heavy-duty trucks. Europe enters the picture through ISO 15031-5, which was based on J1979 and combined U.S. requirements with European OBD requirements for 2000 and later vehicles.

In practical terms, OBDonUDS does the same job as the older links but with a more modern protocol and faster communication. The companion J1979-DA digital annex publishes the updated data tables that define what each code and value means.