Reading and Clearing Codes
Good habits for pulling codes, saving reports, clearing codes and verifying repairs.
Should I clear codes before I start diagnosing?
Short answer: No; save the codes and freeze frame first, because clearing them erases the data that shows what conditions set the fault.
Clearing codes right away is one of the most common mistakes in the bay. When you clear, you lose freeze frame data, reset the readiness monitors, and may erase pending codes that would have pointed you to the real problem. If the fault is intermittent, you may not see it again for days.
The better habit: plug in, run a full-system scan, and save or print the report before you touch anything. Note every code in every module, plus freeze frame for the powertrain codes. Then start testing.
Clear codes after the repair, and use the clearing as part of your verification. Run the vehicle through the conditions recorded in freeze frame and confirm the code does not come back as pending. That saved pre-scan report also protects you if the customer later questions what was wrong when the car arrived.
Tools used for this job
Why should I do a full-system scan on every car?
Short answer: Codes in other modules often explain the engine code, reveal problems the customer did not mention, and document the car's condition before you work on it.
A check engine complaint might come with a U-code in the ABS module, a low-voltage code in the body computer, and a stored airbag fault. Those clues can completely change the diagnosis. A network communication problem or weak battery can set codes in a dozen modules at once, and looking at only the engine computer hides that pattern.
Full-system scans also make money honestly. You find the stored ABS fault before the customer asks why the light came on after you worked on the car, and you can quote it on the spot.
Finally, they protect you. A saved pre-scan shows what was already stored when the vehicle arrived, and a post-scan shows you left it clean. Most professional scan tools can scan all modules in a couple of minutes and save a health report you can attach to the repair order.
Tools used for this job
What is the difference between a pre-scan and a post-scan?
Short answer: A pre-scan records every code in every module before repairs, and a post-scan confirms the vehicle left with no new or unresolved faults.
Pre-scans and post-scans started as collision-repair practice, where many OEM position statements call for them, but they are good practice for any shop. The pre-scan captures the vehicle's condition at drop-off, including faults the customer never mentioned. It guides the repair plan and gives you documentation if something is questioned later.
The post-scan happens after the repair and after any calibrations. It confirms that the original codes are gone, that no new codes were set by unplugging modules or disturbing wiring, and that required calibrations completed.
Save both reports with the repair order. Many scan tools let you store them on the tool, email them, or print a PDF. Follow the vehicle maker's position statements and your insurer's requirements for collision work, since those may set specific rules.
Tools used for this job
Why does the check engine light come back after I clear codes?
Short answer: Because the fault is still there; clearing codes only erases the record, and the computer sets the code again once the self-test fails again.
Clearing codes is not a repair. It wipes the stored code, the freeze frame and the readiness status, and the computer starts its self-tests over. If the condition that caused the code still exists, the test will fail again, often within one or two drive cycles, and the light returns.
Sometimes the light stays off for days because the monitor that catches the fault only runs under specific conditions, such as a cold start followed by a steady highway cruise for an EVAP test. That can make a customer think the problem went away.
Use that behavior to verify repairs instead. After fixing the fault, clear the codes, then drive under the conditions shown in freeze frame or in the drive cycle procedure and check for pending codes and completed monitors. If a pending code returns, keep diagnosing.
Tools used for this job
Can disconnecting the battery clear trouble codes?
Short answer: On many vehicles it erases stored codes and resets learned values, but it does not clear permanent codes and can cause new problems, so use a scan tool instead.
Pulling the battery cable removes power from the computer's memory on many vehicles, so confirmed codes and freeze frame can disappear. It is a poor way to clear codes. It resets readiness monitors and learned values such as idle, fuel trims and transmission shift adaptations, so the car may drive oddly for a while.
On newer vehicles, disconnecting power can also require relearns for windows, sunroofs, steering angle sensors and throttle bodies, and some radios or modules need codes or setup. Battery-registration vehicles may log the event. Permanent codes stay stored regardless.
A scan tool clears codes cleanly while keeping you informed. If you do disconnect the battery for a repair, use a memory saver where appropriate, keep the key and doors handled per the service procedure, and plan for any relearns afterward.
Tools used for this job
General guidance only. Follow the vehicle and tool manufacturer's procedures, and confirm vehicle coverage on the tool maker's list before buying.