Jump to content
SAU Community

Recommended Posts

hey all, iv had a problem with my knock sensor, it retards the ign timing sometimes on idle( between 1-15 mostly sits around 7 degree), but when driving the car felt normal.

I turned on the car today heated it up idled fine, i started to drive and timing dropped to 2-5 degree under load, it even hit 0 it couldnt be driven, but on idle it was okay.

I ran it through a scanner and it came up with the code 34 knock sensor earlier today, but after today im not sure if it would doing this from just the sensor being off, i feel like it might have skipped a tooth on the belt. Anyone had the knock sensor problem before?

Edited by HungarySkyline
Link to comment
https://www.sau.com.au/forums/topic/426473-knock-sensor-problem-rb20det/
Share on other sites

I did. One of my sensors was ALWAYS reading knock between 0 - 20 non stop never a flat line. Pulled off the wire, trimmed it and reattached it and the problem went. I warn you though, it is an absolute flamin mongrel of a f**k to reach. I kid you not, Ive done my clutch, Ive done my timing belt, Ive done my turbo and the worst out of everything was trying to get to the sensor and unplug the wire. If its a code error you might have a faulty sensor. I suggest if you recently did your belt, pull it apart and ensure everything is lined up. One tooth won't cause engine damage, usually, but it will hinder performance terribly. Valves will not be truly sealed when it should be.

I hope your sensor isn't damaged. You could simplify the task greatly if you pull out the plenum and runners. Its a shit job. From what I know, you CAN run on one sensor. Try unplug one, again good luck, and see how it goes. You gotta squeeze the connector and pull out.

  • Like 1
  • 1 month later...

my gts4 I had ages ago had knock sensor code come up every now and then , ignored it as it ran pretty good and then I had to rebuild the motor due to no1 piston melted. -was running lean

I replaced one on a different gtst when replacing the cracked head here a photo to show ya where they are:

post-97292-0-51334500-1373749127_thumb.jpg

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

    • 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.
    • Correct. The ECU cannot read oil temp. (Well, I think it probably can in some situations. I did have the thought of potentially repinning the ECU when I was doing oil pressure). I am using this into the MPVI dongle, so that the MPVI dongle can read oil temperature. It is attached to a VDO gauge which is obviously calibrated to whatever curve the sender actually is using. This would be easy if I could setup a table of voltage to temperature like many sensors, but it appears I cannot do this and can only setup the transform rule which appears to be Input (voltage) x Multiplier, and add an offset. This to me means it MUST be linear. So it may be a complete waste of time wiring this into the ECU. The idea was that the MPVI3 has standalone logging. I wanted to use this instead of a laptop with serial cable (for wideband) for long datalogs. Given the wideband also has electric interference, I may never trust this either in a world where the serial wideband and the analog output wideband do not agree. Last time I did a trace I could see the two wideband traces follow each other, but one was a little leaner than the other. I plan on playing with voltage offsets and actually driving the thing to see how close they correlate. If they never correlate... then, well, maybe I'll never use either. Ideally I'd like to have the Analog wideband read ever so slightly leaner than the serial one, because the serial one is 'correct'. Tuning the car to be ever so slightly too-rich would be the aim. Not needing to have a laptop flying around in the footwell connected with cables is... an advantage. About the only one from the forced upgrade to MPVI3.
    • Hopefully not, since he knows the fuses work ha ha ha
  • Create New...