Intermittent no start 6.0
Issue: Intermittent crank no start.
Started, ran, drove fine 40 miles with one stop. 45° and raining. 10 hours later, 55° and still raining, crank no start. Got towed.
At time of failure: (stats taken after multiple attempts)
While cranking:
- FICM in sinc
- FICM main power: 47.00
- FICM logic power: 11.00
- ICP: 194
- ICP voltage: 0.43
- IPR duty cycle: 85
- Battery voltage: 10.5
- Engine oil temp: 67
- Coolant temp: 72
- Low pressure gauge normal
Next day, about 21 hours later, 55° and clear. Charged the main battery just to replenish from yesterday. Fired up and ran normal. Scan Gauge went dark while cranking so the following stats are at idle. Crank time was normal.
- FICM in sinc
- FICM main power: 47.5
- FICM logic power: 11.5
- ICP: 1375
- ICP voltage: 1.4
- IPR duty cycle: 35
- Battery voltage: 12.0
- Engine oil temp: 56
- Coolant temp: 55
- Low pressure gauge didn’t kick up until after the truck was running which is also when the Scan Gauge lit back up.
After idling a few minutes:
- FICM in sinc
- FICM main power: 48.00
- FICM logic power: 13.5
- ICP: 907
- ICP voltage: 1.03
- IPR duty cycle: 24
- Battery voltage: 13.7
- Engine oil temp: 91
- Coolant temp: 113
- Low pressure gauge normal
Oil level is correct. Oil mileage less than 3000. Electrical connector on ICP clean and in good shape.
what do y’all think?
Issue: Intermittent crank no start.
Started, ran, drove fine 40 miles with one stop. 45° and raining. 10 hours later, 55° and still raining, crank no start. Got towed.
At time of failure: (stats taken after multiple attempts)
While cranking:
- FICM in sinc
- FICM main power: 47.00
- FICM logic power: 11.00
- ICP: 194
- ICP voltage: 0.43
- IPR duty cycle: 85
- Battery voltage: 10.5
- Engine oil temp: 67
- Coolant temp: 72
- Low pressure gauge normal
.
.
.
what do y’all think?
The ScanGauge is not the best code reader, so you might pull a helpful code with a scan tool like FORScan.
Maybe time for an air test (two ways to do it, each with their own specific benefit): through the ICP port or through the IPR port.
I forgot to mention no check engine light, no stored or pending codes. I mostly use the scan gauge just for gauges. Haven’t owned it or the truck long enough to need the scan capabilities, but it’s all I got.
I’ll pull the ICP/IPR and inspect when I get a chance and let everyone know.
The most common code for intermittent issues with the high pressure oil system is P2623.
Anyway, a sticking IPR can also do what you described.....problem is in identifying it. The first clue though would be a hole in the screen.
Been waiting on Ford to get the IPR screen/O-ring set in before tearing into it (had to order).
In the meantime, it’s been starting fine except for once. This time, no low oil pressure. SYNC, FICM, etc. as before. Second attempt started with all systems running normal.
Had to wait for Father’s Day weekend to pass to buy 12mm hex socket and smaller magnet to check pressure relief valve. No one has that O-ring in stock so I’m not sure if I want to pull it.
Did some digging:
5 years, 7 months, but only 12,493 miles ago had the following replaced according to records:
High pressure oil pump
IPR
IPR and exhaust sensor?
Oil change
Any new theories?
Also I could use the torque values for:
IPR
ICP sensor
Oil pressure relief valve
And anything else I have to remove to access what I’m trying to inspect/replace.
Long story short:
Scan Gauge III showed about 25°-45° split in coolant to oil temp. That spurred the oil cooler replacement, head studs, EGR cooler, coolant filter, plugs and standpipes. Once you’re in, keep going right? But absolutely nothing to do with the no-start condition.
Oil temp is fine now.
With Confidence high I set out camping, then no start 6 hours from home with no cell service. Jiggled IPR wiring for restart. Replaced pigtail and haven’t had a no start issue since.
Learning a lot along the way. Sometimes (usually) it’s the simple things.
Trending Topics
Ford Trucks for Ford Truck Enthusiasts
Just to re-emphasize "for posterity", I will put a recommendation in again for FORScan. It does SO WELL pulling codes! Issues with the IPR wiring or actuator (electronics) are pretty good at throwing codes and the ScanGauge has never excelled at code reading. I have a ScanGauge II and like it, but it was always hit and miss" on codes. Food for thought.









