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

[Mike G]

Somewhat surprised this morning to find in addition to the HVAC I haven't done yet on my 21J1...another GWM!

What is that..three in a month? Or just two?

Sponsored

 

[kdonnel]

Somewhat surprised this morning to find in addition to the HVAC I haven't done yet on my 21J1...another GWM!

What is that..three in a month? Or just two?

I posted in another thread, but if Ford is re-releasing 4.1.1(GWM), 4.1.2(APIM), 4.1.3(GWM) it makes sense that 4.2.1(GWM), 4.2.2(APIM) would be followed up with 4.2.3(GWM).

 

[benk016]

I updated the HVAC and GWM last night. The GWM is 1 file only changed. So a small config change. The HVAC took longer than the USB GWM update did.

GWM brings us up to LJ8T-14H021-LKB

 

[Raptip1]

Does anyone know how long the update takes
of the GVM gateway module "A".
It's been at least over 3 hours now,
thanks

 

[Mach-Lee]

I updated the HVAC and GWM last night. The GWM is 1 file only changed. So a small config change. The HVAC took longer than the USB GWM update did.

GWM brings us up to LJ8T-14H021-LKB

Makes you wonder why they couldn’t have included the small config change in 4.2.2 since they had some time to fix it.

 

[kdonnel]

Just applied the GWM and HVAC update.

Didn't go exactly to plan.

GWM applied seemingly without issue.

HVAC as well but it remained in my list.

So I exited FDRS and launched it again and it still saw the update. So I rebooted the laptop, no difference, it still sees the HVAC update. So I applied it again. Still remains.

I then ran a network test to clear any DTC and was greeted with:

After pressing OK it did it's thing but for GFM I get:

If I relaunch FDRS I get green for the GFM.

The HVAC module remains in my list.

Any ideas? I am using FDRS 35.5.4.

 

[Mike G]

Does anyone know how long the update takes
of the GVM gateway module "A".
It's been at least over 3 hours now,
thanks

5 minutes to recognize the drive, another 5-10 minutes to update the software and then shutdown for 10 minutes with the driver's door open. Come back, turn the car on and wait for the message that says it was successful.

 

[Mike G]

Just applied the GWM and HVAC update.

Didn't go exactly to plan.

GWM applied seemingly without issue.

HVAC as well but it remained in my list.

So I exited FDRS and launched it again and it still saw the update. So I rebooted the laptop, no difference, it still sees the HVAC update. So I applied it again. Still remains.

I then ran a network test to clear any DTC and was greeted with:

After pressing OK it did it's thing but for GFM I get:

If I relaunch FDRS I get green for the GFM.

The HVAC module remains in my list.

Any ideas? I am using FDRS 35.5.4.

Your Frunk module went AWOL?

Did you check and clear DTCs before you did any programming?

 

[Mike G]

Makes you wonder why they couldn’t have included the small config change in 4.2.2 since they had some time to fix it.

Yeah this is a real "configuration control" head scratcher. This file was literally 1Kb big.

Is this some sort of "job security" to create baby step updates like this or are they really on the 'struggle bus' when it comes to software configuration control. Nevermind, I think I know the answer.

 

[Raptip1]

5 minuti per riconoscere l'unità, altri 5-10 minuti per aggiornare il software e poi spegnere per 10 minuti con la portiera del conducente aperta. Torna indietro, accendi la macchina e attendi il messaggio che dice che è andata a buon fine.
[/CITAZIONE]

So I abort the operation? he's been in this state for over 5 hours now

 

[kdonnel]

Your Frunk module went AWOL?

Did you check and clear DTCs before you did any programming?

I never do before, I always do after.

I did take note that I had a RFA, OBCC, and one other module with a DTC but not the GFM.

I did get a frunk error message as the HVAC programming finished together with an assortment of other errors, not unlike normal programming sessions.

edited to add:
Just was able to use FordPass to open the trunk so it is still there.

 

[Mike G]

Yes. This looks like the same update I just did and there's no way it takes this long. Reboot the laptop and start over.

 

[Mike G]

I never do before, I always do after.

I did take note that I had a RFA, OBCC, and one other module with a DTC but not the GFM.

I did get a frunk error message as the HVAC programming finished together with an assortment of other errors, not unlike normal programming sessions.

edited to add:
Just was able to use FordPass to open the trunk so it is still there.

Well I would shut the car down and recheck in a half hour to see if it's still doing it. Do a DTC check and clear with the car fully running, not just on the accessory position. I think it's an anomaly.

 

[Mike G]

I updated the HVAC and GWM last night. The GWM is 1 file only changed. So a small config change. The HVAC took longer than the USB GWM update did.

GWM brings us up to LJ8T-14H021-LKB

If you haven't re-formatted your thumb drive yet take a look at the .JSON file the car wrote to it after the update was successful.

I did my update this afternoon and I'm left scratching my head over why the timestamp on the .JSON file is 10:23 AM this morning, when the timestamps for the files that were downloaded were 3:07 PM this afternoon.

Is the car not getting synced to a time reference? Is that a possible reason that updates aren't happening when they should?

This JSON file gets written to the thumb drive by the car after the update is successful...so why on earth would the timestamp be that far off unless the car isn't correctly syncing up with a time reference?

It's Paddy's Day so shenanigans can't be ruled out! ???

 

[benk016]

If you haven't re-formatted your thumb drive yet take a look at the .JSON file the car wrote to it after the update was successful.

I did my update this afternoon and I'm left scratching my head over why the timestamp on the .JSON file is 10:23 AM this morning, when the timestamps for the files that were downloaded were 3:07 PM this afternoon.

Is the car not getting synced to a time reference? Is that a possible reason that updates aren't happening when they should?

This JSON file gets written to the thumb drive by the car after the update is successful...so why on earth would the timestamp be that far off unless the car isn't correctly syncing up with a time reference?

It's Paddy's Day so shenanigans can't be ruled out! ???

Just looked and mine didn't write the JSON file at all on this update. Just the Certificate file and the folder with the update files.

Sponsored