Before Clearing A Truck Fault Code

What Clearing a Code Erases

Code clearing removes fault codes from the ECM's active and stored fault registers. Depending on the ECM calibration, it may also reset the freeze-frame data (the parameter snapshot captured at the moment the fault set), fault occurrence counters, and some accumulated counters related to the fault. Not all of this data can be recovered after clearing — the freeze-frame is particularly valuable for intermittent faults, where the conditions at the moment of occurrence may not be reproducible.

On aftertreatment-equipped engines, clearing fault codes does not necessarily reset inducement distance counters. Cummins and Detroit calibrations maintain separate counters for accumulated inducement distance that may persist after a code clear. A technician who expects the inducement counter to be at zero after a code clear may be surprised when the inducement sequence resumes from its pre-clear position. Reading the inducement counter status before clearing provides a complete baseline.

Information To Capture Before Clearing

Before clearing any fault codes, capture a complete record of: all active fault codes with SPN, FMI, and source address; all inactive (stored) fault codes with the same detail; any freeze-frame data visible in the OEM diagnostic tool; the current inducement counter status if the vehicle has an aftertreatment system; and the ECM's total fault occurrence counts if visible. A screenshot from the diagnostic tool display is the most efficient way to capture this complete record.

On vehicles with fleet telematics, the telematics system may have already captured some fault data — but telematics systems often capture only broadcast SPN/FMI without freeze-frame, occurrence counts, or inducement status. A diagnostic tool reading is more complete and should be the basis for the pre-clear record.

Situations Where Clearing Before Diagnosis Is Harmful

Clearing codes at a customer's request before diagnosis is complete removes the diagnostic baseline. A vehicle that arrives with three active aftertreatment codes, is cleared by the service advisor without a diagnostic read, and then produces different codes on the test drive has lost its original code set — the diagnostic history that showed how the fault developed is gone. This can result in a misdiagnosis or an extended diagnostic time.

Clearing codes to extinguish a warning lamp without repairing the cause is a temporary measure that addresses only the symptom. If the fault condition is still present, the code returns — usually within one or two drive cycles. For safety-relevant systems (ABS, oil pressure, coolant temperature), operating with the false assurance that a cleared code means the system is healthy is a misunderstanding that creates real risk.

When Code Clearing Is the Correct Next Step

Code clearing is appropriate after a confirmed repair, as part of the verification process. After replacing a faulty DEF quality sensor and refilling with certified DEF, clearing the DEF quality code and performing a test drive allows the technician to confirm that the repair resolved the fault. The code should not return on the verification drive. If it does, the repair was incomplete or the diagnosis was incorrect — either way, the return of the code after clearing is diagnostic information.

Code clearing is also appropriate as part of a scheduled maintenance review where codes have been fully documented and assessed. Many preventive maintenance programs include a fault code review at each PM interval — the technician reads, assesses, and documents all codes, addresses any that need repair, and clears the remainder after confirming they represent resolved or monitored conditions. This controlled clearing is different from uninformed clearing at driver request.

Related Pages

• Diagnostics
• Fault Code Lookup
• Methodology
• Disclaimer