What a scanner cannot see: the honest limits of OBD diagnostics

Scanners are often sold as a universal tool, and that does as much harm as distrusting them. It is more useful to know the limits: where a sensor exists, OBD is strong; where none exists, it is silent.

The rule in one line

A scanner sees what the car’s electronics see. No more and no less.

If a parameter is not measured by any sensor, it is not in the protocol — and no adapter can “extract” it.

What a scanner cannot see

Mechanical engine condition. Compression, ring condition, valve clearances. Indirect signs exist — misfire counters, trims — but a compression figure comes from a gauge, not an adapter.

Suspension condition. Play, bushes, dampers. You will see consequences in ABS data but not the component itself; indirect signs are covered in the dampers article.

Brake pad thickness — except on cars with wear sensors.

Bodywork and corrosion — no sensor for this exists at all; covered in the rust article.

Fluid leaks. You will see the consequence — a falling level or overheating — but not the location.

Tyre condition — except pressure where TPMS exists.

Routes and places driven — these are not in the diagnostic protocol; covered in the car data article.

What basic OBD specifically misses

A separate distinction that often gets confused.

The OBD-II standard guarantees access to systems affecting emissions: the engine and what surrounds it. That is the common minimum on every car.

Body electronics, ABS, airbags, transmission — those use manufacturer protocols. Access depends on make, model, and what the app supports.

So: “the scanner cannot see the airbag fault” sometimes means not a broken scanner but a module that answers on a different protocol; extended modes are covered in the Mode 22 article.

Where a scanner is irreplaceable

So the limits do not read as belittling.

Codes and freeze frames — the conditions a fault occurred under, which cannot otherwise be reconstructed.

Live parameters as a trend — invisible by any other means without equipment.

Commanded versus actual — rail pressure, boost, throttle position. The heart of modern diagnosis.

Counters and adaptations — a history that cannot be fabricated.

Post-repair verification — whether the code returns over a full cycle; covered in the post-repair verification article.

How to use it properly

A scanner narrows the search, it does not deliver a diagnosis. The code says “in this system”, live data says “in this component”, and hands and a ramp say “this part”.

Do not buy a part from a code. P0420 does not mean “buy a catalyst”: it means efficiency is below threshold, and there are several causes for that.

Combine: code, live data, inspection, and substitution testing.

In short

• A scanner sees exactly what the car’s electronics see.
• Compression, play, corrosion, and leak locations stay with your hands.
• Basic OBD-II is the emissions system; other modules depend on the make.
• The scanner’s strength is freeze frames, trends, and commanded versus actual.
• A code narrows the search; it does not name a part to buy.

Download the app — codes, freeze frames, and live parameters are read with an ELM327 adapter over Bluetooth SPP on Android.