Code 34 knock sensor

[turboh224g]

We have been struggling trying to get our track only sr powered s13 coupe to start. We are running an engine harnesss only. Yesterday I installed a new redtop ecu and oem maf. When I try to start it it doesn;t start and I am getting code 34, knock sensor. Will the car still start while getting a knock code? Can the car even be getting a knock code when it turns over but doesn't start? Or is my sensor bad? Can I damage anything if I am getting knock and still try to start the car? Thanks,
JKP

[rps13drift]

i feel your pain buddy! I have also been getting that code but my car would start and rev but wouldnt hold an idle! The problem drove me nuts for the past month! Out of curiosity i had my buddy pull th battery cables while i was reving and the car shut down immediately and wouldnt work off alternator power. So i changed the alternator and it got alittle better but still wouldnt idle good! So after reving it for a bit i changed my spark plugs from copper to iridiums and my car wouldnt do anything but crank! So i tossed in a q45 ignitor chip and BAM!!! This bitch fires right up and idles perfect! So even though its saying a knock sensor recheck all your electrical components. I literally changed every intake side gasket and 3 mafs due to the fact that my problem sounded like a loss of air/vaccum situation but it turned out to be weak power/spark all along
good luck!

[opponheimer]

I've got a knock sensor for sale.. pm me.


If its showing the code btw, your knock sensor is likely bad.

[thejapino]

A bad KS will retard timing and your car will feel slowr.

[turboh224g]

does anyone know if it will hurt the motor to start the car if I am actually getting knock?
JKP

[MrFairlady]

can't imagine it would hurt...is the car running crazy Boost??Don't Gas it hard if that is the problem just to be safe.

Should Crank and still be ok somewhat.I wouldn't Boost if you can stand it.Should run.
normally Idle is affected and coolant temp readings,accel maybe etc etc.

Did your CEL come on...or you just ran the code??
My car has no spark..car just cut off while driving 1 day.Ran the code = 11 (CAS)...but my CEL was never on.Has me wondering If That will fix it even though the CEL never came on.Installing new CAS tonight.Sorry to Hijack.

[turboh224g]

we have no cel as this is a track only car running just an engine harness. I am glad to hear you say it shouldn't hurt anything. All I want is to be able to start the car and let it idle if I need to replace the KS to drive it that is fine but I still don't even know if the car starts.
JKP

[UNISA JECS]

FYI Code 34 does not throw a cel on OBDI

[Neejay]

FYI Code 34 does not throw a cel on OBDI
Oh really? So I guess my CEL is from code 35.

[theronin]

FYI Code 34 does not throw a cel on OBDI

that's weird my obd1 threw a cel from a code 34... care to elaborate?

oh and for what its worth i've heard from a very reputable source (Russ) that our knock sensors rarely if ever go bad. usually its just a loose connector or a bad ground to the right of the engine if you are looking at it from the front of the car, right above the o2 sensor.

[Neejay]

that's weird my obd1 threw a cel from a code 34... care to elaborate?

oh and for what its worth i've heard from a very reputable source (Russ) that our knock sensors rarely if ever go bad. usually its just a loose connector or a bad ground to the right of the engine if you are looking at it from the front of the car, right above the o2 sensor.
I hope my problem is that simple. I'm going to go outside now and take a look around.

[Neejay]

FYI Code 34 does not throw a cel on OBDI
Kinda confirmed...

I switched with another ECU, and because it got rid of my code 35 (EGT - california standards), it's safe to assume I had a cali ecu.

Now my CEL doesn't stay on all the time, just if I leave the key in the ON position. (only giving code 34 now)

[UNISA JECS]

Oh really? So I guess my CEL is from code 35.

If your only code was a 34 you would not throw a cell, if you had another code which does illuminate a cell and a 34, the cell was triped by the other code which does illuminate a cell.

I have fixed many S13 with code 34 issues, I know a lil something about code 34 on S13 by now.

that's weird my obd1 threw a cel from a code 34... care to elaborate?

oh and for what its worth i've heard from a very reputable source (Russ) that our knock sensors rarely if ever go bad. usually its just a loose connector or a bad ground to the right of the engine if you are looking at it from the front of the car, right above the o2 sensor.

Read above.

I agree with Russ, do a search with my name and you'll find info on diagnosising wiring to code 34, usually its a short to ground in the knock sesnor signal wire.

[Neejay]

Kinda confirmed...

I switched with another ECU, and because it got rid of my code 35 (EGT - california standards), it's safe to assume I had a cali ecu.

Now my CEL doesn't stay on all the time, just if I leave the key in the ON position. (only giving code 34 now)

If your only code was a 34 you would not throw a cell, if you had another code which does illuminate a cell and a 34, the cell was triped by the other code which does illuminate a cell.

I have fixed many S13 with code 34 issues, I know a lil something about code 34 on S13 by now.
:)

And yeah, my code 34 is the wiring, which I learned based on your post on this issue.

[projectRDM]

+1. A knock sensor code can be anything from bad gas, a fouled plug, dirty air filter, clogged fuel filter, bad O2 sensor, anything to deteriorate the A/F mixture. Replacing the sensor rarely erases the code, but sadly everyone assumes that's all it is and buys the shit out of them.

[fatlizzard]

The FSM tells how to diagnose a code 34 by checking the wiring and the sensor !