Fault codes: how to prepare for diagnosis
A fault code is information for further diagnosis, not a finished diagnosis or proof that a part needs replacing. This guide helps you prepare for a service enquiry; it does not replace the instructions for your specific vehicle or machine.
In this guide
- Identify the vehicle and control unit first
- Save the evidence before clearing codes
- Why is the number alone not enough?
- Clearing a fault code is not a repair
Identify the vehicle and control unit first
Record the make, exact model, year, engine designation and control unit reporting the fault. Match the documentation to the correct serial number and equipment version. A table for another engine or generation does not establish what the code means on your machine.
Save the evidence before clearing codes
Record the full message and complete code, including any additional identifiers. Keep the diagnostic report and whether the fault is active or stored. Note when it appeared, the symptoms you observed and recent repairs. Share VINs and serial numbers privately with service staff.
Why is the number alone not enough?
Keep any module prefix, leading zeros and additional SPN/FMI fields shown by the diagnostic tool. Do not treat a DTC, an SPN and a manufacturer code as interchangeable identifiers. Matching a description requires the control-unit context and suitable documentation; a description alone does not prove the cause.
Clearing a fault code is not a repair
Deleting a record does not repair a defect. If the warning returns, keep a new report and the circumstances instead of repeatedly clearing codes. Follow the operator manual and STOP warnings. This guide is not permission to keep driving, force a regeneration or bypass safety or emissions systems.
Manufacturer documentation: a starting point
These links lead to manufacturer documentation; they do not validate any third-party code table for your machine.