Honda / Acura K20a K24a Engine Forum banner

CEL KPro code PO134??

10K views 26 replies 6 participants last post by  panchovilla760  
#1 ·
why am i getting this code, i have a jdm k20a in a ek if that helps any
 
#11 ·
P0134 code is the primary O2-sensor response error code. The ECU somehow checks the response time of the sensor during a certain period of time just after the engine start-up. Getting this code does not mean your lambda is broken. Just disable this code from Parameters - Closed Loop in kmanager-software.
 
#14 ·
im pretty sure it affects ur car. i disabled mine and it ran like shit, bad gas mileage (15 mpg) bogging during normal driving. if you search on club rsx they talk about it. i tried searching for another alternative even after having it tuned (twice). and i am goin to try changing the o2 out for a new one. on a side note i checked my o2 sensor and all wires are intact no melting of any sort.. ??? :confused:
 
#15 ·
If it affected your car, then there really is a problem with your lambda sensor or wiring. I used to get these error codes in start-up with older kmanager versions and had the box ticked. That didn't have any effect on my tune or the way my car ran. At the moment I know of one car that still has to run with this error code disabled.
 
#22 ·
so i was checking out club rsx in the ecu tunning section,Hondata K-Pro and reflash FAQ, and this is what i found
How does the K-Pro work with a race header that doesn't have a secondary oxygen sensor?

The K-Pro uses the primary (wideband) oxygen sensor to determine air-fuel ratio and for open/closed loop operation. The secondary sensor simply determines if the cat is there and the primary sensor is working. Without the secondary sensor, the ECU will cause a P0134 error code that can be disabled in the K-Pro Parameters window.
 
#23 ·
No, I didn't have my secondary lambda wired to work (european CTR using PRB ECU) and this did not trigger P0134. In case you don't run secondary lambda sensor, you just need to disable OBD2. I have understood that P0134 has nothing to do with the secondary lambda...

(as I mentioned before, I had the error code with earlier versions of kmanager, not with the newer ones, see here.)
 
#24 ·
Ok, now we had the same problem with another car. Suddenly got P0134 and disabling the error code didn't help. Then we checked the wiring, because we thought the FI setup on the car could have melted some wires. Wires ok. Then we replaced the primary lambda sensor and that fixed the problem!

Kinda weird as we usually get code P1166 when the lambda dies. And they do die often :mad: