Post here if you have an active FDRS account and are willing to look up info for others

[Robz]

I unfortunately can't view your DTC history but you do have a LOT of updates available. Some of these are from the initial BC 1.0 rollout.

Thanks for the help. Will let the dealer know.

Sponsored

 

[PTargo]

Looks like that gateway update would be OTA 5.1.1 when it shows up. Don't know why those doors haven't gotten the OTA update by now but maybe it's cause the car has been sitting on a lot for a while. ?‍ dunno. Also it looks like the HVJB was replaced on the 4th of Feb this year.

Thank you, Mike!

 

[Pedro Diaz]

Here's the list of available updates:

You really aren't 'missing' much. Many of us have these exact same updates in our lists and are just waiting for the OTAs to be released to update them.

Wow! This is amazing! I ask, if these are pending updates, why haven't the car or Ford App given me a warning? I've recently received a paper letter from Ford warning me to get the car ready to auto-receive the update to correct the battery charging relays fix. Ironically, the letter came around 11/7 but I was to respond before 10/31. So I'm left to have a dealership handle it. I was hoping to find out that this update was already installed. I don't have the letter in front of me to tell you the exact update "number" but this was discussed in the forum and on YouTube as well.

 

[noflipping]

Here's your list of available updates:

So there are dependencies at work here.

You have a rather old version of Sync.

You have an APIM update in your list that should be applied next before anything else happens. That would update your Sync and after that either a TCU or GWM update would likely show up. If it were me sitting there with the FDRS laptop I'd be updating the APIM first and any follow-on GWM, or TCU that shows up after that...and keep doing that until no more of those show up.

Then I'd do the RFA, the doors, the HVAC, the CMR and PSCM, the OBCC, and then stop without doing the powertrain items (PCM, ABS, BECM, SOBDM, SOBDMB, SOBDMC) or the SCCM. That would bring you to mostly current. Many of us doing our own updates are not doing the SCCM so that it doesn't cause an issue with getting a future BC 1.3 update OTA, so just letting that one happen when it happens. I also havens;'t done the new GFM that was released a couple of weeks ago. I'd like to know what that one's for before doing that update.

As you been told dozens of times before, you're not only very generous, but a genius. I'll see if I can get them to remedy these dependancies. Thanks!

 

[duck2412]

So... any luck this time around, still waiting for the sync update that should refresh the ui

VIN: WF0TK3SUXNMA05375

 

[Mark Hassa]

HI Mike,
Dealer called me the other day to schedule the CSP 23B50. I know I'm behind on the GWM updates, so I figured I'd use GSB 23-7146 to force their hand into getting those updated first. If it were you updating my car, how would you go about it?
3FMTK3SSXMMA50149
Could you also please check the Explorer too?
1FM5K8GCXLGD11053

 

[Mike G]

Wow! This is amazing! I ask, if these are pending updates, why haven't the car or Ford App given me a warning? I've recently received a paper letter from Ford warning me to get the car ready to auto-receive the update to correct the battery charging relays fix. Ironically, the letter came around 11/7 but I was to respond before 10/31. So I'm left to have a dealership handle it. I was hoping to find out that this update was already installed. I don't have the letter in front of me to tell you the exact update "number" but this was discussed in the forum and on YouTube as well.

Available software updates for modules can appear in FDRS long before the OTA team schedules them to go out to customer cars. Many updates never make it to OTA status I'm assuming because although they might be nice to have...they were originally released to correct a specific problem that only a percentage of the cars were sending error reports about, or that customers were complaining about.

There are those of us who do our own updates and kind of follow along with the releases as they come out, and determine at the time whether or not it's worth the time to update.

This is my list from my MME today:

All but one of those updates are from the "powertrain" group. The GFM update is for the Frunk module.

Since doing those powertrain updates using FDRS will apparently (according to other smart folks on the forum) not enable the automatic parking brake feature the way it was intended after the update, I'm happy to wait for those modules to get updated as OTA 6.6.0 whenever they decide top push that to my car.

I know what the GFM is and what it does. I don't know what this particular update was intended to fix and since my Frunk is working fine, I'm happy to leave that update alone until either I find out the reason it's in every Mach-E's update list, or I'll just update it eventually along with other updates that I'm more interested in doing (like whenever the updated BC stuff arrives).

 

[Mike G]

So... any luck this time around, still waiting for the sync update that should refresh the ui

VIN: WF0TK3SUXNMA05375

No such luck today:

 

[Mike G]

HI Mike,
Dealer called me the other day to schedule the CSP 23B50. I know I'm behind on the GWM updates, so I figured I'd use GSB 23-7146 to force their hand into getting those updated first. If it were you updating my car, how would you go about it?
3FMTK3SSXMMA50149
Could you also please check the Explorer too?
1FM5K8GCXLGD11053

So the tech will be updating all the powertrain items in this list (PCM, ABS, SOBDMC, SOBDMB, SOBD, BECM) for CSP 23B50.

If I were doing it I'd start with that gateway first, and it's entirely possible that another gateway will pop up right after that one, and then an APIM after that. As you probably know most of us are leaving the SCCM and GFM alone until after more BC 1.3 updates show up. Right now I plan on letting OTA 6.6.0 happen whenever it happens. I'm in no rush.

And this is what you've got on the Explorer:

 

[jambas]

Anyone able to help check what I'm missing: 3FMTK3SU6MMA58850

Cars been stuck on a failed update all year, so I know I'm probably missing a lot. Went to the dealer today to install the two CSP updates 23B50/22B28, and hoping this triggers other OTA updates to come in.

Thanks in advance

 

[machme]

Hello! @Mike G can you run my VIN for me? I have 6.6.0 applied and curious what it shows outstanding before I think about a FDRS license

3FMTK4SE8NMA19256

 

[Mike G]

Anyone able to help check what I'm missing: 3FMTK3SU6MMA58850

Cars been stuck on a failed update all year, so I know I'm probably missing a lot. Went to the dealer today to install the two CSP updates 23B50/22B28, and hoping this triggers other OTA updates to come in.

Thanks in advance

Well I think you're a bit stuck.

And if the dealer tech doesn't do that gateway update before doing anything else it might get worse.

Due to software dependencies you would not normally ever see a GWM (gateway) update, an APIM (Sync) update, and/or a TCU (telematics modem) update in the list at the same time. Because they are normally updated in a sequence and only one of those three are in your available software list at any given time. But not more than one...

You have both a gateway and an APIM update in your list now. So getting that gateway update done before attempting anything else would be the smart thing to do. (and then the APIM...etc.). Note the sequence in the attached reference that Ford directs those three to be updated in. It's always gateway, APIM, and then TCU. And if you do a gateway update it's possible that another gateway update will pop up in the list because historically there have been multiple gateway updates released back-to-back before the next APIM or TCU showed up.

So I'm hopeful that he/she doesn't simply focus on the powertrain items (23B50) and ignore the gateway and APIM completely.

 

[Mike G]

Hello! @Mike G can you run my VIN for me? I have 6.6.0 applied and curious what it shows outstanding before I think about a FDRS license

3FMTK4SE8NMA19256

Well since those pesky powertrain items were taken care of by the OTA you don't have much left:

 

[scruffyman]

Hello, @Mike G would you be able to run my VIN? I am at 6.1.0 for about a month now. 3FMTK4SE8PMA37890. Thank you!

 

[machme]

Well since those pesky powertrain items were taken care of by the OTA you don't have much left:

Thanks! @Mike G

Sponsored