Quote:
Originally Posted by Homeoboxter
Excellent information! But shouldn`t it trigger CEL right after I erase the code if it`s toast? CEL comes back usually in a day or two.
|
CEL could be from a faulty connection, faulty wiring, or a failed O2 sensor.
I you back probe with a DMM the way I described you will know if it is the O2 sensor or the wiring.
And you will know with the least amount of work.
Back probing can be a little fiddly sometimes but I feel it is the best place to start for your issue.
Remember you want find the connection closest to the O2 sensor and back probe the O2 side of the connection. Not the harness side.
your O2 sensor should be a four wire.
It will have two wires that are the same color. Those are the heating circuit.
You want to back probe the other two wires.
Polarity doesn't matter.
Then you have to run the engine for a few minutes to make sure the O2 sensor is heated up. They have to be around 600-650 degrees F before they start to function.
If you have a OBDII scanner hook it up and watch the other O2 sensor for when it starts working- goes into closed loop. Then you will know things are heated up.
If the suspect O2 sensor is working it should show a rising and falling voltage between I think it is .2 -.95 millivolts.
If you get a voltage signal from the suspect O2 sensor when you back probe it as described then you have a wiring issue. If you don't get a voltage signal from the Sensor it is toast
Hope this helps in some way.
Oh to answer your question:
Some Codes have to happen twice back to back over two drive cycles before they trigger the CEL.
The first occurrence they are set in an area of ECU memory called pending codes. Second occurrence moves the code to permanent code memory and triggers the CEL.
Most issues which are not immediately harmful to the cats are handled this way.
A misfire which can harm the cats sets the CEL on the first occurrence.
That's my current understanding of how it works.
**************** could change tomorrow LOL