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

[Mike G]

I got a popup saying that a download failed. Occured once, not seen it again. Can someone run mine
3FMTK3SU2MMA66945
Thanks

28 Nov '21 build date, Job 2 car.

Here's the list of available updates:

I'd call the service advisor and ask them to pull up your VIN in the OTA dashboard and ask what the status is. They should be able to tell you perzackly what's going on over the phone.

Sponsored

 

[Mark Hassa]

Thank you! I'll go to my dealer and complain about fogging on defrost (I think that's the HVAC update?) And see if they knock out the others... Or maybe my new update schedule grabs them first.

I would also complain about poor DC charging to get the OBCC done. Just tell them you’re not getting updates and they can check their OTA dashboard to see what’s going on.

 

[buffasnow]

So what you're looking for is that GWM in this list to arrive:

After that you'll get the APIM update to the new Sync 640.

So check your update schedule to make sure it's set to a time you'll be driving the car (like on a commute to or from work).

Thank you sir! I have my schedule set for the morning drive to the gym.

 

[OrangerGT]

The short answer is yes, exactly. I have mine set to 0930 daily.

The long answer is this; I have a Mach-E and a Lightning and they both have identical 12V batteries. I noticed when I occasionally needed to apply software updates using FDRS that when I started whichever vehicle first thing in the morning and parked it in my work area and then connected up the powersupply, that the device would indicate that my 12V battery was always around 55-65% state of charge. Which meant I would then have to charge it up for a few minutes until it indicated over 80% (which is what FDRS checks for). This overnight slow drain happens everyday. It eventually gets low enough if it hasn't been driven that the high voltage battery will be engaged to recharge it back up. There has been at least one instance where my Lightning hadn't been driven in so long that when I went to depart with it that my Sync screen was off and I got a notification about the cameras not working. This was due to load shedding. It was all back to normal after about 15 minutes.

The logic for the OTA process takes into account the state of charge of your 12V battery when it makes the decision to check or not to check or do the update. Some updates need a greater state of charge than others due to the amount of time the update will take to process.

So to remove this 12V battery issue as a factor, I've found that setting the schedule to check and process OTAs while the car is driving, and in a good cell coverage area for the TCU, is best. Once downloaded, when you park the car will do the update and the next time you get in you should be notified.

Hey @Mike G, just wanted to give a positive update (and give hope for others here). I just got an update notification today and it installed 4.2.1. This is after trying your steps of setting the Automatic Update schedule time to a time roughly on my commute. It took a few days but now at least it did something!

Do you know if the updates have to be in order or if they can come in any order? I was looking forward to the UI rework which I believe is 4.1.2 and an update to the APIM, is that correct? Seems like it skipped that one if it was supposed to be in order. Also I saw on the list you provided that APIM did not have a pending update anyway.

Thanks again!

 

[EleDonkey]

Do you mind checking for 3FMTK1RM1MMA49127?

Been stuck on 3.6.2.

Thanks a lot!

 

[xofox25]

Yesterday, I've just received 3.5.2.1 by OTA which seems to be the last power up in EU (after doing successively all updates from FDRS 3 weeks ago).
Could you please check my VIN WF0TK3SU7MMA51521 to see what is currently missing ?

Thanks

 

[Mike G]

Do you mind checking for 3FMTK1RM1MMA49127?

Been stuck on 3.6.2.

Thanks a lot!

15 Aug '21 build date, Job 2 car.

Here's the list of available updates:

I'd set the Check Updates schedule to make sure it was checking during a time the car was being driven, and in an area with 3 bars of AT&T coverage. That way the 12V battery is back up above 80% SOC and the logic will allow any updates you have to process. Next I'd call my service advisor and ask them to pull up my VIN in PTS and look at the OTA Dashboard to see if any updates are in the queue and if so what the status of them is. And if you have no OTAs showing for the last 60 days then it might be a good idea to start the discussion on diagnosing why you aren't getting any OTAs. Several (at least 3) people on this thread have confirmed that once they got the PCM (in your list) updated that OTAs started to flow again.

 

[Mike G]

Yesterday, I've just received 3.5.2.1 by OTA which seems to be the last power up in EU (after doing successively all updates from FDRS 3 weeks ago).
Could you please check my VIN WF0TK3SU7MMA51521 to see what is currently missing ?

Thanks

HVAC is all you have this morning.

 

[Mike G]

Hey @Mike G, just wanted to give a positive update (and give hope for others here). I just got an update notification today and it installed 4.2.1. This is after trying your steps of setting the Automatic Update schedule time to a time roughly on my commute. It took a few days but now at least it did something!

Do you know if the updates have to be in order or if they can come in any order? I was looking forward to the UI rework which I believe is 4.1.2 and an update to the APIM, is that correct? Seems like it skipped that one if it was supposed to be in order. Also I saw on the list you provided that APIM did not have a pending update anyway.

Thanks again!

So here's the thing.....4.1.1 was a GWM update. And that came out quite a while ago....it was followed shortly after that by 4.1.2 which was the APIM (Sync 640), and then after that by 4.1.3 which was another GWM update.

They decided some time after that to update the GWM yet again. And that one was the latest revision that is 4.2.1. So for those people that never got 4.1.1 (or 4.1.3)...4.2.1 takes it's place. So the next thing for you would be the 4.1.2 (which seems backwards, I know) and that should be the the Sync 640 update. And that's probably the APIM that's in this list this morning:

So get out there and drive around a bit and see what happens!

 

[noflipping]

Hey Mike...

First thanks for all you do! After a number of weeks in and out of service (with Ford involved), I'm wondering if you can get the latest on my car for me? I was told all modules were updated manually at the dealer after getting the go-ahead from Ford. I'm now waiting to see if the Power-Up updates follow. Mine is so old, I'm not completely sure what version I'm on. Only clue I have is it predates any Alexa option.

3FMTK3SU0MMA05951

Thanks again!

BTW - I looked up on Ford website just now and it says my Sync says it's 4.0.22034

 

[Duncs]

Why am I stuck on 3.6?

3FMTK3SU4NMA03363

Any help is much appreciated

 

[Mike G]

Hey Mike...

First thanks for all you do! After a number of weeks in and out of service (with Ford involved), I'm wondering if you can get the latest on my car for me? I was told all modules were updated manually at the dealer after getting the go-ahead from Ford. I'm now waiting to see if the Power-Up updates follow. Mine is so old, I'm not completely sure what version I'm on. Only clue I have is it predates any Alexa option.

3FMTK3SU0MMA05951

Thanks again!

BTW - I looked up on Ford website just now and it says my Sync says it's 4.0.22034

6 Jan '21 build date, Job 1 car.

Here's the list of available updates:

I'm a bit concerned that there are no new GWM or APIM updates in your list and you have a really old version of Sync. That tells me that you may be stuck. You should probably discuss with your service advisor the fact that when they did the PMI for your APIM on the 6th to install this old version of Sync that you've had no indications that any future updates were going to be available. And you could ask them why today somebody is looking up the "module communications network" chapters in the online service manual (unless that's you doing a bit of research).

 

[Mike G]

Why am I stuck on 3.6?

3FMTK3SU4NMA03363

Any help is much appreciated

Like many other '22 models you probably need to have the PCM updated to enable further gateway and Sync updates to appear. The PCM in your list is likely causing a "dependency issue" which is blocking future updates. Convince your shop to update your PCM and OTA updates will most likely resume.

 

[gregpdx]

Hi Mike and all,

3FMTK3SUXMMA59466

I am waiting on my Mongoose cable to arrive and will purchase an FDRS license for a couple of days when it is here, but I was hoping to know what shows up and more importantly, if there is anything I should skip or run first (because in the past I have read on the forums that sometimes there can be updates shown that don't actually apply, as well as dependencies to be aware of?).

Thank you!

greg

 

[Mike G]

Hi Mike and all,

3FMTK3SUXMMA59466

I am waiting on my Mongoose cable to arrive and will purchase an FDRS license for a couple of days when it is here, but I was hoping to know what shows up and more importantly, if there is anything I should skip or run first (because in the past I have read on the forums that sometimes there can be updates shown that don't actually apply, as well as dependencies to be aware of?).

Thank you!

greg

Greg;

There is a gateway in your list that should come as an OTA.

When you get closer to the day you plan on updating get back with me and I'll give you a list order recommendation. Best to plan on doing most of the list (if not all of it) on a Saturday because of the Sunday cloud server maintenance Ford does. You can program on Sundays but they will take their system offline around 0900-1030 central time to do maintenance, so if you're trying to do an update you may get a failure notification because FDRS lost it's connection while you were doing it.

Sponsored