FCSP Software Version 2.500.34-ford.27+26-08

[abcut973]

To be clear, I don't know 100% if this is a separate issue, or one that's caused BY this.

What I do know is that my unit stopped working over the weekend while the OTAs were rolling out, and my logs show that it had multiple 'failed' downloads.

I'm running 2.112.125:0.0:0.0:0.0 on the outside unit that stopped over the weekend.

The inside unit I repaired today is now running 2.12.125:3:15:3:15:3.15

Those are both BEFORE the problematic OTAs, so maybe my issue saved me?

Ok.
Mine is already at 3.15 since last year OTA.

Sponsored

 

[Aminorjourney]

Ok.
Mine is already at 3.15 since last year OTA.

Hmm.

I'm currently imaging the disk so I can work on it remotely from the unit - but I will also leave my bench system attached with the hope it actually *does* do the OTA update.

 

[TaxmanHog]

I wonder if the recent OTA to the FCSP has been suspended?

 

[Jim Lewis]

Given how consistent it is, I strongly suspect this is the root cause behind a large share of the "unit stopped responding" reports in this thread over the last few years — not a WiFi bug, not an app bug, a disk-full bug wearing a dozen different disguises depending on what happens to try writing at the wrong moment.

Great discoveries by you and @cjueden. I think it's good you qualified your estimation as "a large share of 'the unit stopped responding' reports," as other snafus with the FCSP may exhibit similar symptoms. Around April 2024, I lost both Wi-Fi connectivity and BT broadcasting from my FCSP. A hardware FCSP reset restored Wi-Fi; a software FCSP factory reset through the FordPass app restored FCSP BT broadcasting, but I couldn't repair the FCSP with my truck until I factory reset my truck! https://www.f150lightningforum.com/...y-for-truck-fcsp-bad-behavior-problems.19650/

As reported in this thread, on 8/7/26, I seem to have gotten an earlier FCSP firmware update version than anyone else (5.2.2 rather than 5.3.6). I lost charge derating but not Wi-Fi connectivity. The same situation continued on 8/8 when I got firmware update 5.3.8, slightly newer than the standard issue 5.3.6. But just this Tuesday, 8/11, still on 5.3.8, I got a Connection Lost notice and couldn't connect to my FCSP either through the Ford app or the Ford CSP Pro Setup app, even though the FCSP SSID was showing in my iPhone Wi-Fi settings. So I turned off all power to my FCPS, including the HIS unit and its Dark Start battery, and let the FCSP sit for 74 minutes. Within 2 min after rebooting, the FCSP broadcast its SSID. I could connect to it via the CSP Pro Setup app (the Ford app initially gave Connection Lost). But a minute or two later, I could derate the charging current to 24A, change the charging time window, and see that the FCSP was charging at 5 kW as requested. When I tried the Ford app 40 min after the reboot, it connected to the FCSP and had it reporting "Ready to Charge."

So, the state of my FCSP might be something interesting to investigate via your techniques, @Aminorjourney, but right now, I'm just happy to have it working, and hope that your and cjueden's findings encourage Ford to do some heavy lifting and clean up their mess, and save us all a bunch of future frustration and time wasted messing around with our FCSPs.

 

[Aminorjourney]

Great discoveries by you and @cjueden. I think it's good you qualified your estimation as "a large share of 'the unit stopped responding' reports," as other snafus with the FCSP may exhibit similar symptoms. Around April 2024, I lost both Wi-Fi connectivity and BT broadcasting from my FCSP. A hardware FCSP reset restored Wi-Fi; a software FCSP factory reset through the FordPass app restored FCSP BT broadcasting, but I couldn't repair the FCSP with my truck until I factory reset my truck! https://www.f150lightningforum.com/...y-for-truck-fcsp-bad-behavior-problems.19650/

As reported in this thread, on 8/7/26, I seem to have gotten an earlier FCSP firmware update version than anyone else (5.2.2 rather than 5.3.6). I lost charge derating but not Wi-Fi connectivity. The same situation continued on 8/8 when I got firmware update 5.3.8, slightly newer than the standard issue 5.3.6. But just this Tuesday, 8/11, still on 5.3.8, I got a Connection Lost notice and couldn't connect to my FCSP either through the Ford app or the Ford CSP Pro Setup app, even though the FCSP SSID was showing in my iPhone Wi-Fi settings. So I turned off all power to my FCPS, including the HIS unit and its Dark Start battery, and let the FCSP sit for 74 minutes. Within 2 min after rebooting, the FCSP broadcast its SSID. I could connect to it via the CSP Pro Setup app (the Ford app initially gave Connection Lost). But a minute or two later, I could derate the charging current to 24A, change the charging time window, and see that the FCSP was charging at 5 kW as requested. When I tried the Ford app 40 min after the reboot, it connected to the FCSP and had it reporting "Ready to Charge."

So, the state of my FCSP might be something interesting to investigate via your techniques, @Aminorjourney, but right now, I'm just happy to have it working, and hope that your and cjueden's findings encourage Ford to do some heavy lifting and clean up their mess, and save us all a bunch of future frustration and time wasted messing around with our FCSPs.

Thanks for the encouragement, and good to know it's not everyone.

I've forwarded my bug report to Ford, and I've made a copy of the disk image, so I can at least work with it offline. Watch this space!

 

[Zprime29]

I tried upping my charge rate to 60A. It says it saved in the app but it does not appear to have taken. I'm still charging at 40A. I'll try adjusting again after I get a chance to reboot. Perhaps it's a one and done per boot.

 

[cjueden]

The app doesn't verify the settings took. It sends the command to Ford's OCPP server but doesn't make it to the charger sometimes. You can try again by going one up or down in the app and hope it catches. So long as it's not the max rated amp or 37% of it. There's a bug in the firmware for those settings.

 

[TaxmanHog]

I tried upping my charge rate to 60A. It says it saved in the app but it does not appear to have taken. I'm still charging at 40A. I'll try adjusting again after I get a chance to reboot. Perhaps it's a one and done per boot.

The app doesn't verify the settings took. It sends the command to Ford's OCPP server but doesn't make it to the charger sometimes. You can try again by going one up or down in the app and hope it catches. So long as it's not the max rated amp or 37% of it. There's a bug in the firmware for those settings.

I might have done a reboot, or just hit the lottery on the request posting.

{didn't hit the PowerBall big time last night but did walk away with $8}

 

[tearitupsports]

It is interesting to me that the one piece of equipment that has been rock solid for me has been the FCSP. I have never had connectivity issues or problems like everyone else.

The two possible reasons are that I have always had it dialed down to 64A or below using the hardware limit.

I also have it networked such that it always receives the same IP address from the router. That address is also in a different part of the subnet which is not used for the random DHCP addresses. I am wondering if a changing IP address is what is causing the stations not to work, or then suddenly start working correctly again. I also have no chance of duplicate IP's in my scenario.

I have noticed forever that if I set a lower charge rate in the app it would work immediately. If I tried to raise it back up, it would never work until power cycling the station. The new setting would be active immediately after the power cycle.

 

[Zprime29]

I have noticed forever that if I set a lower charge rate in the app it would work immediately. If I tried to raise it back up, it would never work until power cycling the station. The new setting would be active immediately after the power cycle.

That's an interesting observation. I'll experiment a little tonight before I reboot.

 

[TaxmanHog]

I also have it networked such that it always receives the same IP address from the router. That address is also in a different part of the subnet which is not used for the random DHCP addresses. I am wondering if a changing IP address is what is causing the stations not to work, or then suddenly start working correctly again. I also have no chance of duplicate IP's in my scenario.

Using 80 amps as my default has been fine, and I also reserved the IP on my network for my FCSP, well until recently experimenting with this recent problem.

Otherwise my unit has be very reliable.

 

[K6CCC]

I also have it networked such that it always receives the same IP address from the router. That address is also in a different part of the subnet which is not used for the random DHCP addresses.

All of my known devices have DHCP reservations in my route so my FCSP is always 192.168.206.192. My 206 LAN is all IoT type devices (mostly cameras and power control devices).

Sponsored