Hello all,

Not long ago, our Excursion shut down when my wife started driving home from work. Of course I was out of town. My son showed up with a borrowed Snap-On scan tool, found a P0232. Cleared the codes and it fired up and drove home.

I had seen some radiator fan clutch codes in the past, and read somewhere on this forum if the fan clutch is dying then it can throw the P0232 code and the PCM will shut everything down if it sees a short to protect itself. So I unplugged the radiator fan clutch and it ran with out issue for weeks. I replaced the fan clutch with a new Motorcraft, and while there water pump and thermostate. Hooked everything up and it again ran fine for almost 2 weeks including a trip. Then randomly one day it didn't start, P0232 along with B1352, B1876, & B1865... cleared the codes with Forscan and it started. Happened again but didn't have my lap top, so I grabbed the SCT in the glove box, tried clearing codes, no dice. Re-installed the tune, and then it started back up.

I have one step bigger injectors and also did the stand pipes and nipple cups one that install, a new FICM with a Tune in it, the PCM is tuned (actually for Eco), with a Stage 1 turbo, it has a FASS fuel system with the relay power wire connected to the old HFCM black/pink wire to energize (was hoping the PCM would see this and think the old fuel pump was there and also keep some of the factory features like it turning off after 20 seconds with key on engine off), new alternator, new big battery cable kit, have gone around to all ground wires I can find and have made them true metal to metal (that did make a big difference). The IPR is about 1.5 years old, blue spring kit, mean green starter.

For two days it would not start. Yesterday evening it did and ran smooth, even stopped in random parking lot and shut it off and it refired without issue. Forscan only had B1352, B1876, & B1865. This morning it would not start. Even for the heck of it tried disconnecting the new radiator fan clutch and still no dice. So after a lot of messing with it and checking the wire loom for any areas that might look like they are shorting (I stripped back one area that looked the worst just to find nothing). I was crawling around under it and had left the key on and while I was under the transmission pan I could hear an electric humming. I thought maybe it could be a neutral safety switch. Tried starting in every gear and in neutral and it would only crank in neutral but not fire. Put it back in park and cranked it again and on a slightly longer than normal crank it fired up. It was running smooth and sounded all normal, then about 45 seconds later it shut off. Using Forscan I now have P2617-P, P2617-60, B1352, B1876, & B1483. I am just at a total loss. Any help would be really appreciated.

 

We need live data of Whats happening in no start situation to help troubleshoot this

The cam/crank p2617 code can be thrown code for excessive crank. Or indicate other issue Need live data here to rule in or out

P0232 [Voltage present at the Fuel Pump monitor circuit when it has

NOT been commanded "on" for more than 1 second.]

with you factory harness modified maybe cause here for code
does it have good fuel pressure at all time it does run sometimes so maybe this one not high priority IDK it’s modify system

with limited info given thus far I’d start here
B1352 ignition key circuit failure from google I don’t have access to my info on this maybe others can chime in

 

I will be happy to supply that information, just need to know what data you need.

B1352 has been there for a while and I believe it is related to the key in ignition door open chime. It's tied back so it doesn't short. Wish I could find the OE part to fix it.

 

It would be best to go thru Marks thread here
https://www.ford-trucks.com/forums/1...g-process.html




but here are a couple screen shots from @Bismic thread on trouble shoot of soma data needed at time of no start events

 

what do you mean it’s tied back is it modified

is there an open circuit in that system

I can’t see the exact condition that sets this code

waiting for others to chime in

 

Ok, I will work on getting all the data tomorrow morning.

Quite a while ago, when we first got this vehicle in 2024, this was an issue and chiming all the time. When I pulled off the steering column covers the wire had broken off the plastic tab and was randomly touching metal. There was no way of reattaching it, so I had to zip tie it in a position on the steering column under the covers so it wouldn't touch anything and chime. But maybe the B1352 code isn't related to that... ?

 

Here is all the information, I believe I selected all of the correct data parameters on Forscan.

2005 Ford Excursion Limited 6.0l Powerstroke 4X4
308k miles
I cranked it so many times yesterday I put it on the charger this morning. It wasn't dead, but the last crank I could hear it slowing. So batteries were at 100%. Both batteries are a little over 1 year old and they are AGM.
Oil level is where it's supposed to be, only about 2k miles on it. Change it quite religiously every 5k with OE filter and filter cap. Schaeffers OTR Plus 10w-30 full synthetic.
Forgot to mention it does have the Bullet Proof Oil Cooler with the Air to Oil cooler mounted up in front of the condenser.
I just performed the air bubble test with the secondary fuel filter check valve held open, key off engine crank. Fuel level was covering the top of the check valve. Performed the test twice with about a 20 second crank. No bubbles.

Of course it fired right up today when I tried to pull data while cranking, and it ran smooth for about 5 minutes before I shut it off. Here are links to the videos, please let me know if they work or not:




This is a screen shot of the live data while it was running.


I performed the Key On Engine Off Forscan data log, this is a screen shot of the live data while engine is NOT running and before it started.










These are the DTC present in the PCM after it started and ran for about 5 min. Didn't want to clear and re-pull anything until I hear from you guys.

 

This morning it started right up, idled smooth and normal for 10 or 15 minutes. Here are some screen shots from Forscan.

I will go for a drive later today after work and see if anything changes. I might have a connection to a career Ford mechanic who loves 6.0's and has access to the dealership scan tools... fingers crossed that call comes through.



I shut it down, cleared the codes, and reread the DTC's, this is what I have now, only B1352 & P1876

 

I found more pictures I took of the DTC codes from Dec 28th to Dec 30th. So just as this thing was starting to act up. I've searched and many results say Cam Shaft and/or Crank Shaft Position sensor(s), others say the PCM. It started again this morning and idled for a good 10 minutes as smooth as could be. I get sensors going in and out, saw it plenty with our old factory manufacturing equipment, but a PCM, if it's like a machine control logic, or a computer dead is dead. Any thoughts?

 

Throwing lots of codes

live data look ok
Need it to act up for live data capture

instrument cluster can cause problem I don’t have access to compleat DTC list for u code

 

Yes, it threw a lot of codes! I know I need to data monitor it when it faults, trying to make that happen.

In the meantime, because we desperately need this running, I am throwing parts at it ... ordered Motorcraft Crankshaft and Camshaft sensor, Standard Motor Products Transfer Case Motor, and because it's all that's available now a Dorman 4WD Vacuum actuator. The Transfer Case 2wd short needs to be fixed anyways, and 300k miles on those to critical sensors is good in my book so time to replace them.

Earlier this year I sent the CJB, Instrument Cluster, and the Overhead Monitor into FICMRepair.com and they fixed the CJB and the Overhead Monitor, they checked the Instrument Cluster and it checked out ok. Not saying that it couldn't have gone bad since then, but you'd think it'd be ok.

 

On the surface it sounds like either a PCM power issue or an electrical issue in the crankshaft sensor circuit.

The best data for us to watch is cranking data when it won't start.

 

Well might be worth throwing a pcm power relay at it or swap with another relay just to speed up the process

 

I will keep trying to get it to fault and then grab that live data while cranking. I would love to know for certain what the issue is and report back.

If it were a PCM power relay, wouldn't the gauges all jump or go flat when it drops out because the PCM would go offline? Would it even crank? When it would crank and not fire, all gauges were/are active. Oil pressure jumps up after a bit of cranking, fuel gauge reports accurate level, etc.

 

Yes there is pcm power relay could be getting flakey