Search the Community
Showing results for tags 'crank sensor'.
I have a 1999 s10 blazer with a 4.3 motor i'm putting in a 2002 4.3 motor and the crank sensor whole is different what can i do? Are there any other differences i know about as well?
My 99 with 5.7L is really hard to start when it has been sitting for a few days (usually at least 3 days). It cranks over, but seems to run into resistance each time around. If I crank and hold it for about 5-10 seconds, it will fire, but what seems like only on a couple of cylinders, then dies. Sometimes, it seems to backfire. If I keep trying, It *does* eventually start (just the other day, I think it took about 20 tries over a few minutes to get it to start. Once it starts, it runs rough for about 10 seconds, then runs fine. I've checked the fuel pressure and it's fine (about 60 PSI), even after sitting for a few days. If I drive it for at least 10 minutes, it will start fine the next day. If I let it idle for 10 minutes, it's not enough to make a difference the next day. One of the weirdest problems I've ever encountered, for sure! When driving it daily, or maybe letting it sit for one day, it starts right up with the normal crank time. After talking with another mechanic, we were thinking it could be fuel leaking from the FPR into a cylinder, or two. My gas mileage was down, too, so we replaced the FPR (and the spider injector assembly, as well). We found evidence of leaking fuel, but it didn't fix the hard start problem. The mechanic that replaced the FPR/spider injection was talking with a buddy and suggested it could possibly be the Crankshaft Position Sensor (mentioning that there was a TSB for that sensor; though I haven't been able to find it). The thinking is that if the crank sensor is not working right, it could be throwing the timing way off and trying to fire at the wrong time. I've been having this problem for the past 3 years. Has anyone else had this kind of problem? Does it make sense that a crank sensor could be the cause? I've tried throwing parts at problems, before, and I can do that again, but I know it's always better to diagnose. However, this one seems pretty hard to diagnose and it sets no codes when it happens.