No code. Yet there is a symptom.
The absence of a fault code does not rule out a problem. The scope of the scan and the conditions in which the symptom occurs matter.
Diagnosis continues with context: observation, testing, then confirmation.
01 · Understand the scan
Three situations to distinguish.
Before looking for a faulty component, check what the result actually tells you.
No scan performed
The warning light is off, but no tool has scanned the vehicle. Record ‘codes not read’.
A dashboard without warnings is not a fault-code report.
A limited scan
The tool scanned the engine or only some of the control modules.
Keep the tool name, the systems scanned and any communication failures.
No codes recorded
The modules scanned return no codes at the time of the scan.
Record the date, the scope and any recent code clearing. The symptom still needs investigation.
Keep the complete report, including the displayed statuses. ‘No codes found’ always relates to a particular tool, scope and moment.
Understand fault code statuses02 · Prepare the case file
Five parts of your case file.
Describe what you observed. If information is missing, simply write ‘unknown’.
The exact vehicle
Make, model, year, engine, fuel type, transmission and mileage. An uncertain specification still needs confirmation.
The symptom, in your own words
Jerking, noise, vibration, stalling, difficult starting… Where do you feel it? When did it start? How often does it happen?
The conditions in which it occurs
Cold or warm engine, idling or driving, accelerating or decelerating. Include conditions already observed, without provoking the fault.
What changed recently
Servicing, repairs, battery replacement, fuel, an impact or a long period off the road. Record the sequence of events and the effect observed.
Reports and checks already available
Diagnostic report, tool used, modules scanned, readings with their units and measurement conditions. A missing measurement stays missing; a replaced part does not prove the cause.
03 · Turn an impression into a description
An observation a professional can use.
Fictional scenario, with no customer case.
‘The car jerks when warm, during acceleration. I do not feel it at idle. I scanned only the engine control module with a consumer code reader: no codes displayed. I have no live data. The problem started before the last service.’
Still to add: vehicle details, exact tool, scan date, frequency and a detailed history.
Describe what was observed. Observation, testing and confirmation are three different stages.
04 · Two practical examples
Two symptoms, two approaches.
These technical examples are educational. They illustrate an approach and do not establish a diagnosis for another vehicle.
Jerking under acceleration
On a BMW 116i F20 with the N13 engine, model years 2011 to 2015, jerking under heavy load may occur with brief drops in power, without an engine warning light or a relevant stored code.
Diagnosis may then require examination of the available parameters and ignition operation.
The professional selects suitable checks, then confirms or rules out possible causes on the vehicle.
A vibration that depends on load
A vibration felt during acceleration but absent during deceleration can persist even when a scan shows no fault codes.
Recording the exact conditions and taking vibration measurements helps locate the phenomenon.
Remember: an empty fault list does not identify a part to replace. The symptom, the conditions in which it occurs and appropriate checks guide the next steps.
Car will not start? Distinguish three situationsPrecautions
When should you leave it to a professional?
A warning or dangerous behaviour
Follow the handbook, particularly for STOP, brake, oil-pressure or temperature warnings.
The absence of a code does not establish that the vehicle is safe to drive.
A test or measurement is needed
Do not provoke heavy load to reproduce a fault. Never consult a diagnostic tool while driving.
Tests, measurements and repairs must be appropriate for the vehicle and carried out by a qualified person.
Consult the handbook for your own vehicle.
FAQ
Useful questions.
Can a car have a fault without a fault code?+
Yes. Jerking or vibration can occur without a relevant stored code. A missing code confirms neither that the vehicle is in good condition nor a specific cause.
Should I start by replacing a part?+
This guide does not identify a part to replace. The next step is to document the symptom and let a professional choose useful checks.
What should I provide if I do not have a diagnostic tool?+
Vehicle details, a precise description, the conditions in which the symptom occurs and the history. Record ‘codes not read’ and let the professional decide what scan is needed.
Where does Diagolia fit in?+
Diagolia helps organise information and explore possible causes. It complements diagnostic tools and the technician’s validation; it does not certify that a vehicle is safe to drive.
Clearer context. Better focused checks.
See how Diagolia works and prepare the details of your case.
3 free diagnoses