Random sputtering / hesitation
Thread Starter
|
More Turbo
Joined: Nov 2011
Posts: 508
Likes: 0
From: PNW
Random sputtering / hesitation
So my '01 7.3 has 137k on it - no chip. After about 450 trouble-free miles of desert driving and mountain roads two days ago I took another run (about 150 miles). Stopped for about 3 hours, hit the road and about 20 miles into the drive I stopped for a light and on takeoff I got to about 20 mph and started getting big time sputtering, cylinders not firing, black smoke puffing, major power loss. so I pedaled it until I could get to full throttle and it just pulled out of it.. 210 miles with no issues since. Anybody had this happen before? Any ideas? My buddy added RBP fuel addictive to the truck right before the last 20 mile run, full tank at the time.. I find it hard to believe that the additive would have done it, but?
Junior User
Joined: Jul 2014
Posts: 55
Likes: 0
I'm working on diagnosing similar, but much more frequent issues. Some things you could check:
ICP Sensor. An easy check; located on front end of drivers side high pressure oil rail. I understand that if there is oil in the electrical connector the sensor should be replaced and the connector cleaned with brake clean.
Did your SES / Check Engine Light come on? If it did (even if it turned off again), you will have one or more DTCs stored. P1316 is common and means the IDM has codes stored. It takes more than a basic scanner to get the IDM codes. FORD can do so, of course. AutoEnginuity with Ford package can too. Don't clear codes without retrieving the IDM code(s) via a KOEO test.
Have you had the CPS recall done? I don't know much about this one and am not sure if it's likely to be the issue for a once off like you had there.
ICP Sensor. An easy check; located on front end of drivers side high pressure oil rail. I understand that if there is oil in the electrical connector the sensor should be replaced and the connector cleaned with brake clean.
Did your SES / Check Engine Light come on? If it did (even if it turned off again), you will have one or more DTCs stored. P1316 is common and means the IDM has codes stored. It takes more than a basic scanner to get the IDM codes. FORD can do so, of course. AutoEnginuity with Ford package can too. Don't clear codes without retrieving the IDM code(s) via a KOEO test.
Have you had the CPS recall done? I don't know much about this one and am not sure if it's likely to be the issue for a once off like you had there.
Thread Starter
|
More Turbo
Joined: Nov 2011
Posts: 508
Likes: 0
From: PNW
Thanks for the info, I am back at diagnosing this issue again. To answer previous inquiries about codes/lights I had none, and scanned it just to be sure something wasn't stored and there were no codes. Fast forward to yesterday the truck was warming up, I was holding the engine at about 700+/- RPMs and it died, just like turning the key off. I started it right back up without issue, and drove it home with no power loss or anything... Could this be the CPS? I've never changed it but most folks tell me its all or nothing with the CPS... suggestions or confirmation welcome, I've got one I picked up form Ford I'm going to install tonight but a little info from others to ease my suspense would be good.. I've got a trip this weekend and don't want it to leave me out in the woods.
Thread Starter
|
More Turbo
Joined: Nov 2011
Posts: 508
Likes: 0
From: PNW
I was hoping someone would say that, I read on another forum (with less trustworthy info) of such behavior from the CPS but I wanted to hear from the FTE guys first. I'm going to swap it and see. This may be unrelated but the truck also takes a bit longer to start than my OBS.. never rough starting just takes more cranking. is there such a thing as weak cps signal?
Hotshot
Joined: Jan 2011
Posts: 18,849
Likes: 179
From: Puget Sound
The CPS signal won't be weak - it's digital in nature. It can, however, skip beats - intermittently at first, then just die.
Another possible cause - bad connection with your UVCH, but this usually throws a SES light. You can test it with the UVCH link in my signature.
Another possible cause - bad connection with your UVCH, but this usually throws a SES light. You can test it with the UVCH link in my signature.
Thread
Thread Starter
Forum
Replies
Last Post
