Post by
Project240 »
https://forums.nicoclub.com/project240-u5974.html
Tue Oct 14, 2008 7:00 am
My car runs absolutely terrible. It starts up fine, and then within several seconds, the idle drops to almost nothing, just barely enough to stay running. Sometimes it stalls out. Once it warms up a little bit, the idle stabilizes around ~850, but it's still a little unstable, warbling around a bit. If I give it any gas before it's fully warmed up, it stumbles a little, threatens to stall out.
Once it's warmed up and I'm driving, I only get to ~2K before it starts stumbling so bad I can hardly accelerate. Any load at all causes it to start sputtering and bucking. It takes ~30 seconds to limp it up to 55mph.
I pulled ECU codes, and got 34, for the knock sensor. I pulled the sensor and it looks perfectly fine. I used a multimeter to check the sensor, check continuity in the wiring all the way to the ECU...everything checks out fine. The FSM, at this point, says to check the ECU pins for damage (which there isn't), erase codes, and take a test drive. I'm going to do so, but I just can't imagine the thing running any better since I didn't find any issues.
SetupS14 T28 @ 10psi, Walbro pump, FMIC, stock ECU/injectors/MAF, 3" turboback, new NGK BKR7E V-power copper plugs
It's an S13 convertible, with an S13 blacktop, #62 ECU. I never use anything less than 92-93 octane.
What's up? I know that ECU codes for one thing will sometimes get tripped by something else. Is there anything jumping out at you that might be wrong with my car that would trip code 34?
Is it possible the ECU code got tripped for some reason, so the car now thinks the knock sensor is bad and is constantly pulling timing, and it'll run fine once I clear the codes?
IN SHORT: Why am I throwing a knock sensor code when there's no problem with the knock sensor?
Please, chime in, I'm at a loss here.
Modified by Project240 at 1:25 PM 10/14/2008