What an OBD2 Scanner Can and Cannot Tell You

Some links on this page are affiliate links. If you buy through them, OBD Dynamics may earn a commission at no extra cost to you. It helps keep the lights on and the advice honest.

A scan tool is the single most useful thing you can put in a toolbox, and it is also the most commonly misunderstood. The misunderstanding is always the same one: people expect it to tell them which part to replace. It does not do that, and knowing what it does do instead is what turns it from a gadget into a diagnostic instrument.

Reading a fault code properly

A diagnostic trouble code is five characters, and each position means something specific.

• The letter tells you which system. P is powertrain (engine and transmission), B is body, C is chassis, and U is network or communication between modules.
• The first digit tells you who defined the code. 0 means it is a generic code standardised across manufacturers. 1 means it is manufacturer-specific, and you will need manufacturer-level information to interpret it fully.
• The remaining digits identify the subsystem and the specific fault.

The critical point: a code describes a circuit, not a component

This is where most money gets wasted. A code reporting a fault in an oxygen sensor circuit does not mean the oxygen sensor is faulty. It means the module saw a reading from that circuit that was outside what it expected. That could be the sensor — or it could be the wiring, a connector full of corrosion, a bad earth, a vacuum leak upstream, a failing fuel component, or the module itself. Replacing the named part without further testing works often enough to be seductive and fails often enough to be expensive.

The correct sequence is always: read the code, understand what the code actually means, then test to confirm which part of that circuit is at fault.

Freeze frame is the underrated feature

When a fault is stored, most systems also capture a snapshot of what the engine was doing at that moment — engine speed, load, coolant temperature, vehicle speed, fuel trim and other parameters. This is enormously valuable, because it tells you the conditions the fault occurs under. A fault that appears at cold start and low load is a different investigation to one that appears hot at motorway speed, even with the same code stored.

Live data is where the real diagnosis happens

Reading stored codes is the beginning; watching live data is the actual work. With the engine running you can watch sensor values in real time, compare them against what they should be, and see how they respond when you change something.

1. Compare sensors that should agree. Two sensors measuring related things that disagree tell you a great deal.
2. Watch fuel trims. They show how much the engine management is having to correct, and in which direction, which points at unmetered air or a fuel delivery problem long before a code appears.
3. Wiggle the wiring while watching the value. An intermittent connection shows up instantly as a spike or a dropout.
4. Graph it rather than reading numbers. Patterns are visible in a graph that are invisible in a scrolling list.
5. Record a drive. For an intermittent fault, logging live data while the fault occurs is often the only way to catch it.

Pending codes and permanent codes

• Stored codes have met the criteria to set a fault and usually a warning light.
• Pending codes have been seen once but not yet confirmed. They are an early warning and worth paying attention to.
• Permanent codes cannot be cleared with a scan tool at all — they clear themselves only once the vehicle has confirmed the fault is genuinely gone. They exist precisely to stop people from erasing a problem instead of fixing it.

What clearing codes actually does

It turns the light off. It does not repair anything, and it destroys information you may need — the freeze frame goes with it, and the readiness monitors reset, meaning the vehicle has to complete its self-tests again before those systems report as ready. Read and record everything before you clear. If the fault is still present, the code will return, usually within a drive cycle or two.

What a scanner cannot tell you

• Mechanical condition. Compression, timing, worn bushes and a slipping clutch are not on the network.
• Whether a part is good. Only that a circuit is reading out of range.
• Faults in systems that do not report. Older or non-electronic systems have nothing to say.
• What to do about it. That is diagnosis, and it still requires a person, a wiring diagram and a multimeter.

A scan tool narrows an entire vehicle down to a system and a circuit in about two minutes. That is worth an enormous amount — it just is not the same thing as an answer.

Tools mentioned in this guide

A full-system scanner reads every module, not just the engine. These are the tools we would start with.