Understanding OBD diagnostics – reading codes and placing them in context
A fault code is quickly read out. The harder question is what it actually means: OBD diagnostics is a standardised way into the vehicle, and that access has a clearly defined scope. Once you know what the standard covers and what it does not, you read an entry far more cautiously – and replace a component that was never the cause far less often.
This page explains what lies behind the diagnostic socket, how a fault code is built up, and where the limits of the standardised scope run. If you already have your codes and want an independent assessment: MotorScope assesses your diagnostic data and delivers an analysis report usually within one hour of complete data arriving – around the clock, at night and at weekends too.
Have your diagnostic data checked
When a look at the OBD data is worthwhile
OBD diagnostics is not an end in itself. It makes sense when there is a concrete question behind it.
-
The engine warning light is on and you want to know whether you have to act immediately.
-
You have read out a code and find five contradictory explanations for it online.
-
Before the garage visit you want to know what you are actually talking about.
-
A cost estimate names a component and you want to check whether the code really supports that.
-
Before buying a used car you want to see the fault memory and the readiness status.
-
Before the MOT and emissions test you want to be sure that no open entry and no unfinished readiness status stands in the way.
-
A fault has returned after a repair and you want to compare the old and the new entry.
-
You look after several vehicles and want to sort entries before a budget is approved.
Safety first. If the engine warning light is flashing, if there is a severe loss of power, smoke, a smell of fuel, unusual noises, or anything unusual about the brakes or steering, do not keep driving the vehicle. Have it checked on site first – a data analysis is no substitute for an inspection of the vehicle.
What OBD-2 is – and where the standard ends
OBD stands for on-board diagnostics: the vehicle monitors itself while driving and files irregularities in a fault memory. What matters for understanding it is where the standard comes from – not from workshop diagnostics but from emissions law.
Why OBD-2 exists at all
The standard was introduced to make a vehicle’s emissions-related monitoring uniform and verifiable from outside. What is monitored is therefore first of all whatever affects emissions: mixture formation, combustion, exhaust after-treatment and the associated sensors. In the EU the European variant EOBD applies; it has been mandatory for new passenger cars with petrol engines since 2001 and with diesel engines since 2004. Older vehicles may have a diagnostic socket without providing the full standardised scope.
The diagnostic socket
Standardised access is through a 16-pin diagnostic socket. As a rule it sits in the cabin on the driver’s side and is reachable from the driver’s seat – often below the steering column, behind a cover in the footwell or in the centre console. The exact position differs from vehicle to vehicle; the handbook usually gives it.
Standardised and manufacturer-specific diagnostics
This is the central distinction – and the most common source of misunderstandings.
Standardised diagnostics means: a particular, emissions-related set of data must be retrievable in the same way on every vehicle. That is why a standard device works across brands. This scope is limited to emissions-related monitoring of the powertrain; whether and how far transmission data is reachable through it differs from vehicle to vehicle. It covers only what the standard provides for.
Manufacturer-specific diagnostics means: everything beyond that. The manufacturer’s own fault codes, more finely resolved readings, actuator tests, basic settings, adaptation procedures and access to control units that have nothing to do with emissions behaviour. That requires appropriate diagnostic equipment and matching software coverage for the vehicle in question.
The line therefore does not run between “engine” and “the rest” but between standardised emissions diagnostics and manufacturer-specific vehicle diagnostics. Which route leads to which scope of data, and what that means in practice, is described under online vehicle diagnostics.
What the standardised scope offers: the services (modes)
Standardised access is divided into individual services, often called “modes”. In plain language these are essentially:
ServiceWhat lies behind it
Stored fault codesEntries that led to the engine warning light coming on
Pending fault codesIrregularities that have occurred once and still have to be confirmed
Freeze frame dataSnapshot of the operating values at the moment of storage
Live datacontinuously updated readings from operation
Readiness statusInformation on which self-tests have been completed since the last clearing
Results of individual monitorsReadings from the internal test routines
Vehicle informationamong other things the VIN, where the vehicle provides it
Clearing the memoryclears entries, freeze frame data and the readiness status
Not every vehicle and not every piece of software provides all services in full. For an assessment what counts in the end is not how many services a device supports but what is actually in the export.
Readiness code: the point that counts before the emissions test
The readiness status shows which of the internal monitors the vehicle has completed since the memory was last cleared. Some of these self-tests only run under certain conditions – a cold start, particular engine speed and load ranges, a certain distance driven. That is why it takes a few journeys after clearing before the status is complete again.
In practice this means: clearing the fault memory shortly before the emissions test usually leads to the incomplete readiness status being noticed during the test. It raises exactly the question that was meant to be avoided. The same applies when buying a used car: a freshly cleared memory with an unfinished readiness status is not a neutral finding.
Clearing is not a repair. It removes the entry, not the cause – and with the entry go the freeze frame data and the readiness status, exactly the information from which a connection could later be reconstructed.
How a fault code is built up
A fault code is not a random string of characters. It has five positions, and each position carries meaning.
The first letter: which area
LetterArea
PPowertrain – engine, mixture, exhaust, drivetrain
BBody – interior and comfort environment
CChassis – brakes, steering, vehicle dynamics
UNetwork – communication between control units
The second position: standardised or manufacturer-specific
A 0 or a 2 in the second position stands for the standardised range, a 1 for a manufacturer-specific code; with a 3 both occur. Standardised means the code means the same thing across vehicles. With a manufacturer-specific code the manufacturer defines the meaning, and without their documentation it cannot be determined reliably. That is why code lists from the internet so often produce contradictory hits for manufacturer-specific entries.
The remaining positions: system and serial number
The third position narrows down the system affected; the last two name the specific irregularity within that system.
An example, position by position
An example: the entry P0171.
P – the entry comes from the powertrain area.
0 – the code belongs to the standardised scope and means the same across vehicles.
1 – this narrows the area further, here the environment of mixture preparation and air measurement.
71 – the specific irregularity within that area: the mixture was persistently too lean, and the system had to correct towards “richer” over a longer period.
And now the decisive point: the code says that the mixture had to be corrected persistently. It does not say why. Unmetered air at a seal or a hose connection, a measurement error in the air mass sensing, insufficient fuel pressure, a leak in the exhaust path ahead of the sensor – all of these can lead to the same entry. Anyone who replaces a component on the strength of the code alone is very probably replacing on suspicion. How to get from such an entry to a solid conclusion is described on the page about fault diagnosis.
Fault status: static, sporadic, pending
The status always belongs with the code. It often decides more about the assessment than the code itself.
Static means: the condition is currently present. The fault is there at the read-out and can therefore most readily be checked reproducibly.
Sporadic means: the condition was present but is not present now. The entry stays stored.
Pending means: the irregularity has occurred but has not yet been confirmed. Some monitors only store permanently once the behaviour occurs again in a further driving cycle.
The status describes the moment of the read-out, not the weight of the entry. That a condition is not present right now does not make it harmless: contact resistance, chafed wiring, loose connectors, temperature effects and voltage drops almost always report themselves this way. They are the reason a fault cannot be reproduced at the test appointment and returns after an apparently successful repair. That is why the status belongs in the export with every entry – together with the freeze frame data that supplies the condition.
The order in which symptom, fault memory, freeze frame data and live data are assessed is described on the page about how fault diagnosis on a car proceeds methodically.
What OBD diagnostics does not say
For the data to be weighted correctly, the other direction belongs here too: four things the standard fundamentally does not do.
A code names a deviation, not a culprit
An entry describes which monitor responded and in which direction the value departed from what was expected. Whether the cause is the reported component itself, its wiring, its supply or a quite different effect further up the chain does not follow from the code alone. A reported sensor is more often the messenger than the offender.
The standardised scope does not cover the whole vehicle
Emissions-related monitoring is the core of the standard. Chassis, body, comfort and assistance systems lie outside that core and are not reachable through standardised access, or only in part. An empty memory within the standardised scope therefore does not mean that no entry exists in any control unit of the vehicle.
A cleared memory destroys the history
Clearing removes entries, freeze frame data and the readiness status. That leaves out exactly what otherwise produces a connection over time: when the fault first occurred, under which operating conditions, how often, and whether the same or a different entry returned after a repair. If clearing took place shortly before the read-out, that should be stated with the data.
Complete readiness does not mean “vehicle in order”
A complete readiness status says that the internal self-tests have run through. It says nothing about wear, mechanical condition, leaks below the response threshold, or systems outside the monitored scope. The reverse applies as well: a vehicle can behave noticeably oddly without any entry in the memory – live data and the description of the symptom are then more important than the fault memory.
OBD diagnostics is therefore a good starting point and a poor finishing point. It provides clues that have to be ordered and compared with how the vehicle actually behaves. That comparison is exactly what the online assessment consists of – location-independent as remote car diagnostics, and on request with the data taken at the vehicle.
What data the assessment needs
Required
Vehicle data: VIN (17 characters; the letters I, O and Q do not appear in it), model, engine, year of manufacture and mileage.
Description of the symptom: when the behaviour occurs – right after starting, under load, on the motorway, with a cold engine or only after a longer drive. Since when, how often, under which conditions.
Diagnostic data: diagnostic tester export, fault memory print-out or app export with control unit, fault code and fault status.
Helpful, if available
-
Freeze frame data with engine speed, coolant temperature, engine load or vehicle speed.
-
Live data and target/actual comparisons.
-
The readiness status, if the software reports it.
-
Screenshots from an OBD app and photos of the warning lights.
-
Invoices for work already carried out and a list of replaced parts.
-
Any indication that the fault memory was cleared, that the battery was weak or that a connector was recently disconnected.
How to make your data usable — Send the complete log wherever possible rather than a code typed out by hand. Screenshots only help if every value is legible and not just the top line of the screen is shown. Photos should be sharp and show the entry in full. A special diagnostic tester is not a requirement – existing print-outs, photos or app exports are often enough, provided the fault description is meaningful.
How the analysis works
-
Describe the problem — Give the vehicle model, engine, year of manufacture and mileage – and describe when the symptom occurs.
-
Send the data — Upload fault codes, diagnostic logs, freeze frame data or screenshots through the form.
-
Assess the connections — MotorScope compares the data with the symptoms you described and the work carried out so far.
-
Receive the analysis report — Usually within one hour of complete data arriving, you receive your analysis report with a traceable assessment and a prioritised list of possible checks.
What the assessment costs, and the terms that apply if the data is taken at the vehicle, is described under online vehicle diagnostics.
What the online assessment does – and what it does not
What the online assessment does
-
Puts fault memory, live data and symptoms into context
-
Shows which measurement is most likely to bring clarity next
-
Makes a repair recommendation verifiable before you approve it
-
Prepares the garage visit with a clear question
-
Is independent of repair orders and parts sales
What it does not do
-
Repairs and parts sales
-
Approving repairs or certifying roadworthiness
-
Replacing a personal inspection of the vehicle
-
Swapping parts on suspicion, or a guarantee of success
-
Replacing the German MOT (HU), the emissions test (AU) or any other legally required inspection
If the data does not show a clear picture, the report says so explicitly. Rather than settling on a cause prematurely, it shows which check will bring the most clarity next.
Frequently asked questions about OBD diagnostics
Where do I find the diagnostic socket?
As a rule in the cabin on the driver’s side and reachable from the driver’s seat – often below the steering column, behind a cover in the footwell or in the centre console. The exact position differs from vehicle to vehicle and is usually given in the handbook.
Does every car have OBD-2?
No. For new passenger cars in the EU the European variant EOBD has been mandatory for petrol engines since 2001 and for diesel engines since 2004. Older vehicles may have a diagnostic socket without providing the full standardised scope – how far you get shows at the read-out.
Why do I find contradictory explanations for my code?
Because many lists mix standardised and manufacturer-specific codes. If the second position is a 1 – and depending on the code also with a 3 – the meaning is manufacturer-dependent and cannot be derived reliably from a general list. And even with standardised codes, the entry describes a deviation, not its cause.
The fault is gone after I cleared the memory. Is the problem fixed?
Not necessarily. What has been cleared is the entry. If the condition occurs again, the code returns – but until then you are missing the freeze frame data, the readiness status and the history that would have been useful for the assessment.
Is there any point in clearing the fault memory shortly before the emissions test?
MotorScope advises against it. After clearing, the readiness status is incomplete until the internal self-tests have run through again – and that is noticed during the test. It makes more sense to place the cause in context beforehand.
What does the status “sporadic” say about urgency?
On its own, nothing: it only records that the condition was not present at the moment of the read-out. Contact resistance, chafed wiring and voltage drops show up almost exclusively this way. What counts for the assessment is therefore the combination of status and freeze frame data – both belong in the export.
Is an adapter from the internet enough to see every fault?
For the standardised, emissions-related scope, often yes. Manufacturer-specific codes and control units outside that scope are mostly not reachable through it, or only in part. Which routes lead to which scope of data is set out under online vehicle diagnostics. MotorScope does not sell diagnostic equipment and does not recommend buying any particular model or app.
Does the vehicle have to be presented for the assessment?
Not for the assessment – the data has to be read out and sent once. That is the basic idea of remote car diagnostics: the analysis report is produced independently of location, with no ties to any garage.
You will find further answers under All questions and answers.
Understand the data first. Then act with purpose.
Upload your diagnostic data and receive an independent assessment usually within one hour – before you order the next part.