In short
- A diagnostic scan reads the fault memory of a car's control modules, revealing problems the dashboard does not show.
- It captures stored, pending and often recently cleared faults across the engine, gearbox, ABS, airbags and more.
- Readiness monitors that have all reset are a strong sign the fault memory was wiped shortly before the viewing.
- A scan is powerful but not complete on its own, which is why our inspection in Budapest pairs it with a physical and road check.
A diagnostic scan is one of the most useful tools an inspector carries, but it is widely misunderstood - both by buyers who think it reveals nothing and by those who think it reveals everything. In truth it sits somewhere between the two. Reading a modern car's electronic fault memory exposes problems that never reach the dashboard, records a history that a seller cannot easily erase without leaving traces, and points a physical inspection towards the areas that deserve the closest attention. It also has real limits, which is why it belongs alongside a hands-on assessment rather than in place of one. This guide explains what an OBD scan actually reads on a used car, how to interpret what it finds, and where its boundaries lie.
What on-board diagnostics actually are
Every modern car is a network of electronic control modules - for the engine, the gearbox, the ABS and stability system, the airbags, the climate control and much more - and each of them monitors itself and records faults. On-board diagnostics, or OBD, is the standardised way of talking to those modules through a socket usually found under the dashboard. A scan tool connects there and asks each module what it has stored.
The result is a list of fault codes, each pointing to a particular circuit or condition, together with supporting data such as how often a fault has occurred and, on many systems, the conditions when it last happened. Read properly, this is a rich picture of a car's electronic health that no amount of looking and listening could produce. Read carelessly, it is a list of codes that can mislead as easily as inform, which is why interpretation matters as much as the reading itself.
Stored, pending and cleared faults
Not all fault codes mean the same thing, and part of a competent scan is telling them apart rather than reciting a list.
Stored and active faults
A stored fault is one the module has logged and, in many cases, is illuminating a warning light for. These are the current problems: a misfire, a sensor out of range, a system that has failed its self-check. They are the codes that most directly describe what is wrong with the car today, and they anchor the rest of the inspection.
Pending and intermittent faults
A pending code marks a fault the module has seen but not yet confirmed often enough to trigger a warning. These are valuable because they reveal problems before they become obvious - an intermittent misfire, a sensor beginning to drift - giving a buyer early warning of trouble that a test drive would not surface.
The trace of recently cleared codes
Perhaps most telling of all is evidence that the memory has been wiped. Many systems record whether faults have been cleared and reset their readiness monitors when they are, so a car whose monitors have all reset to incomplete has very likely had its codes erased recently - often just before a sale.
Why readiness monitors matter to a buyer
Readiness monitors are self-tests that a car runs on its emissions and engine systems over normal driving, and each one reports complete once the car has confirmed that part of the system is working. Crucially, clearing the fault memory resets them all to incomplete, and they only return to complete after the car has been driven through a full range of conditions.
For a buyer this is quietly powerful. A car presented for sale with all its readiness monitors reset is either freshly repaired or, more often, has had its fault memory cleared shortly before the viewing to hide a warning that would otherwise be showing. Neither is proof of a serious problem, but both are a reason to look harder and to treat a suspiciously clean dashboard with appropriate scepticism.
The limits of a diagnostic scan
A scan is not a complete verdict, and a good inspector is candid about that. It reads faults the systems have detected, but many important things are not monitored electronically: the condition of the bodywork, corrosion, the state of the tyres and brakes, worn suspension joints, oil leaks, and the quality of past accident repair all sit outside its reach. A car can return a clean scan and still have serious mechanical or structural problems.
There are also faults that live between the codes - a slipping automatic that has not yet logged a fault, an engine using oil, a noise that points to a bearing. This is precisely why a scan supports a physical and road inspection rather than replacing it. The codes tell you where the electronics have noticed trouble; the hands-on checks tell you about everything the electronics cannot see.
Making sense of the codes rather than fearing them
A single fault code is not automatically a disaster, and the instinct to reject any car that shows one is as mistaken as the instinct to ignore them. Codes vary from the trivial - a fault logged years ago and long since fixed - to the serious. What matters is understanding what a code means for the specific car: whether it is current or historic, cheap or expensive, isolated or part of a pattern.
This interpretation is where experience counts. The same code can be a minor annoyance on one model and a symptom of a known expensive fault on another. Rather than handing a buyer a raw printout, the value is in explaining what the findings mean, which are worth acting on, and how they should shape the price or the decision. A scan is a starting point for judgement, not a substitute for it.
How we use a diagnostic scan during an inspection in Budapest
In our inspection the scan is one tool among several, used to read every accessible module rather than the engine alone. We note stored and pending faults, check the readiness monitors for signs of a recently cleared memory, and use what we find to guide the physical checks - a misfire code sends us to the ignition and compression, an ABS code to the sensors, and so on.
We then set the results out in plain English, separating the trivial from the significant and explaining what each meaningful finding is likely to cost. For a buyer purchasing remotely, this combination of an electronic read and a hands-on assessment is exactly what a quick viewing cannot provide, and it is one of the clearest reasons to have an independent inspection before committing to a Hungarian used car.
Cars we inspect related to this guide
Browsing one of these? Open its inspection page to see the model-specific checks and book an on-the-spot pre purchase inspection in Budapest.
Frequently asked questions
Does a diagnostic scan show every problem with a used car?
No, and any inspector who claims it does is overselling it. A scan reads faults the electronic systems have detected, but corrosion, tyres, brakes, worn suspension joints, oil leaks and poor accident repair are not monitored electronically. A car can pass a scan cleanly and still hide serious mechanical or structural problems. That is why we pair the scan with a physical and road inspection rather than relying on it alone.
Can a seller clear fault codes before I view a car?
Yes, and it takes only seconds with a basic tool. However, clearing the memory also resets the car's readiness monitors to incomplete, and they only return to complete after a full range of driving. A car with all its monitors reset has very likely had its codes wiped recently, which is a reason to look harder. We check the monitors during the scan precisely to catch this.
Is one fault code a reason to reject a used car?
Not by itself. Fault codes range from the trivial - something logged long ago and since repaired - to the serious, and the same code can mean very different things on different models. What matters is whether it is current or historic, cheap or expensive, isolated or part of a pattern. We interpret each meaningful code and explain what it means for the specific car rather than treating any code as a deal-breaker.
What is a pending fault code?
It is a fault the control module has seen but not yet confirmed often enough to trigger a warning light. Pending codes are valuable because they reveal problems early - an intermittent misfire or a sensor beginning to drift - before they become obvious on a test drive. We read pending as well as stored codes so you get early warning of faults that are developing but not yet showing on the dashboard.
Do you scan systems other than the engine?
Yes. Where the car allows it, we read every accessible control module - engine, gearbox, ABS and stability control, airbags, climate and body electronics - because faults in those systems matter just as much and are just as easily hidden. A read limited to the engine misses a great deal. Scanning the whole car is part of giving you a complete picture of its electronic health.
Found the car? Get it checked.
Before you pay, book an independent, English-speaking inspection in Budapest. We come to the car and report in English - 35 999 Ft or 39 999 Ft with photos and video.
