Dashboard Warnings

OBD-II code readers vs garage diagnostics: what a home scanner can and can't tell you

Guides4 min read20 October 2026

By · Published · Updated

How plug-in OBD code readers work, what the fault codes mean, where they fall short of professional diagnostics, and how to use one sensibly.

When the engine management light comes on, a plug-in code reader can tell you in a minute what the car's computer has logged. That is genuinely useful, but a fault code is a clue, not a diagnosis. This guide explains how the system works, what a cheap reader can and cannot do, and when it is worth paying a garage.

What OBD is?

On-board diagnostics (OBD) is the self-monitoring system built into modern cars. In Europe the standard is known as EOBD, and it has been required on new petrol cars since 2001 and new diesel cars since 2004. Every compliant car has a standard 16-pin socket, usually under the dashboard on the driver's side, within reach of the steering column. Your handbook shows where it is.

When a sensor reports a value outside its expected range, the engine control unit stores a diagnostic trouble code (DTC) and, if the fault affects emissions, switches on the engine management light.

Reading a fault code

Codes are five characters, for example P0301:

What a home code reader does well?

Basic readers, including small Bluetooth adapters that pair with a phone app, are inexpensive. Generic readers mostly cover engine (P) codes.

Where a basic reader falls short?

Don't just clear the code

Most readers can clear codes and switch the light off. If the fault is still there, the light will return, and in the meantime you have lost the stored information a mechanic would have used. Clearing the light just before an MOT does not fix anything, and selling a car having hidden a known fault can leave you in trouble. Note the code, and any freeze-frame data, before you clear it.

A sensible way to use one: step by step

  1. With the ignition off, plug the reader into the OBD socket.
  2. Turn the ignition on (engine off unless the reader's instructions say otherwise) and read the stored codes.
  3. Write down every code, including "pending" ones, and save the freeze-frame data.
  4. Look the code up for your make and model, but treat forum answers as possibilities, not facts.
  5. Do the simple, safe checks: fuel cap tight, connectors seated, no obvious split hoses.
  6. If the fault is not obvious, or concerns brakes, airbags or steering, take it to a garage and give them the codes.

When to go straight to a garage?

When you get a quote, ask what the diagnosis includes: just reading codes, or testing to find the cause. A good garage will explain how it reached the conclusion.

Frequently asked questions

Will a code reader damage my car?

Reading codes is passive and safe. Be more careful with advanced tools that can change settings or code modules.

Does the MOT test plug into the OBD port?

The MOT checks the warning lamps themselves and the car's emissions. An illuminated engine management light has been a major defect since May 2018.

Does my electric car have OBD?

Most do have a diagnostic socket, but many EV faults use manufacturer-specific codes that generic readers cannot interpret.

Sources and further reading

Facts checked on 20 October 2026. Spotted an error? Tell us and we will correct it.

Get the next guide first

New articles land every week. Follow along by RSS or bookmark the homepage.

Follow by RSS