مسح الأكواد من وحدة دون الأخرى

Fault codes cleared in one module while a related module retains its own record, so the two now disagree about whether anything is wrong. It is a diagnostic artefact rather than a vehicle fault, and it wastes a great deal of time because the surviving code describes an event that has already been repaired.

It happens because clearing is not global. Many tools clear only the module currently addressed, and a generic tool may clear only emissions-related codes from the engine module while transmission, chassis and body modules keep theirs. So a stored code can be a historical record of something fixed weeks ago, still being reported by a module nobody re-addressed.

Freeze frame and status flags are what settle it. A code marked historical or passive, with a frame naming conditions the vehicle has not seen since, is old news; one marked current is live. Clear everything from every module and drive the vehicle, then read again — what comes back is real and what does not was residue. Do this before diagnosing, not after, since it costs minutes and removes the possibility of chasing a repaired fault.