The Complete DIY Guide to Updating Your Mach-E with FDRS

[generaltso]

It's update Friday again:

'21J1 in NA and the UK/EU have new updates to powertrain this morning:

*So far* these have not shown up for '22/'23 models that I have checked.

These are all 'coordinated' and will be done in sequence when you select one of them (I always start with the PCM and FDRS sometimes decides to do the BECM first anyway, just so you know).

I don't know if these will be an OTA set yet. We will have to wait and see.

Maybe I'll let my dealer do this round of updates so they can finally clear the BECM Recall flag.

Sponsored

 

[Mike G]

Maybe I'll let my dealer do this round of updates so they can finally clear the BECM Recall flag.

Hmmm, that’s a new one for me. Wasn’t aware there was such a thing.

 

[Neil4Real]

It's update Friday again:

'21J1 in NA and the UK/EU have new updates to powertrain this morning:

*So far* these have not shown up for '22/'23 models that I have checked.

These are all 'coordinated' and will be done in sequence when you select one of them (I always start with the PCM and FDRS sometimes decides to do the BECM first anyway, just so you know).

I don't know if these will be an OTA set yet. We will have to wait and see.

These are all pretty quick ones, right? Notice anything or get a DTC that won't clear?

 

[Mark Hassa]

It's update Friday again:

'21J1 in NA and the UK/EU have new updates to powertrain this morning:

*So far* these have not shown up for '22/'23 models that I have checked.

These are all 'coordinated' and will be done in sequence when you select one of them (I always start with the PCM and FDRS sometimes decides to do the BECM first anyway, just so you know).

I don't know if these will be an OTA set yet. We will have to wait and see.

Could be the next OTA. Very similar list to 3.6.2. Inhibit update for about 20-25min.

 

[Mike G]

These are all pretty quick ones, right? Notice anything or get a DTC that won't clear?

Was busy today and it's raining buckets here anyway, first thing tomorrow.

 

[richsi]

Programmed: PCM, SOBDMB, SOBDMC, BECM, ABS. Total programming time 35 minutes. BECM failed once, tried retry option and worked the second time. After programming PCM was still on the list, tired it again and failed. Did reset and clear DTC's, PCM still on the list. Tried it again and failed with following message:

Procedure Unseccessful, "Get Config Data From Givis", Modified Configuration data is missing from Ford Server

Stopped and left it on the list and closed down session. Any help?

Note, select PCM first and it daisy-chains all the other Modules in the order shown above, nothing else to select after you start PCM. Also warning, it draws big power (all modules) from the PSU (35-38 Amps) beware!

 

[Mike G]

Programmed: PCM, SOBDMB, SOBDMC, BECM, ABS. Total programming time 35 minutes. BECM failed once, tried retry option and worked the second time. After programming PCM was still on the list, tired it again and failed. Did reset and clear DTC's, PCM still on the list. Tried it again and failed with following message:

Procedure Unseccessful, "Get Config Data From Givis", Modified Configuration data is missing from Ford Server

Stopped and left it on the list and closed down session. Any help?

I believe that is from the certificate server not responding properly. It should sort itself out. I'm going to do the updates tomorrow morning and will report if it does the same thing, but I doubt it will.

 

[richsi]

I believe that is from the certificate server not responding properly. It should sort itself out. I'm going to do the updates tomorrow morning and will report if it does the same thing, but I doubt it will.

OK, I figured something of that nature, not concerned about it just reporting what I have observed for others. Keep everyone up to date!

 

[scoopman]

Programmed: PCM, SOBDMB, SOBDMC, BECM, ABS. Total programming time 35 minutes. BECM failed once, tried retry option and worked the second time. After programming PCM was still on the list, tired it again and failed. Did reset and clear DTC's, PCM still on the list. Tried it again and failed with following message:

Procedure Unseccessful, "Get Config Data From Givis", Modified Configuration data is missing from Ford Server

Stopped and left it on the list and closed down session. Any help?

Note, select PCM first and it daisy-chains all the other Modules in the order shown above, nothing else to select after you start PCM. Also warning, it draws big power (all modules) from the PSU (35-38 Amps) beware!

I just updated myself, and got the exact same experience as @richsi -- took about 20-25 minutes.

I've decided to enjoy my new BCM and ABS software, and not to be concerned with Ford's server errors that they left unresolved over the weekend.

 

[Mike G]

So the rains quit and I did end up updating yesterday evening.

I don't know if it was the fact that all these updates were 'coordinated' powertrain updates that were chained in sequence or whether there's a server error that is messing with the session logs but here's what showed up this morning for the events from yesterday:

No mention of the ABS, SOBDMB, or SOBDMC even though they got updated. And the time stamps are about right for the amount of time I spent. I did go from one update right into the next with a quick ignition off, then back on, to get to the next update so maybe it just didn't record the intervening events.

And at the end I did get returned to the software updates list with a PCM still available, but I turned the car completely on ("ignition on, engine on") and ran the rescan network button once and it dropped off the list. I did clear and retest all DTCs that showed up as a result of the communications interruptions during programming, and everything came back green.

I noticed the hardware/software revisions for these updates (with the exception of the PCM) are actually newer now than those same modules on '22 models.

Also one final note. I've checked a few '22 models this morning and they have these same updates in their lists of available software. Kinda weird that '21 models show the updates on Friday and the '22 models the next day, cause those updates were not showing on '22 models yesterday (at least the ones I checked).

 

[Mach-Lee]

So the rains quit and I did end up updating yesterday evening.

I don't know if it was the fact that all these updates were 'coordinated' powertrain updates that were chained in sequence or whether there's a server error that is messing with the session logs but here's what showed up this morning for the events from yesterday:

No mention of the ABS, SOBDMB, or SOBDMC even though they got updated. And the time stamps are about right for the amount of time I spent. I did go from one update right into the next with a quick ignition off, then back on, to get to the next update so maybe it just didn't record the intervening events.

And at the end I did get returned to the software updates list with a PCM still available, but I turned the car completely on ("ignition on, engine on") and ran the rescan network button once and it dropped off the list. I did clear and retest all DTCs that showed up as a result of the communications interruptions during programming, and everything came back green.

I noticed the hardware/software revisions for these updates (with the exception of the PCM) are actually newer now than those same modules on '22 models.

Also one final note. I've checked a few '22 models this morning and they have these same updates in their lists of available software. Kinda weird that '21 models show the updates on Friday and the '22 models the next day, cause those updates were not showing on '22 models yesterday (at least the ones I checked).

This is what happens when the server goes down during updates. I recommend you do another network scan today to make sure the server has the correct versions recorded for your vehicle so you don’t end up with problems.

 

[21st Century Pony]

So the rains quit and I did end up updating yesterday evening.

I don't know if it was the fact that all these updates were 'coordinated' powertrain updates that were chained in sequence or whether there's a server error that is messing with the session logs but here's what showed up this morning for the events from yesterday:

No mention of the ABS, SOBDMB, or SOBDMC even though they got updated. And the time stamps are about right for the amount of time I spent. I did go from one update right into the next with a quick ignition off, then back on, to get to the next update so maybe it just didn't record the intervening events.

And at the end I did get returned to the software updates list with a PCM still available, but I turned the car completely on ("ignition on, engine on") and ran the rescan network button once and it dropped off the list. I did clear and retest all DTCs that showed up as a result of the communications interruptions during programming, and everything came back green.

I noticed the hardware/software revisions for these updates (with the exception of the PCM) are actually newer now than those same modules on '22 models.

Also one final note. I've checked a few '22 models this morning and they have these same updates in their lists of available software. Kinda weird that '21 models show the updates on Friday and the '22 models the next day, cause those updates were not showing on '22 models yesterday (at least the ones I checked).

So I did the same with the new 2022 list which just showed up this morning... ran the PCM 1st. It went on for a few minutes and afterwards, it chained all the other updates together (SOMDB, SOMDBc, ABS etc.).

Afterwards, I still had PCM showing as the sole update available. Cleared all DTCs (twice). Ran network tests. Tried the PCM again, twice.

Very quick failure this time, with message "Procedure unsuccessful - GetConfigDataFromGIVIS".

I'm guessing it's related to the Mach-Lee's post... a server issue on Ford side?

 

[737flyer]

I don’t understand why Ford doesn’t sent OTA’s quicker for all the files that are in FDRS. I guess if you don’t do your own updates you never get them all.

 

[Mike G]

I don’t understand why Ford doesn’t sent OTA’s quicker for all the files that are in FDRS. I guess if you don’t do your own updates you never get them all.

?
?
?

 

[bshaw]

I don’t understand why Ford doesn’t sent OTA’s quicker for all the files that are in FDRS. I guess if you don’t do your own updates you never get them all.

Although the end result should be the same, the OTA process and FDRS accomplish the update in completely different ways.
FDRS is able to take everything offline and write to any module directly on CANbus.
OTA stages an update somewhere in the car (GWM?) and writes the update from there. Someone with more knowledge of OTA can expand on the explanation.

Some modules cannot be updated via OTA, and at the end of the day, Ford is probably really conservative with OTA where they would rather keep you not updated than put the car into an unusable or degraded state from an OTA that was incomplete. With something like ~36 separate modules in the car, managing dependencies must really be a challenge for pushing out updates.

Sponsored