Can read, but not delete fault DTC codes

[sri_130]

Anyone had this issue?
My OBD2 scanner thing, used to work as normal. But now, it can read the codes, says it's erased them, but it hasn't. Ignition off/on again, they are still there. I know I've remedied at least one of the codes as well! FFS.

I bought an Elm327 cable, but struggling to get that to connect at all, to even read codes using scantool, despite it showing as connected and correct drivers on the laptop.

[Chipwizards]

Are the ignition and battery power wires to the ECU connected exactly as stock?

If not, then the 'deleted' codes, which are only deleted in RAM, don't get written out of the non-volatile EEPROM where codes are more permanently stored. So when you power it back up and the codes are read back from the EEPROM they are still there.

Data (codes, adaptions etc) are written from RAM during the 'shutdown' phase after they key is turned off, which typically lasts about ten seconds.

[sri_130]

Are the ignition and battery power wires to the ECU connected exactly as stock?

If not, then the 'deleted' codes, which are only deleted in RAM, don't get written out of the non-volatile EEPROM where codes are more permanently stored. So when you power it back up and the codes are read back from the EEPROM they are still there.

Data (codes, adaptions etc) are written from RAM during the 'shutdown' phase after they key is turned off, which typically lasts about ten seconds.

Same as it always has been Wayne.
I'll try another reader.
If not, will have to ask you to delete them when I come back