Jump to content
SAU Community

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 

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


  • Similar Content

  • Latest Posts

    • Hi all,   anyone know where I can pick one of these up for a reasonable price? I just resprayed my rear trunk due to fuel stain and my new muse spat install.    added a photo for some content 🤣👍   thanks 
    • Consider a 35 too...
    • He's right ~ there is no 'magic' with stuff like this ... it is more likely that in the process of looking for the short, the loom/wire 'incidentally' got moved in the process, thus removing the short ~ now, that maybe a wire (in a loom) rubbing against the edge of some grounded metal, that's worn through the insulation, causing the (now intermittent) short to ground. If one wire in a loom has been damaged in this fashion, it's reasonable to presume that other wires beside it may have also be damaged, and now exposed...you can bet the green crusty copper corrosion will start... ...that'd be a pisser, Murphy's Law steps right in as GTS observes...but worse, something like that is easier to find when shorted...ie; unplug bulb and fuse, and put multimeter in continuity mode so you get constant beep, and carefully poke about hoping to find if some movemet of the harness stop the beeping.... ...it's still all a bit Arnie tho' ..It'll be back... 😃
    • Yeah, but knowledge of one wire's insulation worn through to short on earth implies the possibility of other wires doing the same. I had my power steering die, because the wire that runs to the solenoid valve on the rack runs in the same loom as the power wire for the O2 sensor. And when the O2 sensor/wire did something stupid and burnt part of that loom to death, the only indication was the shit(ter) fuel economy and the heavy steering. It took deep excavation of the looms in the bay to find the problem. Not wear through in that case, but similar shit.
    • Ah, I thought he'd wired it to one of the spare ECU inputs! Too long ago since I read that post, ha ha. I've been arguing with radiators, harmonic balancers, alternators and rust since reading it.
×
×
  • Create New...