Po332 knock sensor
#1
TECH Fanatic
Thread Starter
iTrader: (10)
Join Date: Apr 2006
Location: Fort Worth, Tx
Posts: 1,340
Likes: 0
Received 0 Likes
on
0 Posts
Po332 knock sensor
car runs fine, lid/catback for mods, no problems other than the light. there seems to be no timing retard, i hooked it up to a solus this morning and revving the engine i achieved 26* of timing at about 3.5k rpm, and about 17-18* at idle. where do i need to start diagnosing this? could the sensor have just died?
#2
TECH Addict
Join Date: Jun 2002
Location: Las Vegas, NV
Posts: 2,428
Likes: 0
Received 0 Likes
on
0 Posts
If you got just that one code, you need to replace the KS it corresponds to. I'd personally change both sensors and the wire.
What usually causes a bad KS is water getting in behind the engine, under the intake.
There's a TSB, but the fix is to replace the sensors and wire, create a silicone dam around the sensors, and remove the foam square under the intake.
What usually causes a bad KS is water getting in behind the engine, under the intake.
There's a TSB, but the fix is to replace the sensors and wire, create a silicone dam around the sensors, and remove the foam square under the intake.
#6
TECH Addict
Join Date: Jun 2002
Location: Las Vegas, NV
Posts: 2,428
Likes: 0
Received 0 Likes
on
0 Posts
That's not throwing parts at a problem. Your computer is telling you the KS is hosed. I've never heard of anyone getting a false KS code. This is a very common problem; there's a TSB for it. And it's just plain smart to change out both knock sensors while you have the intake off, and throw in the wire too because it's very difficult to remove the wire without damaging it.
#7
Launching!
iTrader: (10)
Join Date: Jun 2005
Location: Rochester, NY
Posts: 244
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by Sunset'01Z
is there any way to test the sensor and make sure it's bad before i replace it?
Trending Topics
#8
TECH Fanatic
Thread Starter
iTrader: (10)
Join Date: Apr 2006
Location: Fort Worth, Tx
Posts: 1,340
Likes: 0
Received 0 Likes
on
0 Posts
thanks guys. i looked up the tsb on all-data and i did the job today. it took about 6 hours, but i'm not finished. in the process of putting it all back together, i somehow got the MAP sensor setting a code. replacing the sensor fixed my problem though. now i just have to figure out why my map sensor is reading 0.02 volts on the scanner. maybe i forgot to plug it in Oo lol. soo ya that's what i'm going to be doing tomorrow. i hope i dont have to take the manifold back off......