FCSP Software Version 2.112.91:2.149:1.32:1.53:0.62

[TaxmanHog]

Ok I assumed you knew exactly what you are doing, but couldn't find anything matching the previous screenshots. I realize those were with the old Fordpass app which no longer has that data. That is indeed a wierd bug, but has it caused any functionality issues?

Functionally she charges perfectly fine, hopefully I'm not missing out when the next true update version comes out, as of now I actually had this version with full string of digits, then a proposed update popped up many months ago resulting in this corruption.

So far I do not think Siemens has issued any firmware/software updates, I'm relying on others to report if/when that happens, hoping my unit heals this flaw.

Sponsored

 

[Scorpio3d]

Ok I assumed you knew exactly what you are doing, but couldn't find anything matching the previous screenshots. I realize those were with the old Fordpass app which no longer has that data. That is indeed a wierd bug, but has it caused any functionality issues?

Mine works fine charges the truck like it should just reports the data wrong!

 

[Scorpio3d]

Functionally she charges perfectly fine, hopefully I'm not missing out when the next true update version comes out, as of now I actually had this version with full string of digits, then a proposed update popped up many months ago resulting in this corruption.

So far I do not think Siemens has issued any firmware/software updates, I'm relying on others to report if/when that happens, hoping my unit heals this flaw.

Did you perform a power cycle on the FCSP?

 

[TaxmanHog]

@Ford Motor Company PLEASE have someone look at the database which stores our charging history data, I suspect a process corruption has occured after 10/13/2024.

 

[TaxmanHog]

Did you perform a power cycle on the FCSP?

Yes, but I am going to repeat in the morning, as the units do a phone home sometime after midnight.

 

[Scorpio3d]

Yes, but I am going to repeat in the morning, as the units do a phone home sometime after midnight.

I just did mine. I will see what happens tonight.

 

[Scorpio3d]

I'm familiar with how to pull the SW version, here is a snapshot that I just pulled from the FCSP setup app by "Manage Settings".

Interstingling Fordpass v5.6.0 has hidden this value formerly found in the Advanced > Charge Station Setting display.

I think you are both android I am iOS. Mine is showing the full software version numbers not a bunch of zeros, of course I did not check it before I did the power cycling earlier?

 

[TaxmanHog]

I think you are both android I am iOS. Mine is showing the full software version numbers not a bunch of zeros, of course I did not check it before I did the power cycling earlier?

Correct, I'm using an Android install of the FCSP Set-up App and Fordpass app.

I believe other members on Android are getting the full software version number, my situation is unique.

 

[Jim Lewis]

I am iOS and since about the same time as @TaxmanHog, I've been getting a corrupted FCSP software version number for MONTHS. My post today snuck in just ahead of Mr. T's, probably just as he was finishing up his...
https://www.f150lightningforum.com/...112-91-2-149-1-32-1-53-0-62.16527/post-430899

 

[TaxmanHog]

I am iOS and since about the same time as @TaxmanHog, I've been getting a corrupted FCSP software version number for MONTHS. My post today snuck in just ahead of Mr. T's, probably just as he was finishing up his...
https://www.f150lightningforum.com/...112-91-2-149-1-32-1-53-0-62.16527/post-430899

Oh yes, I missed your report, and that phenomena {leading zeros then substantial values} has happened to others earlier on this thread.

 

[TaxmanHog]

Yes, but I am going to repeat in the morning, as the units do a phone home sometime after midnight.

I just did mine. I will see what happens tonight.

No improvements with this mornings restart. Data from departure time conditioning event while plugged in still corrupted by 1000th the true value.

@Ford Motor Company your database is garbage

 

[Maquis]

No improvements with this mornings restart. Data from departure time conditioning event while plugged in still corrupted by 1000th the true value.

@Ford Motor Company your database is garbage

I’m seeing the same junk since 13-Oct.

 

[Scorpio3d]

No improvements with this mornings restart. Data from departure time conditioning event while plugged in still corrupted by 1000th the true value.

@Ford Motor Company your database is garbage

Same with mine!
Another weird thing which is probably an Apple thing is when I take a screenshot photo. It also includes a copy of my home screen, but I was sitting in the truck today so it included what is on the screen of my truck from CarPlay. Very weird!

 

[Ffxdude]

No improvements with this mornings restart. Data from departure time conditioning event while plugged in still corrupted by 1000th the true value.

@Ford Motor Company your database is garbage

I’m seeing the same junk since 13-Oct.

Same here. Seems to go back to 10/14 for me. This is why it would be nice to be able to export our charging history.

 

[TaxmanHog]

Same here. Seems to go back to 10/14 for me. This is why it would be nice to be able to export our charging history.

That makes sense, actually 10/13 was my last good charging data point, but I'm generally only charging weekly except when I am doing some testing. Yesterdays charge session continues with bad data.

I'm hoping the engineers who manage the database receive my APP reports and thee fix what is affecting this on the server side of the system. Maybe @Gimme_my_MME could jingle a few bells for us!?

Then they need to go back and perfect the flawed information from 10/14 forward to the repair point.

Sponsored