Ok so i plugged in the laptop and ran datascan still using v1.4... Well come up with code34 2 starts ago.. So i am like hmmm so i reset the ecu and code 55 come up i am like hmm ok then... So i stopped the car then connected to datascan again checked codes and getting code 55 i done this a couple of times... Now for code34 to come up i am guessing its something to do with the wiring from the dat sensor to the ecu from what i have been reading... My car does not ping at all holds boost fine when i do give it some stick which is not all the time i drive like a granny hahahah But got me stuffed how code 34 comes up then reset the ecu and code55 comes up now... I am only guessing here but if there was a problem with the ecu when you reset the ecu code34 would still keep popping up?? Well motor will be coming out down the track once everything else is all sorted out... So everything will be checked out and replaced pretty much... Nath
Which means one of two things: a) The ECU is actually detecting knock - this is the most likely or b) The connection to the knock sensor is intermittently bad
Yeah that what was thinking... Well it was the 2 starts this morning... Well it was 3 when i checked with datascan... Car was not started at all yesutrday so sat in the driveway... Got me stuffed tho like you said code34 should be popping up after the ECU has been reset but its not... maybe its just a the connection to the knock sensor is intermittently bad as to what ltd has said...
Have you taken it for a full on fang after starting it as it may only occur under full load/boost ? .
I don't believe code 34 comes up when it detects knock. Only when it detects an error in the knock circuit. If you haven't driven the car since then, I believe it will continue with a code 55. Take it for a drive and see what you come up with.
Well i took the car out before and gave it a little bit... Plugged in the laptop and code 55 come up... So got me stuffed... I guess all i can do is keep checking with datascan and see how i go... I noticed that when i did load up datascan the first time as i got it off hyper101 it was showing code34 but that was when it was on his car... Maybe i should install v1.5 so its a fresh install and see what it shows up then... Thanks for the help so far guys
I get code 34 when I start my car from cold. For example today I started my car at about 1:30pm and got code 34. I cleared the codes and have started it about 12 times since and each time I get code 55. I don't know what to deduce other than it is my actual det sensor that is stuffed rather than any wiring.
Hmm that is very weird... The funny thing is i start the car each morning and goto work and go home etc i have checked a couple of times and code 55... weird tho how it come up the ecu detects code 34 but when you reset it goes to code 55... Bloody cars lol oh wells i think i will just replace the dat sensor once the motor is out anyways...
Intermittent code 34 is almost always faulty wiring/det sensor. For the record, code 34 doesnt mean you are detonating... just the circuit that monitors detonation is faulty... Check det sensor wiring from plug at rear of plenum to det sensor... Often the black wire is broken, almost broken. If that's fine then you have a terminal det sensor... Best interim solution is a bypass with 1Meg Ohm resistor or relocate a new sensor onto the back of the plenum... search will reveal details
