My oxygen sensor has seen nearly 120k, and my car's throwing code 1 (obd1) every once in a while. But, the obd1 ecu was only plugged in recently (mugen chip). I'm aware that the chip is causing me to run a bit rich, but my ob2a ecu never threw this code 1 before.

What my main concern is if I do go ahead and replace the oxygen sensor now and continue to run rich for an extra month or two, will it foul my new oxygen sensor? Or do you think it's just a coincidence that the o2 failed a week after running the obd1 ecu?

 

Do you still run the secondary 02 sensor? If so you could swap em and see if this makes the CEL go away.

I can't imagine the mugen chip would cause the sensor to go foul, but you never know when a car has 120k on it.

 

Car was running off the jdm p73 when I bought it, so it never needed the secondary O2.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by erikiksaz1 &raquo;</TD></TR><TR><TD CLASS="quote">My oxygen sensor has seen nearly 120k, and my car's throwing code 1 (obd1) every once in a while. But, the obd1 ecu was only plugged in recently (mugen chip). I'm aware that the chip is causing me to run a bit rich, but my ob2a ecu never threw this code 1 before.

What my main concern is if I do go ahead and replace the oxygen sensor now and continue to run rich for an extra month or two, will it foul my new oxygen sensor? Or do you think it's just a coincidence that the o2 failed a week after running the obd1 ecu?</TD></TR></TABLE>

could be due to the chip.. you can test it by replacing with obd2 ecu

 

pm'd

 

if thats an oem o2 sensor. its common especially on itr for o2 to fail without throwing codes.