24-pu0121-ftdi-fx ota

[elmedico27]

Last April.
https://github.com/elmedico27/fordpowerup

Whooo! I’m ahead of the game for once! ?

Sponsored

 

[Track9979]

Just got it too. 2 weeks after not completed 6.3.0 on my 23 GT
edit: next day (today) got
24-PU0119-DC-CHG4 - Plug and Charge and after running the update, got
6.7.0 - Frunk Update
23-PU1024-6CH-AUD - Audio Update
24-PU0301-BLM-PE - Entry Made Easy (left the window open for this one...)
all of which required the car to be inhibited
No apparent issues after updating

 

[Ladj1985]

I got notified of this today too. When I got home I told it to start the update. A few minutes later got notified that it failed. First time I’ve ever had a failed update.

 

[dallowev]

Just installed this one a few mins ago.

 

[tbrumleve]

Also just got this one. 6.14 three weeks ago was my last update. I know it came out in March, but that was also the time frame when I stopped receiving OTA’s until months later. Probably clearing the queue

 

[zvez]

I got notified of this today too. When I got home I told it to start the update. A few minutes later got notified that it failed. First time I’ve ever had a failed update.

check your 12v battery state of charge, Ford says some OTAs need at least 80% state of charge to succeed.

 

[zakth]

WARNING! This update installed last night… remote started my car this morning and when I went out I was greeted with a High Voltage Battery Fault warning… never had an issue with this Mach-E GT until this update… had a 21’ premium that also have a HVBJB fault…

 

[SmokesLetsGo]

Got this update on my 2023.5 last night, no issues.

 

[ToOldForThis]

This was the first update my car received after purchasing it (used) back in March. No issues with the install or after.

 

[avdonr]

If someone can provide their VIN to me I can check to see if this really is the BCM update that’s been available in FDRS for the last month.

I’m skeptical of the release notes and label for this OTA, seems like they recycled it from last BCM update. Maybe this is just a re-release for the same update.

 

[Dadams]

If someone can provide their VIN to me I can check to see if this really is the BCM update that’s been available in FDRS for the last month.

I’m skeptical of the release notes and label for this OTA, seems like they recycled it from last BCM update. Maybe this is just a re-release for the same update.

Vin removed

 

[avdonr]

3FMTK4SE6PMA03480

Hmm, unfortunately can’t really tell from your VIN. I can’t see OTA history, was hoping that just looking at the software update screen would tell me that your BCM was updated but it still shows a pending update. Maybe the backend didn’t update yet. I’ll keep tabs on it.

I hope they didn’t resume the rollout of the OTA from March and forget to change the file to be the new BCM version lol.

 

[Dadams]

Hmm, unfortunately can’t really tell from your VIN. I can’t see OTA history, was hoping that just looking at the software update screen would tell me that your BCM was updated but it still shows a pending update. Maybe the backend didn’t update yet. I’ll keep tabs on it.

I hope they didn’t resume the rollout of the OTA from March and forget to change the file to be the new BCM

That was about 7:30 when it installed

 

[rugedraw]

Hmm, unfortunately can’t really tell from your VIN. I can’t see OTA history, was hoping that just looking at the software update screen would tell me that your BCM was updated but it still shows a pending update. Maybe the backend didn’t update yet. I’ll keep tabs on it.

I hope they didn’t resume the rollout of the OTA from March and forget to change the file to be the new BCM version lol.

I think this has something to do with the string of vehicles being bricked by OTA's recently. I was recently made aware by another member here that FTDI is an acronym for "failed to de-inhibit". This may be a blanket OTA that sends some change to the BCM to help prevent vehicles from getting bricked from OTA's, and this is just an updated version of the OG update to include whatever fix they came up with now.

 

[garyd9]

I think this has something to do with the string of vehicles being bricked by OTA's recently. I was recently made aware by another member here that FTDI is an acronym for "failed to de-inhibit". This may be a blanket OTA that sends some change to the BCM to help prevent vehicles from getting bricked from OTA's, and this is just an updated version of the OG update to include whatever fix they came up with now.

Unless I'm misinterpreting the above posts, the OTA seems to be installing the older BCM code, and leaving the new one still pending in FDRS. @Dadams installed their OTA, but FDRS was still showing a BCM update available...

Sponsored