FluKy15

That's news to me, never heard that before.

Croc

a lot of reports here about this.

FluKy15

I just gotta red this forum more often then darnit lol

caleb2483

yea a lot of threads about it... and seems like replacing the o2 sensor (with the new revised one?) does the trick..

but im more concerned about the damage it does to the engine while driving around with this code... well for me driving it around with the code erased and reflashed ecu again... my worry is if the o2 is still bad (even though i cleared the code) and keep driving it around, harms the engine components???

someone chime in please?

T-Man

I drove around for quite a while with the CEL on/cleared daily. I had no problems, no noticable affect on fuel mileage either. I datalogged fairly often just to make sure nothing looked screwy during that time and everything looked fine. I think the ECU just goes into some sort of safe mode.

caleb2483

what about the graph i posted? me at idle... doesnt that look bad?

FluKy15

I think the car was trying to tell you something... Daily.

T-Man

Well, yeah. Actually, the cool part about datalogging during that time is that I learned what operating conditions would trip the CEL. I don't remember exactly what it was now, but it was at a specific throttle position and rpm combination. It would trip the code and the CEL light would come on within a few miles aftewards. From what I remember reading on here, there was a defect with both the Primary O2 itself, as well as a computer programming error in the ecu. The TSB involved getting a new sensor and a Honda reflash. I believe HONDATA got their hands on the update and put it into their FlashPro/reflash. Also, FYI, the new sensor was physically different then the old one. It worked like a charm .