Check Engine Light!!!

[privetryan89]

I have a check engine light that as been on for a while. I scanned the computer and it said that it was an oxygen sensor has gone bad. I changed it and the light went away for about 20 minutes then it came back on. I scanned it again and it said the same thing. I then cleared it and it came right back. What else could it be or do you think the one I replaced it with is bad? What if something else is wrong? Some help please!

 

[L4CX]

Did you check the Grounds and wiring to the O2 sensor? That could have something to do with it. Does it actually say "sensor is bad"? There is a thread around here that explains O2 sensors in depth. Hopefully someone will chime in and mention that thread.

 

[Dopler174]

It could be a bad new part, or you could have replaced the wrong one.

 

[aldive]

I would love to have the money spent on replacing O2 sensors that are perfectly good.

Chances are it was never a bad O2 sensor. The codes are usually thrown for something upstream of the O2 sensor.

Good luck in resolving your CEL.

 

[privetryan89]

The wiring seems fine. The part is brand new. When I scaned it the code told me a sensor was bad and which one was bad. That's the one I replaced. Could it be something in my emissions?

 

[Blee1099]

What was the actual code and what engine 4.0 SOHC/OHV or 5.0?

 

[privetryan89]

I forget the actual code but a book of codes came with the scanner. The code told my which sensor. I then took that data and looked it up on this automotive program from ford about my model year explorer. So I know that its probable the right sensor I replaced.
Could the computer be reading the sensor that is bad but telling me that the other one is bad instead? But what about the wiring? What could be wrong with it?

 

[budwich]

not to "dis" your "analysis" and "conclusions", but you will get more help in tracking down the problem if you give the forum the code(s)... without them people will be just "shooting in the dark".... the likely thing that will happen is that they will hit your wallet and your "free time" chasing your tail.

And "no" it is highly unlikely that the computer is "confused" about what "faulty" sensor it is trying to report and as was pointed out, it is more likely that the code is a symptom of problems elsewhere.

 

[cjones101812]

best to rescan for codes (is the check engine light on for the same reason?) and post them. as budwich said, that's the only way we can help.

 

[privetryan89]

I'm sorry, it will be a while till I can give you the code. My dad lent the scanner to a friend. When I get the scanner back I'll give you the code. and don't worry. you guys aren't dising me. I showed have told you the code in the start.