Quote:
|
Originally Posted by 400E
I was unclear in my question. Here's what I meant to say:
How long do fault codes stay in the computer if they are not manually cleared?
I had understood that the computer itself has the capacity to clear certain codes if a certain number of normal operation cycles (i.e., engine start/stop) occur, so that a one-time, transient fault code won't stay resident in the computer forever.
Is this accurate?
|
The drive cycle code clearing is a memory feature for any soft code.
But for intermittent codes , there has to be 2 back to back trips of the exact same fault for storage . However , if the first trip registers a fault , it is pending in the memory. If it does not return the next trip, it does not get stored, but erased. That is why brake lamp sw codes are hard to find.. but is you get an ASR fault due to a sw failure , you can get the pending code from the module even though it has not been stored. It is a pending code awaiting failure on the next trip to get stored. But it is still there..
Many Tech with ASR complaints just change the B/Sw before proceding to the ETA b/c of the high fail rate and difficulty of catching the intermittent poor contact of the sw. You can pump a bad b/sw many times and not see a failure , but it can also fail 5 times in a row.. it is a mechanical contactor, highly used switch...
You will notice that his problems were at low speeds and stop and go.. good probable of sw failure due to activation. On the same note , you notice he was having stall problems, indicating a probable ETA.. My first shot would be go with the sw and clear out any memory codes ..
As I mentioned in the earlier post, the EA/CC w/asr module is where one wants to look for possible stored or pending codes
The CE MIL lamp has nothing to do with these codes as the CE is activated by emmissions related codes
The Stop Lamp codes are #2 and #6 of the N4/1 module and do not trip a CE lamp........