P0134

Odey.V.K20 · Post by **Odey.V.K20** » Sun Jun 28, 2009 10:23 pm

My car is throwing error code P0134. Little background on the car, it's a 2004 Honda Civic SI-G, with a K20A3 engine swap, Greddy Turbo Kit, 650cc injectors, Apexi ... exhaust. So i replaced the primary O2 sensor, and the car is still pulling the error code. Next thing is to check the wiring going to the sensor, but beyond that i have no ideas on how to solve this issue. I ran the car for a day with the code disabled in open loop and i burned over 1/2 tank of gas driving 140kms, and the car was running so rich and it was bogging down.

Any input would be awesome,

Thanks in advance,

Post by **Spunkster** » Mon Jun 29, 2009 10:12 am

Has the car been tuned on the dyno? Have you followed the Helms manual troubleshooting for the error code you are getting?

Odey.V.K20 · Post by **Odey.V.K20** » Wed Jul 01, 2009 11:16 am

Yes the car has been tuned. Is it possible that the car needs a new tune to fix this issue?

Well originally it pulls up P1167, but if you diable P1166 in the parameters section on K-pro it goes away and then pull P0134.

The wires have been checked and ran back to make sure no flaws in the wiring are there, there was a couple burnt wires on the exhaust that were fixed but the issue is still coming up. Is it possible the sensor shorted out when the bare wire came in contact with the metal of the exhaust?

Post by **Spunkster** » Wed Jul 01, 2009 4:56 pm

That last bit of information is important and should have been given in your first post. Try the ECU in a known good vehicle and see if it works correctly then. This will let you know if it is the ECU or the vehicle/wiring/sensor.

Odey.V.K20 · Post by **Odey.V.K20** » Wed Jul 01, 2009 5:06 pm

Ok. The ECU is for a 2002-2004 Acura RSX. So can i just throw that ECU in a stock RSX? Or does it have to be a turbo RSX?

Post by **Spunkster** » Thu Jul 02, 2009 9:28 am

Any 02-04 manual RSX as long as you upload the correct calibration.

Odey.V.K20 · Post by **Odey.V.K20** » Thu Jul 02, 2009 11:56 am

Does it matter if it's a type-s or a base model?

Post by **Spunkster** » Thu Jul 02, 2009 1:11 pm

Any 02-04 manual RSX

Odey.V.K20 · Post by **Odey.V.K20** » Mon Jul 13, 2009 11:00 pm

So i can't find a manual RSX test vehicle and neither can the performance shop that my car is being worked on. Is there another way to isolate the problem without having a test vehicle? The ECU was tested for faults about 4-5 months ago by hondata and a hondata dealer in Calgary Alberta. It was tested in Calgary with a test vehicle but was only run for about 10 minutes, but that should have been plenty of time to bring up the error code.

Post by **Spunkster** » Tue Jul 14, 2009 9:27 am

Get on the forums and ask around, there has to be someone else in your area that has an RSX or Civic SI that you can test this in. Based on what you have posted it sounds lik eyou either have a damaged ecu or a problem with wiring. The next step is to isolate which it is.

Odey.V.K20 · Post by **Odey.V.K20** » Sun Aug 16, 2009 11:11 pm

Well after we replaced the O2 sensor, they found some wires that burn't onto the exhaust. The mechanic told me he's pretty sure the one is a constant power wire to the sensor. Is there anyway that could have fried the sensor?

Also found a test vehicle, one is a 2002 rsx with a swapped k24, and the other is a 2002 rsx type-s. The type-s is written off but still runs and drives but is harder to access. The swapped k24 still uses the k20 sensors and wiring. Would this still work as a test vehicle?

Post by **Spunkster** » Mon Aug 17, 2009 9:56 am

Try it in those vehicles to see if everything works properly.

Odey.V.K20 · Post by **Odey.V.K20** » Mon Aug 17, 2009 9:28 pm

Should be testing it out tomorrow.

According to the shop it was initially pulling up a primary heater circuit code, they ended up taking it to Honda, and they think Honda replaced the secondary sensor with a primary sensor. I believe they are different. I was looking at the tune yesterday, and no codes are disabled in the closed loop section of parameters, and up until this there was no CEL. Is there anyway that them using the wrong sensor in the secondary slot could be messing up the whole system? Cause when nothing is disabled P1166 comes up but nothing else. Then when you disable P1167, P0134 comes up.

Odey.V.K20 · Post by **Odey.V.K20** » Wed Aug 19, 2009 2:29 am

Won't be able to test for another couple of days. If it's not the ECU, what can we be doing in the meantime to narrow down the possibilities of what it could be?

I've heard everything from fuel delivery issues or an exhaust leak.

Post by **Spunkster** » Wed Aug 19, 2009 11:03 am

There is nothing more to check until you have tried the ECU in a known good vehicle. This will tell you if you damaged the ECU when you had the melted wires.