Weird Idle after throwing code P1133???
Since putting on headers I've been getting the insufficient O2 switching on the driver's side, code P1133. I put on new Denso O2 sensors and tried to seal everything up around the collector and it still comes on about once every 100 miles or so. Last night it came on and then the car started idling funny, way up at 2500 rpm, then down at 1500, but never at 925 where it was set during a recent tune. I carry an Actron scanner with me, so I plugged in and got the 1133 code and then erased it after pulling off the road. The idle went back to normal. OK, now was that just a coincidence? Or is it real. I had a strange idle the other day without the code, but I fixed it by cleaning a very dirty IAC valve.
If this is real, what is going to happen when I get my friend with HPTuners to turn the code off. He says he won't turn the code off, just make it so it doesn't throw the code. I'd hate to think that if it throws the code, doesn't report it and the car just runs funky! That would be terrible. What should I do?
What I need to know is, is it normal for a car to run funny after throwing a code and then clear up after erasing it?
Didn't mean to offend you. I replaced both front O2's with new Denso O2's. It fixed the passenger side code 1153, but not the driver's side. After searching I've found that some people after numerous new O2's still couldn't eliminate 1133 or 1153. I may still have a header leak on that side, but I sure don't hear or see (carbon tracks) one. The last thing I do not want to try is grinding down the bung on that side to get the O2 sensor more into the gas flow. Just seems like it would be very hard to grind it square and if you don't I'll end up with a leak right at the O2 sensor which would not be good.
I am thinking about just turning off the reporting of this code. My questions are, will it act up after throwing a code? That is, does the computer do funny things after a code is thrown or was it just pure coincidence that I had the IAC issues again? The car has idled perfectly since clearing the code and I haven't gotten a code since. This is really frustrating. I hate to go buy more new O2's, but I may get a new AC Delco O2 sensor off of Ebay, they are only $35. Also, if you turn off the reporting of the code, will anyone be able to see it when emmisions people hook up for testing?
Thanks,
Glenn
Trending Topics
Onfire, I used the antiseize that came with the Denso O2's.
The only thing that really scares me is I think I might have a leak where the AIR tube welds on. I sure can't see it or hear it, but when I was putting the air tube on, I thought I felt the tube give a little. Maybe I'm just being paranoid. Anyway, I took the tubes off and replaced them with block off plates. At least that fixed the check valve fluttering (and I did put on the 3/16" diameter orifice plates), but I still got the 1133 code.
My tuner said not to turn off this code, that he had heard of funny things going on when people did that. I'll try re-torqueing the header bolts and put some more high temp RTV on the collector flange. This is a pain, but thanks to everyone that is helping.
The Best V8 Stories One Small Block at Time



