When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
While driving to work yesterday on the highway, I noticed the SES light on. It stayed on for a minute or so and then went off.
When I got in the car after work, it didn't start right up as usual - I had to leave the engine cranking for a few seconds before she weakly started up.
On the way home, again on the highway, she experienced a sudden surge for about a half a second and the SES light came on again and stayed on for a minute or so. No other problems last night except for another hard start after the grocery store.
I hooked up Datamaster to her tonight after driving my Jeep to work today, and there were no DTC's set. I drove for a half hour or so and didn't get the SES light at all, but I did notice the ASR lights and the AECC Off light blinking at me (se other threads.)
I'm going to run Datamaster on the way into work again tomorrow but until then, any ideas?
Well, I found the cause of this. The ECT sensor that feeds the computer (and digi-dash,) is intermittenlty sending false signals of negative temperatures.
Since I just installed a 160 stat a few days before this started, I'm going to reset the ECM and if that doesn't do it, replace the sensor itself. Which one is that anyway? The one in the pump housing?
Fuel pump loses power - no gas - engine stalls - SES light comes on. Car is hard to start until the fuel rail is re-primed. Plugged fuel filter could cause the same symptoms. I'd check fuel pressure.
It doesn't - that's a different problem. I was responding to your issue with a a check engine light, no codes, apparent stall & difficult to start - to me, it sounded like you ran out of gas; not literally of course.
I think that's the only problem as the fuel filter and fuel pump are relatively new. The ECM is trying to adjust the AFR based on the false ECT reading and that's what's causing the hesitation and the jump to open loop when it gets the false reading for too long. Since I first posted this, I saw the behavior in action and caught the code (that didn't get stored for some reason) when Datamaster logged it.
So post the code - should be a 14 or 15 if it's in the coolant temp circuit & the code would stay in history for 50 ignition cycles. Someone should be able to help.