O2 codes.

Disclaimer: Links on this page pointing to Amazon, eBay and other sites may include affiliate code. If you click them and make a purchase, we may earn a small commission.

Ishodu

SHO Member
Joined
Jun 26, 2002
Messages
5,077
Reaction score
615
Location
Ontario Canada
Well got a CE light today. So I check the codes and for KOEO I get 111 and then 173,177. 173-Oxygen sensor not switching - system is or was rich - Single, Right or Rear HO2S. 177- Oxygen sensor not switching - system was rich Left or Front HO2S. I know it looks like the two O2 sensors are done but they are new. Less than 4000km (2400miles)on them. I cleared up the codes and I will see what happens. I did the KOER test and all it well. Any ideas?
 

Mr Anonymous

Tire Wall
Joined
Apr 24, 2002
Messages
7,317
Reaction score
1,947
Location
St. Louis, MO
I suspect you probably have a rich condition which the O2 sensors are accurately reporting. How has your gas mileage been lately? Any chance your t-stat is stuck open?
 

Ishodu

SHO Member
Joined
Jun 26, 2002
Messages
5,077
Reaction score
615
Location
Ontario Canada
The gas mileage seems normal. The T-stat is only about 6000km old I replaced it in the fall. The temp gauge reads 190 and won't go lower than that. I don't know what to think of this. The ECt Sender is also new.
 

rangerj

Active Member
Joined
Jun 6, 2002
Messages
2,338
Reaction score
10
Location
Brunswick, Ohio
ISHODU,

The computer "codes" when it does not get the signal from a sensor that it is programmed to expect. A "code" from a specific list of sensors will activate the "Check Engine" light.

The HEGO, or more commonly the 0-2 (oxygen) sensors "switch" from rich to lean continuously as the exaust gas flows by them.

If a code is set because the 0-2 sensors stop switching, and stay in either the lean or rich condition, the computer codes (and activates the CE light).

The question is, why did the 0-2 sensors stop switching? Are they in fact reading a rich condition? Is there a poor connection, an open or shorted wire interferring with the "signal"?
Or, do you have failed sensors?

I put the failed sensor question last to make a point. The point is that a "code" does not automatically mean a failed sensor. It is wise and economical to check out the other possible causes of the "code" before replacing a sensor.

In the instance you describe it would seem that you had an intermittant rich condition that resolved itself. If it returns and stays, then start looking for the cause.

Cold Molsons for everyone! cheers rangerj
 

Forum statistics

Threads
107,077
Messages
1,181,196
Members
16,142
Latest member
Kaevorlly

Members online

Back
Top