phil128605

Hey, hoping someone has some answers. Im throwing the codes above. I know the definition off all of them. From what I have gathered from searching the forum, it seems that one of my A/F sensors is bad. I had replaced the one closest to the radiator about a year and a half or 2 years ago. Is it this one that has gone bad again, or is it the other bank. Any suggestions are appreciated.

salimshah

How about resetting the CEL and try to capture code at the earliest. With multiple codes, at times it is better to work with the first.

Salim

phil128605

thanks, im going to buy a code reader and try that. I have a new a/f sensor, but I hate to install it before i figure out for sure which one is messed up.

phil128605

okay, so i bought a decent code reader. erased the codes and drove about 2 miles. the first and only code to pop up at that point is the P0125 (insufficient coolant temp for closed loop fuel control). in my freeze frame data, It says LTFT (Long term fuel trim) B2 -3.9. All the other banks are at 0.0. Does this indicate that the A/F meter on B2 is the one that is bad?

Lexmex

When you plugged in the code reader were you in motion at all?

Sometimes a single P0125 all by itself is a function of bad coolant (I had that issue a while ago), but given you got those are codes at a time I would be interested to know if you see any movement in any of the A/F sensor readings on either bank.

BTW, I just ordered two Denso 234-9009 A/F sensors and they should arrive some time within the next week, so I'll be comparing my before and after readings. The original sensors still function, but I know they aren't full 100% given the time in Mexico.

phil128605

I was not moving at all, the car was not on. I think this reader takes the data when the code pops up. I deleted all the codes, drove it more and the p0125 came on by itself for about 10 miles, then p1153 popped up. By the time i drove home i had p0124 p1153 p1155 p1153. So now im thinking it is the p1153, the front sensor

Lexmex

This is one of the reasons I have some software/scanner to check to the freezeframe on the codes to see what event triggered (e.g. a/f sensor reading, fuel trim, intake air temperature, etc.), because then it can be narrowed down, because if I see a/f sensor readings out of spec several times after resetting the CEL, then I put my finger on it other than checking voltage directly on the sensor itself with a voltage meter.

BTW, straight from the manual, the a/f sensor issue can be the triggering event for the P0125 code, but again I've had the code and in my case after changing out the coolant the problem went away (which I knew was contaminated). Again, if you can see what the readings are on those 2 A/F sensor banks, that's going to isolate the problem. Sometimes, some injector blockage issues can also result in this (i.e., bad gas), but it's rare.

phil128605

well, couldnt get the sensor out, so i took it to a place that is going to pull the manifold to get the sensor out, tap it, and put in the new one. hope its the problem.

T4-Teg

iTrader: (2)

What is your coolant temp? The insuffient coolant temp could be caused by a bad temp sensor (unlikely) or the more common stuck open T-stat. I would replace the thermostat and do a coolant flush, if your readings are lower than normal. Im not sure the exact coolant temp for the RX vehicles, but for the most part if any vehicles coolant is less than AT LEAST 180* there is a problem, and the PCM will not let the vehicle go into closed loop operation.

You very well could have more than one problem. You may also have a Bad A/F sensor.

phil128605

im pretty sure it was 186 when the P0125 was tripped. Thats what my freeze frame data shows on my reader.