2002 OBDII codes
TECH Apprentice
Joined: Aug 2018
Posts: 383
Likes: 108
You probably have an intermittent misfire and haven't noticed it. You need to hookup a scanner that has misfire counts to see what cylinde(s) are missing.
Same thing with the knock sensor code. I think that one will cause the ECU to pull timing a bit or something if it detects knocking. There's a way to check the knock sensors with dvom and striking the engine block with a large screwdriver and hammer. I found a video and it to my truck a while back. Either knock sensors and/or wiring harness are usually the problem.
TECH Fanatic
Joined: Aug 2006
Posts: 1,407
Likes: 63
From: Knappa, Oregon
johnfin1, you have previous posts about the same issue of random misfires. One mentions the misfire being on cylinder #4, did you change the plugs, the coil, and check out the fuel injector on #4? Because most of these kind of misfire codes will lead you back to: New plugs, new wires, and changing or moving the coil to try to determine if it is faulty. Your knock sensor code is likely a result of the computer trying of compensate for not running on all cylinders all the time.
Thread Starter
Teching In
Joined: Jan 2022
Posts: 22
Likes: 3
Yea, it was #3 but now it just general. Car runs and performs perfect. I have an actron CP9580 which does a ton of checks, dynamic too, but I dont see any feature for individual firing check. Is there a cheap scan tool that can do that? What about a strobe light?
