FleshThorn

Same problem here with an 87, 22RE. I am getting continuity from ks connector to ECU, replaced ks with another one from a junker. Seems to take a little longer for the code 52 to turn the check engine light on, but code 52 is still there. I really don't have the cash for a new ks at the moment and I have my doubts as to if that will fix it after everything I have read.

yeehaw1

Well, i don't know the codes off the top of my head, but I'm assuming it's the 52 your talking about, and I've been pulling the ecu/knock sensor codes for a while now, 87' 22re motor, motor seems too be running fine, no pinging/knock, so I've kind of ignored it, what exactly is this code good for anyway, what's the fix and what exactly is your truck supposed to do different while this code happens? Light dosent come on till I roll down the drive a ways.

FleshThorn

Code 52 is saying that you have a bad knock sensor or circuit. The ECU then retards the ignition and your engine is not running as strong as it should be. Have you noticed that it seems a little sluggish pulling up hills ? Mine also is not running so bad that I can not ignore it, but then again this has been a problem since I bought it this past Winter and I don't know how it is suppose to run.

yeehaw1

me and you seem to be in the same boat then, uphill has always seemed a lil sluggish, but it's a 4 banger. I got my truck last November and it's been throwing this code since a couple weeks into December or January. I'm not real sure how it's suppose to run either, but yeehaw will run with no problem down the interstate. Thanks for the explanation as to what the ks is supposed to do to.

bob hennig

Many times not sensor but lies in bad wire, wire is shielded to prevent external intrusion of voltages, emf's. Bypass wire back to the computer with new shielded wire and attach to KS direct. Ground the shielded part of wire to good ground near computer. No continuity between shield and ks wire, good continuity between shield and ground, good continuity between KS terminal and conputer terminal. The 22 r is simple to get to, the 3.0 is under intake injector manifold, a real pain. Eliminates that problem. Just might be your fix.

blake.nemitz

your ecu cannot retard the timing enough if the base is 25*,factory is 8*, try settin at 10-12 btdc with your jumper and clear the codes, i bet it wont come back on.

FleshThorn

Some good info in this thread for understanding the knock sensor and code 52: https://www.yotatech.com/forums/f116...thread-216933/

cowb0y

I too am experiencing the same symptoms. Sluggish up hills, slow to accelerate, decreasing gas mileage (15 mpg). I recently changed the timing belt, waterpump, thermostat, and 02 sensor all within the last couple of weeks. Adjusted timing, which was a bit off, but now at 10 btdc. After last timing adjustment, my rig threw code 52. Gonna look into the tps, but afraid its the k/s since I do hear a ping but if I up the idle (~1100 rpm) and timing (12 degrees-ish), then ping goes away. Whachu guys think, is the ping a dead mark? or Can a fella work with this problem on a budget?