Scan Gauge code clearing

[mikes04rt4]

when the scangauge clears ne codes is it just clearin the code or is it more less a comp reset(like unhookin the battery)

[morgantj13]

bump for answer...

[forcefedjunkie]

It is just clearing the codes.

Todd

[4TEHW]

Quote: Originally Posted by forcefedjunkie

It is just clearing the codes.

Todd

This. I was having issues with my cam sensor and I'd throw a code. I was able to clear it using my Scangauge removing the ~2,000RPM limiter. Life saver, for sure. Even though you can pull a fuse to clear it, being able to handle it from your car is priceless (considering when it happened I was on a very busy freeway and then later, in the middle of nowhere at night).

[7055]

I was never able to get this to work. I had poo38 which is the no cat code even though I had a cat. It would come on whenever I unplugged the sensor to work on things even though I plugged it back in.

[4TEHW]

Quote: Originally Posted by 7055

I was never able to get this to work. I had poo38 which is the no cat code even though I had a cat. It would come on whenever I unplugged the sensor to work on things even though I plugged it back in.

You weren't able to clear it with the scan gauge? If there's an ongoing problem, the PCM will detect it and 'throw' the code again. Clearing it is only a temporary fix, unless you address the issue.

[7055]

It wasn't an ongoing problem, the sensor was plugged in. I just drove the car until the light turned off usually, many starts and shutdowns.

[a853rox]

Quote: Originally Posted by 7055

I was never able to get this to work. I had poo38 which is the no cat code even though I had a cat. It would come on whenever I unplugged the sensor to work on things even though I plugged it back in.

Is that not the one that is present on all S2/S3 kits? I should go out and check mine but there is one associated with S2/S3 that won't throw CEL and will be there after a reset, but isn't a real issue...

[7055]

No this was when I was all stock. It was whatever code you get if the downstream o2 isn't plugged in. What would happen is I'd unplug the o2 when working on the car, then when I plugged it in and started driving there was always that code as a result. It would go away eventually but I could never clear it with the Aeroforce. It wasn't a real issue since it doesn't affect how the car runs.

[forcefedjunkie]

Did you clear it with key on/engine off, turn ingition off, then back on? The PCM must have been immediately setting the code when you restarted the car.

Todd

[7055]

I just did it while the car was running, went into the DTC screen and hit the button to clear the codes. So I guess you have to do it with the car not running and the ignition on, that must have been why.