reset ECU yesterday (left dissconnected for an hour). reconnected ECU switched ignition on but not started still giving code 34, surely this would have read no faults as it had not even been driven? surely not the detonation reading anyway.

 

please help.

Lack300,

 

If I remember correctly, code 34 means the detonation sensor is faulty, not that it is detonating. The car will go into safety as the sensor is faulty and could not detect if there was detonation - does that make sense????????

 

Vijay

so what do i do then. can anybody out there fix it. it is really pissing me off.

cheers "T"..........

Tony, if you're after clearing the ECU code then popping in a resistor will do the trick. I reckon that your car isn't actually detting instead the wire harnass between the det sensor and the ECU has gone south ... I can help you out with the resistor - 5 minute job.

 

Cheers,

 

Danny

 

A little clarification on the dreaded Code 34:

 

This code signifies a non standard voltage across the knock sensor. This can be due to the following:

 

1. the knock sensor has detected engine detonation (the sensor is actually a solid state device "listening" for a set frequency/vibration that corresponds to the engine detting.)

 

2. the knock sensor is faulty

 

3. there is a problem with the wiring loom between the knock sensor and the ECU.

 

As the procedure for replacing the knock sensor requires the lower plenum to be removed or alternatively an engine out job, it is far easier to by-pass the knock sensor. This is done by inserting a 1 mega ohm resistor in the connector to fool the ECU in thinking the knock sensor is fine. This will clear the ECU Code 34 and restore the car to normal boost BUT it will prevent it from going back into safety boost if and when the car does start detonating. So, be very careful in considering whether or not to perform the by-pass procedure.

 

Hope this helps clarify some things.

 

Any further question - please let me know.

 

Cheers,

 

Danny

I've said it before and I'll say it again!!!

 

I would SERIOUSLY consider my options before bypassing the det sensor!!! Tony, I know your car already has detting problems and removing the det sensor could makes things so much worse!!! If the car had been running fine then yeah, bypassing the sensor would be a possible option as a temporary measure - but it aint running fine!!!!

 

CheerZ,

 

Andy

cheers for the help and concern guys, read all sorted now...

>>1. the knock sensor has detected engine detonation (the sensor is actually a solid state device "listening" for a set frequency/vibration that corresponds to the engine detting.)

 

NO NO NO NO NO NO NO and NO

 

If your engine IS detonating, it will NOT trigger a code 34.

 

ONLY a faulty sensor or connection to the sensor will trigger a code 34

 

 

 

[This message has been edited by H Le Hir (edited 26-03-2002).]

henry why doesnt it go away when ECU has been reset. though i have left it disconnected for 4 days now is this long enough. will try tomorrow, standard ecu has been in for few days with boost jets running 11psi no faults readings.

 

lack could you not have been sodl a duff ECU?

It seems to me you have gone through all the channels trying to find the fault.

Sounds very much like you were sold a buggered ecu?

Tony,

 

It probably *is* going away when you reset the ECU, but since the code is telling you that either the sensor or wiring is faulty, as soon as you turn the ignition on and it checks the sensors (I can't say if it does this at start-up, or as soon as the car is at Ign. pos 2) it's finding a fault with the detonation sensor, and flagging the fault code up again...

 

Again, it's not reporting detonation here - it's telling you that the sensor (or wiring to it) is shafted.

 

Aaron

...... and if the ecu is replaced with a known good one then no errors appear - let me guess....... THE ECU IS FAULTY!!!!

 

CheerZ,

 

Andy

yup first rule of thumb , elimination. swap out the ecu with another one, If it all comes up trumps then you know its the ECU that is shagged.

RTFM !!

 

Measure resitance at the Sensor - Or failing that the plug ! as the det sensor is tucked away down there.

 

Then Measure Resistance at the Pin on the ECU connector if the two readings match then Hey Presto the ECU is fucked.

 

If the First reading is garbage Detsensor or connector is screwed.

 

It the Two readings dont match you have a fault in your loom.

 

Its all in the manual un fault diagnosis.

 

 

 

------------------

Z ya

 

Nico91TT

 

 

Dont be a Punk ...

 

Please please buy it - im gettin desperate now god damit !!!

listen up guys the fault disappears when i put my stanadard ECU back in. code 55

 

when i put veilside ECU in i get code 34 without even starting the car up.

 

what i am waiting for is the ECU to lose the settings but how long does this take. it has been out for 5 days now. just havent had time to swap them back again yet. to see if it still reads code 34.

 

cheers "T"........

I reckon that ECU is shagged, OR maybe has a broken pin 23.

http://www.twinturbo.net/ttnetfaq/FAQpages/ecuharness.html

Lack id take the ecu back to whomever you bought it form and get your money back, it is shagged.