My May 21 Job 1 Mach-E no longer gets OTA updates automatically

[TruWrecks]

My May 21 Job 1 Mach-E no longer gets OTA updates unless they are forced by Ford to everyone.

My car has not received an OTA updates or phoned home to Ford to get any since it got a failed OTA in September 2022. Yes it is connected to my home Wi-Fi.

I have tried setting up scheduled times for updates, and allowing any time. According to my router and Unifi switches neither SYNC nor the tcu have tried to connect anywhere to download any updates.

CSP 22B28 for HVAC is the only download and install my Mach-E has performed since September 17. 2022. It completed on January 25. 2023.

I have used FDRS on a 2 day license to manually update my MME and to reprogram the GWM module. Still no phoning home. I applied GWM, steering module and Door security modules D and E updates. Now there are no other updates showing. No UI Refresh. Nothing.

My dealer won't diagnose my MME for not getting update. Their response is "We can't bill warranty work when the car has no errors on dash or is not malfunctioning on the road." Unless the car has a persistent alarm or mechanical failure, go away.

Any other Job 1 owners not getting updates for over 6 months?

Sponsored

 

[Neil4Real]

No OTA updates have downloaded over Wi-Fi, they've all using the AT&T cell connection, so that doesn't tell you anything.

You then did all available updates via FDRS, which match the current OTA's (aside from the APIM refresh). There is a known issue that Ford's database isn't properly syncing or something with cars that still need the APIM update, I'm assuming with the release of the 4.2.2 or whatever GWM update.

Essentially, you're as current as you can be. If you didn't do FDRS updates, then there is a chance you would get updates OTA, but once you did those, there is nothing for you to get OTA...

Lastly, if you want to, you can full the fuse for the TCU I believe. This has worked for some people that were stuck, but again, I don't think you're stuck.

 

[TruWrecks]

Then you misunderstood my post. I manually updated with FDRS after almost 6 months of my MME not getting any updates Over-The-Air. CSP was the only one and that was pushed by Ford. SYNC does not control the HVAC with the center dial so I don't have 4.2.1.

 

[Shayne]

Then you misunderstood my post. I manually updated with FDRS after almost 6 months of my MME not getting any updates Over-The-Air. CSP was the only one and that was pushed by Ford. SYNC does not control the HVAC with the center dial so I don't have 4.2.1.

I got 3.6.1 on November 26th that is the HVAC update that you note you got sept 17th a month before. I have received no updates since but not thinking I am stuck again yet and hoping it will update again some day.

 

[Mach-Lee]

If you're saying you have no updates showing up in FDRS right now, but you still don't have the new UI, that really sucks. It means Ford's database is messed up for your car, or there is some kind of update prerequisite that wasn't programmed properly. Unfortunately I don't know that Ford knows how to deal with this right now.

There are a couple things you can try that might help. First, if you are using a VXDIAG VCX Nano adapter, chuck that and get a Mongoose, and do a network scan. The VCDIAG has some timing or communication issue with FDRS that causes Ford's database to get messed up for your car. Mongoose can fix that, and doesn't mess up database.

Second thing you could try is a 12V battery cable lift to reset all the modules. That might get the GWM and TCU talking again. When you say won't phone home, I assume that means it's not updating charge status in FordPass and remote start doesn't work?

Do you have any lingering trouble codes? Such as a U3000? Have you looked at the network scan logs for errors?

 

[TruWrecks]

I got 3.6.1 on November 26th that is the HVAC update that you note you got sept 17th a month before. I have received no updates since but not thinking I am stuck again yet and hoping it will update again some day.

The HVAC update for my MME was delivered on 01/25/23. That was when Ford forced the update. The update I received in September was for ABS.

 

[TruWrecks]

If you're saying you have no updates showing up in FDRS right now, but you still don't have the new UI, that really sucks. It means Ford's database is messed up for your car, or there is some kind of update prerequisite that wasn't programmed properly. Unfortunately I don't know that Ford knows how to deal with this right now.

There are a couple things you can try that might help. First, if you are using a VXDIAG VCX Nano adapter, chuck that and get a Mongoose, and do a network scan. The VCDIAG has some timing or communication issue with FDRS that causes Ford's database to get messed up for your car. Mongoose can fix that, and doesn't mess up database.

Second thing you could try is a 12V battery cable lift to reset all the modules. That might get the GWM and TCU talking again. When you say won't phone home, I assume that means it's not updating charge status in FordPass and remote start doesn't work?

Do you have any lingering trouble codes? Such as a U3000? Have you looked at the network scan logs for errors?

I have only used a Mongoose+ for FDRS. I don't own a VCX Nano. The 12 V has been disconnected long enough to force the MME to fully reset. My TPS sensors had to be learned again.

I can send remote commands to the MME with bluetooth, but the MME never sends or receives data while on Wi-Fi by itself. According to the FordPass application 2 nights ago the status at 23:00 was last updated 4 hours ago. It should have connected and updated it's info at 21:00. According to my router and switch the MME didn't send or receive any data, but the MME infotainment center shows it connected to my home WiFi.

It is depressing.

 

[Shayne]

The HVAC update for my MME was delivered on 01/25/23. That was when Ford forced the update. The update I received in September was for ABS.

My mistake and apologize for the the confusion. Received power up 3.6.1 HVAC on Jan. 26 day after you and not in Nov. my bad. On Dec 8th I received a bad install that locked all conductivity including no fordpass, no wireless carplay etc. (they call it fleet mode here ?‍). That was for 1.5 months with nothing connected until they could get me in to fix it. 2 hour fix which included 10,000 mile service for $40 and had it back working as it was at the beginning of December . Ford gave me 50,000 points told me was worth $250. Told them that I'd give $250 for a functional departure schedule but they again noted they knew nothing about the car, could not help and told me to talk to the dealer. The dealer knew before it went in that preconditioning this car this winter did not work for me but as mentioned got it back working just as it was at the beginning of Dec. He told me he has had no other complaints (has no other MME's?) but would keep his eye out for a TSB. Would not confirm it did not work for him either and ignored a further request.

Repost for my month of Feb. Wi-Fi and agree no communication. That has been the case since February 2021. Apple Android and M$ all appear ok updating with my internet connection. Maybe Bert is hogging the bandwidth?

So you think like 1.7.1 and 2.7.1 that 3.6.1 is another stuck for many? @Gullwingdmc link mentioned the MME is scared to update by itself in fear of a dead 12V? Maybe if we hook the charger up to it we will have better luck? Really done jumping hoops babysitting this car. Feb 2024 (3 years) is my deadline then it will be never again. Ford needs to stop concentrating totally on pushing subscriptions and concentrating on making it functional. Dysfunctional preconditioning for the entire winter. 2 winters will not be acceptable and will never be repeated.

Just a piece of tin and the sky is not falling. I will go with frustrating.

 

[Mach-Lee]

I can send remote commands to the MME with bluetooth, but the MME never sends or receives data while on Wi-Fi by itself. According to the FordPass application 2 nights ago the status at 23:00 was last updated 4 hours ago. It should have connected and updated it's info at 21:00. According to my router and switch the MME didn't send or receive any data, but the MME infotainment center shows it connected to my home WiFi.

It is depressing.

That's normal. Others have noticed the MME really doesn't do much with WiFi anymore. All the connected and remote features, telemetry, and OTAs come over AT&T LTE modem not WiFi. I think the only time it uses WiFi is if there is absolutely no LTE coverage.

Pulling down on the home screen of the FordPass app once, and then a second time 20 seconds later usually refreshes my status. You can also send a lock or unlock command to refresh status (lock, unlock, and remote start go over LTE not Bluetooth).

And BTW, the status may not update late at night on weekends because that's when the servers are doing maintenance. You won't be able to refresh vehicle status during server maintenance times (12AM-6AM? Eastern Sat/Sun).

 

[Kangio]

Same Issue here. Jan 21 MME. Last OTA was Oct 24th, 2022 (3.5.4.2). According to FDRS, there was a failed OTA attempt in mid November ’22. (?3.6) Took it to dealership in Feb, they did some TSB’s and said all modules UTD, but was still stuck at 3.5.4.2.

I have worked with the OTA specialists, who said they would force out an OTA to my VIN, and that it could take up to 5 days. After a week, no OTA. Followup with OTA hotline, they say that no “pending” updates are showing for my VIN, as if my car doesn’t “exist”. Said I needed to go to dealership.

Dropped off at service yesterday. They are supposed to work with TAC to figure out what is going on.

BTW, I was one of the lucky ones stuck on OTA 1.7.2 for 8 months in ‘21, which took multiple attempts with service department to force the update and finally allow me BC. Then received several OTA’s before getting stuck again last Oct. Car is connected to wifi every night. Also did the various voo doo suggested on other OTA threads including ensuring 12v battery charge, door locks, headlamps off, etc…

 

[Shayne]

AT&T LTE modem not WiFi. I think the only time it uses WiFi is if there is absolutely no LTE coverage.

Who is used in Canada not at&t? Partner Coverage if you zoom in Canada is all green. Up north it appears it is not working so well but my local wi-fi has not been used.

 

[Mach-Lee]

Same Issue here. Jan 21 MME. Last OTA was Oct 24th, 2022 (3.5.4.2). According to FDRS, there was a failed OTA attempt in mid November ’22. (?3.6) Took it to dealership in Feb, they did some TSB’s and said all modules UTD, but was still stuck at 3.5.4.2.

I have worked with the OTA specialists, who said they would force out an OTA to my VIN, and that it could take up to 5 days. After a week, no OTA. Followup with OTA hotline, they say that no “pending” updates are showing for my VIN, as if my car doesn’t “exist”. Said I needed to go to dealership.

Dropped off at service yesterday. They are supposed to work with TAC to figure out what is going on.

BTW, I was one of the lucky ones stuck on OTA 1.7.2 for 8 months in ‘21, which took multiple attempts with service department to force the update and finally allow me BC. Then received several OTA’s before getting stuck again last Oct. Car is connected to wifi every night. Also did the various voo doo suggested on other OTA threads including ensuring 12v battery charge, door locks, headlamps off, etc…

Sounds like either a locked APIM if you were stuck on 1.7.1 and they did the fix unsuccessfully, or a dependency issue because the server database for your car might be messed up. If your APIM got locked from a failed recovery attempt, you will be stuck on whatever version of SYNC you currently have forever until the APIM is replaced. The server does not authorize any updates for locked APIMs.

See this TSB: https://www.macheforum.com/site/threads/tsb-22-2404-revised-tsb-for-stuck-usb-updates.23093/

Who is used in Canada not at&t? Partner Coverage if you zoom in Canada is all green. Up north it appears it is not working so well but my local wi-fi has not been used.

Bell in Canada. Map: https://www.bell.ca/Mobility/Our_network_coverage

 

[Shayne]

Bell in Canada. Map: https://www.bell.ca/Mobility/Our_network_coverage

Based on the map and servicing Moosonee I kind of guessed. That is my plan on phones lots of service bars here. 3 of 4. Any truth in the 12V being the problem? If they do not push them there is no real problem at our end.

 

[Mach-Lee]

Based on the map and servicing Moosonee I kind of guessed. That is my plan on phones lots of service bars here. 3 of 4. Any truth in the 12V being the problem? If they do not push them there is no real problem at our end.

The 12V battery needs to be above a certain % before updates will install, it varies with the update but is typically 80-95%. Updates usually try to install immediately after the vehicle is driven since that would be when the 12V battery is at its highest. All my recent OTAs have installed shortly after parking the vehicle for the day (update downloads while I'm driving, and then applies a few minutes after I park). Driving the vehicle several times a week in an LTE coverage area is important for OTAs so the car can talk to the mothership and receive update triggers. Again, it only checks for updates while you are driving it, not while it's parked.

The 12V battery only matters if an update is trying to install after downloading, it will not prevent you from getting an update trigger however. What that means is you don't have to worry about the 12V unless you got a failed update attempt.

 

[Shayne]

BTW, I was one of the lucky ones stuck on OTA 1.7.2 for 8 months in ‘21, which took multiple attempts with service department to force the update and finally allow me BC. Then received several OTA’s before getting stuck again last Oct. Car is connected to wifi every night. Also did the various voo doo suggested on other OTA threads including ensuring 12v battery charge, door locks, headlamps off, etc…

For me it was 2.7.1 or something like that toke 2 times in to fix it which was good (2 months in between). Sat a good long time waiting for it to update before inquiring. Stuck on 1.7.1 software for 8 months tops me and understand as I went through no key etc. at the beginning also. It has got better and really only looking for a functional comfortable way to set a departure (FP) and a new DCFC curve and I am good. All else appears to be working OK. Apple wireless complains to boot but works fine after.

The 12V battery needs to be above a certain % before updates will install, it varies with the update but is typically 80-95%. Updates usually try to install immediately after the vehicle is driven since that would be when the 12V battery is at its highest. All my recent OTAs have installed shortly after parking the vehicle for the day (update downloads while I'm driving, and then applies a few minutes after I park). Driving the vehicle several times a week in an LTE coverage area is important for OTAs so the car can talk to the mothership and receive update triggers. Again, it only checks for updates while you are driving it, not while it's parked.

The 12V battery only matters if an update is trying to install after downloading, it will not prevent you from getting an update trigger however. What that means is you don't have to worry about the 12V unless you got a failed update attempt.

Thanks,

Never going to drive this car several times a week. I'm out on 100 acres and drive in (100 km) once or twice every two weeks. Putting more hours on the Massey then the road vehicle in my new profession. I find it has done it at my first stop a number of times after 50 km (30 miles). I don't think there is a problem here yet as the last installed no problem. I will most likely throw a charger on it and condition the 12V when it warms up.

Happy the software is auto maintaining (preparing for drive) this winter and running out of complaints. Will there be an update that maintains the 12V so it can install updates? Only need a couple of things but it needs to update to get them.

Sponsored