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

[TaxmanHog]

Dang. I'm sorry.

Just as a reminder: folks - consider not upgrading - and consider locking your FCSP from your Internet.

I'm still hoping to get a fix for this block, but it's not *looking* good

Do you think Siemens might have an ability to individually back-door the compromised FCSP's and apply a fix unit by unit, or is physical intervention the only solution at this point for those devices that got the malformed update and broke functionality?

Sponsored

 

[tearitupsports]

This is such a wierd issue. I am not having any issues at all with the new firmware. I can easily connect to the FCSP still. It sounds silly, but has anyone rebooted the home router to flush out the DHCP table and let the FCSP try and reconnect? There is a piece to the puzzle we are all missing, because the firmware itself is not inherently broken for all, but it certainly doing something in a lot of people's systems.
My Wifi settings are below.

2.4 GHz
Network Name (SSID)

Authentication Method
WPA2-Personal

WPA Encryption
AES

 

[TaxmanHog]

This is such a wierd issue. I am not having any issues at all with the new firmware. I can easily connect to the FCSP still. It sounds silly, but has anyone rebooted the home router to flush out the DHCP table and let the FCSP try and reconnect? There is a piece to the puzzle we are all missing, because the firmware itself is not inherently broken for all, but it certainly doing something in a lot of people's systems.
My Wifi settings are below.

2.4 GHz
Network Name (SSID)

Authentication Method
WPA2-Personal

WPA Encryption
AES

I've gotten an entirely new router from xfinity since this issue, it was a routine equipment upgrade, new device has 2.4, 5 and 6 ghz transceivers. But I'm still unable to login, my device does charge, but no more stat's, a factory reset might not even work based on Nikki's prior observations.

 

[TaxmanHog]

All that said, my expectations

Replace or repair my FCSP free of cost.

 

[Jim Lewis]

I am not having any issues at all with the new firmware.

TL;DR: Ford has issued its final FCSP update. Ford saves on server electricity bills. We get slightly less telemetry data.

Update: I discovered, perhaps because of the firmware update, my FCSP got connected to a different, distant mesh router on my LAN and was on its 5 GHz band. So I changed my router settings to constrain the FCSP to 2.4 GHz and to connect to the TP-Link Deco mesh unit just on the other side of the garage wall from the FCSP. The Deco app shows the FCSP now has a very strong Wi-Fi signal. Still getting Connection Lost to Ford Servers, and tried again to change my charging rate. No can do now, so the Ford server connection must be essential for derating charging current.

One thing I'd be curious to know, @tearitupsports. If you call up the Charge Station via the menu item in the Ford app on the Charging Tab, does it say anything there other than "Connection Lost?" And, perhaps you haven't tried it yet, but can you also successfully edit the charging rate to something less than 80A?

I haven't tested whether the HIS backup ability has changed yet. But in every other aspect, my FCSP appears to be functioning normally after the upgrade to firmware version 5.3.8. I can charge at 24A. I can access the FCSP via the Ford Charge Station Pro Setup app. My interpretation of the "Connection Lost " message I get in the Ford app is that the Ford servers just aren't running or aren't reachable by my FCSP for some external reason, since I can clearly access my FCSP over my own LAN.

A cynical view might be that, with a final firmware update, Ford has decided it's over and done with the FCSP and there is no point in running servers to get telemetry from the FCSP on charging. That's all that's going to be done by the truck now. The Ford app Charging History reports kWh delivered to the truck. Only geeks care about the corresponding kWh consumed by the FCSP in the process. And maybe in L2 charging, when you change the charging rate, it's actually the truck that gets the derating and tells the FCSP through PLC what to deliver; i.e., the hardware charging rate is set by the FCSP dial, but the software charging rate is determined by negotiation with the truck. Does anyone know for sure if the FCSP actually has the software rate setting (or why is it only accessible through the Ford app and not the Charge Station Pro Setup app)? (Looks like when I initially derated my FCSP, I had a Ford server connection, and now I don't, so I can't change the rate now).

 

[TaxmanHog]

TL;DR: Ford has issued its final FCSP update. Ford saves on server electricity bills. We get slightly less telemetry data.

Update: I discovered, perhaps because of the firmware update, my FCSP got connected to a different, distant mesh router on my LAN and was on its 5 GHz band. So I changed my router settings to constrain the FCSP to 2.4 GHz and to connect to the TP-Link Deco mesh unit just on the other side of the garage wall from the FCSP. The Deco app shows the FCSP now has a very strong Wi-Fi signal. Still getting Connection Lost to Ford Servers, and tried again to change my charging rate. No can do now, so the Ford server connection must be essential for derating charging current.

One thing I'd be curious to know, @tearitupsports. If you call up the Charge Station via the menu item in the Ford app on the Charging Tab, does it say anything there other than "Connection Lost?" And, perhaps you haven't tried it yet, but can you also successfully edit the charging rate to something less than 80A?

I haven't tested whether the HIS backup ability has changed yet. But in every other aspect, my FCSP appears to be functioning normally after the upgrade to firmware version 5.3.8. I can charge at 24A. I can access the FCSP via the Ford Charge Station Pro Setup app. My interpretation of the "Connection Lost " message I get in the Ford app is that the Ford servers just aren't running or aren't reachable by my FCSP for some external reason, since I can clearly access my FCSP over my own LAN.

A cynical view might be that, with a final firmware update, Ford has decided it's over and done with the FCSP and there is no point in running servers to get telemetry from the FCSP on charging. That's all that's going to be done by the truck now. The Ford app Charging History reports kWh delivered to the truck. Only geeks care about the corresponding kWh consumed by the FCSP in the process. And maybe in L2 charging, when you change the charging rate, it's actually the truck that gets the derating and tells the FCSP through PLC what to deliver; i.e., the hardware charging rate is set by the FCSP dial, but the software charging rate is determined by negotiation with the truck. Does anyone know for sure if the FCSP actually has the software rate setting (or why is it only accessible through the Ford app and not the Charge Station Pro Setup app)? (Looks like when I initially derated my FCSP, I had a Ford server connection, and now I don't, so I can't change the rate now).

My system is still pinging my network and feeding some form of data, but I suspect this limited operational data is populating via TELE-MATICS, ie. the "TRUCK" is saying to Ford App that the FCSP is showing [Transferring Power] status now because I charged last night after my return from Boston Medical Ctr.

I've charged each of the last five days , showing various operational condition like ready to charge, etc.

The FCSP no longer displays the white lamp status after unplugging, so the charging log data transfer is definitely not happening because of the hosed firmware, I hope Siemens or Ford have not powered down the receiving server.

 

[tearitupsports]

One thing I'd be curious to know, @tearitupsports. If you call up the Charge Station via the menu item in the Ford app on the Charging Tab, does it say anything there other than "Connection Lost?" And, perhaps you haven't tried it yet, but can you also successfully edit the charging rate to something less than 80A?

It still shows a valid status for mine.

 

[chl]

I think it was mentioned somewhere above, that a programming error resulted in the memory storage on the FCSP to fill up and not 'clear.'

With limited/no free memory space, things will stop working in computerized systems.

If a red button (on the mother board) factory reset clears the memory and frees some up for the system, perhaps things would work again...for a while until it fills up again.

But maybe the reset with the red button wouldn't clear the memory, and/or might make matters worse because we'd have to go through the whole setup process and that might fail, and we'd lose what little communication we have with the Ford app.

We'd be back to a dumb EVSE that will charge at the max the truck can handle or what the dial on the motherboard is set to, with no status updates in the app.

Yes, Ford and/or Siemens needs to fix these FCSPs or tell us how to DIY it.

 

[Jim Lewis]

Another TL;DR Post: My FCSP seems to be communicating with the Ford Mothership again.

After various manipulations described below, the orange "Connection Lost" status (unable to connect to servers) has gone away, replaced by the green "Transferring Power" logo that should only show when the truck is transferring power to the house (which it isn't). I have been able to incrementally change the power transfer rate several times: 24A->26A->34A->20A, and the Ford app responds by showing rates of 5.1, 5.3, 7, and 4.2 kWh, respectively. Also, when I go to Charging Station, Insights, Charging tab, the Ford app now shows a test energy transfer for 8/30/26, whereas previously, after the firmware update around 8/7/26, it would show nothing for a charging session until now.

I have the Ford AI assistant in my iOS version of the Ford app. When I asked it why I was getting Connection Lost, it urged me to check my network settings, and I discovered that after the firmware update, the FCSP had connected to a distant Deco mesh router at 5 GHz with a very weak connection vs. the 2.4 GHz the AI said was preferable (router and band connections had been on Auto settings). After selecting the closest mesh router on the 2.4 GHz band in my network app, I got a very strong Wi-Fi signal from the FCSP. AI advice was then to do a cold reboot of the FCSP with all power off for at least 10 minutes, then to set up the Wi-Fi connection again in the Ford Charge Station Pro app, and before doing this, to launch the Ford app and force-kill it so it had to start fresh once used after the new Wi-Fi pairing.

When I did all of the above, it still said Connection Lost in the Ford app for several hours, but then, just as I was about to show the wife how I'd been wasting my time, I noticed that Connection Lost was gone and I was getting the Transferring Power message for FCSP status, no mention of lost server connection, and the amount of an experimental test charge was now showing under Charge Station, Insights. And, hey, I can now derate my FCSP at will. I am not holding my breath that this is going to last into the future. But it works for now.

 

[TaxmanHog]

Only data point I have for August is 8/1

Actual Emporia data and FCSP KWH in black text is live data, while the RED text in the FCSP KWH column is interpolated at 99.2% of Emporia values, as has been the historic trends of the past.

 

[I <3 My Lightning]

@TaxmanHog and @Jim Lewis
Im still running the last firmware before these new sets. I have not allowed mine to update because when I am done charging, I disconnect the truck and I pull the plug... Yes mine is plugged in, search is your friend...

The ford servers are operational.
Here is my charge session from today... I'll report back after this next session is completed in about an hour.

Edit: Note the time stamps when the charge was completed and what was reported by the server. It was a lag. When I go back and look at the past recent charging sessions, the time stamps match when I completed and what/when is was logged.

 

[TaxmanHog]

The ford servers are operational.
Here is my charge session from today... I'll report back after this next session is done in about an hour.

This is great news, my FCSP has been damaged by the rogue firmware update, so I hesitate to block network access, shut it down between charging sessions or impede connectivity over and above its hamstrung condition presently.

I'm hoping that Siemens might still be able to fix this remotely, IF they have another way to connect to the system that is 'different' than the way us end user connect.

 

[Jim Lewis]

I have not allowed mine to update because when I am done charging, I disconnect the truck and I pull the plug.

I'm happy to report that we are rolling out an over-the-air (OTA) software update to the charger to address this. Please make sure your charger is connected to Wi-Fi to receive the update and ensure it is not plugged into your truck. Here’s some additional guidance on how to connect your vehicle to Wi-Fi.

According to Brian's OP post in this thread, if you leave your vehicle unplugged from the charger, you are likely to receive the firmware update (unless you mean disconnecting your FCSP from grid power when you are done charging). I can attest that's how I got the first of several firmware updates around August 7th, 2026. I went away for a day trip and when I came back, as I parked in the garage, my FCSP was updating.

 

[I <3 My Lightning]

Confirmed...Ford servers are not the problem...

 

[tearitupsports]

I plugged in to charge and it is updating in the app correctly.

Sponsored