Jump to content
SAU Community
  • Welcome to SAU Community

    Welcome to SAU Community, like most online communities you must register to view or post in our community, but don't worry this is a simple free process that requires minimal information for you to signup. Be apart of SAU Community by signing in or creating an account.

    • Start new topics and reply to others
    • Subscribe to topics and forums to get email updates
    • Get your own profile page, build reputation and make new friends
    • Send personal messages to other members.
    • See fewer ads!

    Consider joining our newsletter for the latest content updates

    Click here to register


Blaeeeek

RB20DET Code 34 even after knock sensor bypass

Recommended Posts

Hey fellas. 

Since I bought my HCR32 it has ran pretty well although it runs rich and sucks down fuel. I checked the codes and it throws a code 34, knock sensor and a code 21, ignition signal. I heard that when code 34 is thrown the ECU will retard timing and dump in fuel. 

 

I went ahead and bypassed the knock sensors for diagnosis purposes. I went down to the ECU and soldered 1/4 watt 1M ohm resistor on each of the two wires for the two knock sensors, and grounded the other ends to the chassis. 

 

After doing so, I went and test drove the car and I could feel a slight hesitation around 5-6k rpm or so, which it didn't do before. It feels like it maybe is slightly slower after said hesitation, perhaps the ECU pulling timing. However, it didn't do this prior to me bypassing the knock sensors. 

 

Got back home, checked the codes, and code 34 once again showed. If I bypassed the sensors with the resistors I would think it's not possible to throw that code. 

 

My question is, is the hesitation pulling timing, and it actually wasn't pulling timing before the bypass like I thought it was? Or could it have been pinging that I felt? I'm not sure exactly what pinging feels like as I've never experienced it. 

 

Perhaps my rich/awful mpg issue is something else and this was all a waste of time. Let me know what you guys think, thanks 

Link to post
Share on other sites
11 hours ago, GTSBoy said:

Did you clear the original code? Won't go away immediately.

Yeah, disconnected the battery to clear and verified code 55 before test driving it, came back and code 34 once again. 

Link to post
Share on other sites
27 minutes ago, Blaeeeek said:

Yeah, disconnected the battery to clear and verified code 55 before test driving it, came back and code 34 once again. 

I had this before on rb25, turned out to be my tps hey, bloody weird 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...