How do I clear STORED Codes?





I can reliably clear these codes with either reader. But the next time I run diagnostics (with either reader), the same STORED codes are back.
Is there some step I am missing to erase these stored codes completely?
Last edited by DFWdude; Mar 18, 2024 at 08:35 PM.




I can reliably clear these codes with either reader. But the next time I run diagnostics (with either reader), the same STORED codes are back.
Is there some step I am missing to erase these stored codes completely?
Can you give us a screencap or better the complete pdf "report" to get whole network interactions.
Stored faults are not only historical but also transient codes... they are meaningful.
Become familiar with chassis reboot to sanitize SAM/CGW/ESP pilling up silent network errors.
There is a whole range of system uneasiness that is kept under wrap below the radar. The solderless bottleneck is the purveyor.
The more you peal off the onion, the cleaner it becomes.





I will capture a screenshot of the Gateway Module the next time I'm in there.
Would there be any problem doing a chassis reboot (I assume disconnect battery for 20 minutes)?
Last edited by DFWdude; Mar 18, 2024 at 09:15 PM.
And some days after, error code is back, it not current and only stored. That mean your system has an error. I guess that codes are communication or some messenger missing. It usually due to unstable voltage. So live with it because these errors are quite difficult to determine other than replacing good battery.




Mine was like that too. Not always, sometime.
It was giving some fault from Front SAM N10/1 , something to do with lights. I forgot the detail.
We can't expect Launch to be as good as Xentry recommended by BenzNinja.
That is why I have now 4 scanners and if important function I only trust the Xentry recommended by BenzNinja because I do not want to brick any module.
Trending Topics
What are the two codes you can't clear?
The Best of Mercedes & AMG
An example: prior to disabling auto start/stop with a recently acquired scanner, I disabled it by disconnecting the battery sensor. All but one scanner (the one I used to code off ***), never detected any DTCs. These 2 DTCs identified a faulty battery sensor, which being disconnected, was accurate. There was never any CEL, and because these codes were being detected at power up, they could never be cleared. After coding the *** off, I reconnected the sensor, cleared the codes and they now do not appear.





Can I clear these by disconnecting the battery for 20 minutes, or what?




These faults will clear temporarily.
Exact same pair will come back... "not fixed"
I used to have these exact same two faults regularly.
The common mind share had me thinking this was caused by disconnecting the scanner. Nope!
I dont think so anymore because now the pair is gone.
This condition is a genuine "tip of the Iceberg".
These two faults showing up mean CGW got swamped with disrupted data flow.
I don't EXACTLY know why but have clues...
This quit bugging me when I switched scanner from AUTEL to MS. cReader - I thought: great this works better. It was just a scamner bug like the ghost LIN 70b1 temp sensor.
Now I guess not, you have it on LAUNCH SCAN.
Then I'll conclude it was my CAN-C ISM causing this latency jam that disturbs CGW.
There are too many un-terminated connections pilled up across the gateway that have not expired - That's what rebooting car helps with. It took me over 10 years to understand this bug.
When CGW is upset, ESP is too. I think its the broken ESP traffic that fills up CGW queues.
ie. hance REBOOT EVERY 2 WEEKS. Simply disconnect GND at the strut tower and AUX GND too.
A reliable CAN-C HELPS ECU timings.... here:
Have you noticed fish-bites misfire when scanning engine ON, yes? Can-C HAS PROVEN Impacts ECU TIMINGS

+++ clearing CODE is like clearing RAIN +++
Resetting codes is like windshield wipers during the rain: it's great but does not stop the source.
Last edited by CaliBenzDriver; Mar 19, 2024 at 04:56 PM.





