Let's Get Our Mach-E Siblings UPDATED

[DadzBoyz]

I've posted, previously, about the 10 key-cycle method to force your Mach-E to poll Ford's servers for Power-Up updates. It has worked for me, 2-3 times, like a charm. I'll include that again below.

That said, I know some of you are probably stuck, or feeling stuck with older Power-ups like 3.5.2 or 3.5.3 or 3.6.2, etc. It seems, from my reading of trusted technical members/posters on this forum, that there can be situations where a Mach-E may need some help from the dealer to address a stuck module that is preventing some updates from running.

In January, I had called Ford's BEV customer support on a couple of issues and was given a Case number and asked to take the car to a dealership for attention. Armed with a BEV case, some research and the attached letter, with details, I went to the local dealer. They updated those modules that had Ford CSP's, SSM's, or any other service or satisfaction programs associated with them. In the letter, I detailed each problem associated with the module with a CSP/SSM that had not been addressed on my car, and asked them to update it. It was helpful to go to the Forum thread where friendly Forum Wizards with FDRS access are willing to run your VIN to see what modules need updating (thread link below). Taking that readout is helpful as well. They will update only those modules that are impacted by, or causing the problems referenced in the CSP/SSM. Anything beyond that, they will charge you for.

By documenting known issues and providing Ford's own reference numbers, the dealers should have no trouble getting to work and charging Ford for their time. I think this could be a way to get those Mach-E's that are stuck on older Power-Ups over the hump or roadblock that may be preventing OTA's for you.

Once you've had this done, I would suggest the 10 key-cycle method to force your Mach-E to connect to the OTA server and pull down your updates. Yes, it seems crazy, but it has worked for me. After running the 10 key-cycles, it may take a day or two, but it has been my experience that your car will start pulling down OTA's.


FDRS Thread:
https://www.macheforum.com/site/thr...up-info-for-others.10230/page-266#post-624731


10 Start Cycles

1. Start your MME.
2. Turn it off.
3. Get out and lock it.
4. Walk far enough away to disconnect PAAK and/or your key fob.
5. Wait until interior lights turn off.
6. Return to step 1.

Do this 10 times.

Sponsored

 

[elbo]

Is that 10 times thing a belated April's fool?

 

[Logal727]

I've posted, previously, about the 10 key-cycle method to force your Mach-E to poll Ford's servers for Power-Up updates. It has worked for me, 2-3 times, like a charm. I'll include that again below.

That said, I know some of you are probably stuck, or feeling stuck with older Power-ups like 3.5.2 or 3.5.3 or 3.6.2, etc. It seems, from my reading of trusted technical members/posters on this forum, that there can be situations where a Mach-E may need some help from the dealer to address a stuck module that is preventing some updates from running.

In January, I had called Ford's BEV customer support on a couple of issues and was given a Case number and asked to take the car to a dealership for attention. Armed with a BEV case, some research and the attached letter, with details, I went to the local dealer. They updated those modules that had Ford CSP's, SSM's, or any other service or satisfaction programs associated with them. In the letter, I detailed each problem associated with the module with a CSP/SSM that had not been addressed on my car, and asked them to update it. It was helpful to go to the Forum thread where friendly Forum Wizards with FDRS access are willing to run your VIN to see what modules need updating (thread link below). Taking that readout is helpful as well. They will update only those modules that are impacted by, or causing the problems referenced in the CSP/SSM. Anything beyond that, they will charge you for.

By documenting known issues and providing Ford's own reference numbers, the dealers should have no trouble getting to work and charging Ford for their time. I think this could be a way to get those Mach-E's that are stuck on older Power-Ups over the hump or roadblock that may be preventing OTA's for you.

Once you've had this done, I would suggest the 10 key-cycle method to force your Mach-E to connect to the OTA server and pull down your updates. Yes, it seems crazy, but it has worked for me. After running the 10 key-cycles, it may take a day or two, but it has been my experience that your car will start pulling down OTA's.


FDRS Thread:
https://www.macheforum.com/site/thr...up-info-for-others.10230/page-266#post-624731


10 Start Cycles

1. Start your MME.
2. Turn it off.
3. Get out and lock it.
4. Walk far enough away to disconnect PAAK and/or your key fob.
5. Wait until interior lights turn off.
6. Return to step 1.

Do this 10 times.

I feel like the 10 times thing was only when it checked for map updates for BlueCruise. Right @Mach-Lee ?

 

[Mach-Lee]

I've posted, previously, about the 10 key-cycle method to force your Mach-E to poll Ford's servers for Power-Up updates. It has worked for me, 2-3 times, like a charm. I'll include that again below.

That said, I know some of you are probably stuck, or feeling stuck with older Power-ups like 3.5.2 or 3.5.3 or 3.6.2, etc. It seems, from my reading of trusted technical members/posters on this forum, that there can be situations where a Mach-E may need some help from the dealer to address a stuck module that is preventing some updates from running.

In January, I had called Ford's BEV customer support on a couple of issues and was given a Case number and asked to take the car to a dealership for attention. Armed with a BEV case, some research and the attached letter, with details, I went to the local dealer. They updated those modules that had Ford CSP's, SSM's, or any other service or satisfaction programs associated with them. In the letter, I detailed each problem associated with the module with a CSP/SSM that had not been addressed on my car, and asked them to update it. It was helpful to go to the Forum thread where friendly Forum Wizards with FDRS access are willing to run your VIN to see what modules need updating (thread link below). Taking that readout is helpful as well. They will update only those modules that are impacted by, or causing the problems referenced in the CSP/SSM. Anything beyond that, they will charge you for.

By documenting known issues and providing Ford's own reference numbers, the dealers should have no trouble getting to work and charging Ford for their time. I think this could be a way to get those Mach-E's that are stuck on older Power-Ups over the hump or roadblock that may be preventing OTA's for you.

Once you've had this done, I would suggest the 10 key-cycle method to force your Mach-E to connect to the OTA server and pull down your updates. Yes, it seems crazy, but it has worked for me. After running the 10 key-cycles, it may take a day or two, but it has been my experience that your car will start pulling down OTA's.


FDRS Thread:
https://www.macheforum.com/site/thr...up-info-for-others.10230/page-266#post-624731


10 Start Cycles

1. Start your MME.
2. Turn it off.
3. Get out and lock it.
4. Walk far enough away to disconnect PAAK and/or your key fob.
5. Wait until interior lights turn off.
6. Return to step 1.

Do this 10 times.

The 10 cycles only works for gateway module updates, and it’s only necessary to do it once if you’re stuck below 4.x updates. You can also pull fuse #21 or lift the 12V cable for the same effect. Once you’ve installed 4.2.1 you don’t have to worry about doing that again, you should get the other updates when it’s your time (usually within a week or two after 4.2.1).

BlueCruise map updates will be checked every 10 key cycles but those are a separate process from OTAs.

 

[Mark Hassa]

Honestly I’m more curious about what PowerUp everyone is on. If someone could do another poll, that would be interesting.

 

[Mach-Lee]

Honestly I’m more curious about what PowerUp everyone is on. If someone could do another poll, that would be interesting.

I feel like most people are at the 4.2.2 level with the camera button. If you don’t have the camera button by now, you’re probably behind.

 

[DadzBoyz]

Is that 10 times thing a belated April's fool?

It's real. Their BEV phone support taught me. I thought they were crazy until I did it and it instantly updated my BlueCruise Maps, enabling Hands-Free. It's worked a couple of times since then as well.

 

[moparguy]

I feel like most people are at the 4.2.2 level with the camera button. If you don’t have the camera button by now, you’re probably behind.

I am stuck at 3.6, what's the camera button?

 

[astrorob]

I am stuck at 3.6, what's the camera button?

camera button in the top ribbon for quick access.

also of course has the new UI with the smaller app tiles below the map/carplay/android auto.

 

[Nygman]

It's real. Their BEV phone support taught me. I thought they were crazy until I did it and it instantly updated my BlueCruise Maps, enabling Hands-Free. It's worked a couple of times since then as well.

I called BEV support once, they said the updated failed, but it will try again soon, and the next day I got an update mysteriously. Since then I have received regular updates, only yesterday I got 4.2.4. being in the same build group, I think you should be there too?

 

[azerik]

I did it and it instantly

20 minutes and 20 key cycles later

mine started trickling in just beforeit’s planned trip to the LD. I tried this key cycle with no luck left the car running in Brie garage for 4 hours, no luck. It’s all a rain dance re really

 

[DadzBoyz]

I called BEV support once, they said the updated failed, but it will try again soon, and the next day I got an update mysteriously. Since then I have received regular updates, only yesterday I got 4.2.4. being in the same build group, I think you should be there too?

I am. I got 4.2.4 yesterday.
FordPass is buggy. It says that I received an update but can’t tell me which and what’s included.

 

[Nygman]

I am. I got 4.2.4 yesterday.
FordPass is buggy. It says that I received an update but can’t tell me which and what’s included.

Same here but shows up in car. Actually got notification when out doing errands yesterday, So must have updated while driving. We're probably on the same sync schedule now.

 

[Vulnox]

Yeah I wouldn't buy into the 10 key cycle thing, sounds like someone on BEV support was just confused about a process. The OTA updates are triggered by your VIN being set to get an OTA update on Ford's end, nothing your car does matters.

Here is the OTA Status Log from one of our MMEs recent OTAs.

Note the "Trigger created on TMC", that means Ford designated our VIN as able to retrieve an OTA update.

Then at 4:26PM when my wife left work, the car acknowledged that an OTA Trigger is Available.

Then the update started "delivering" to the car at the next power cycle at 6PM.

That "Trigger created on TMC" is on Ford's end, it has nothing at all to do with how many times you cycle your car. She was working at the time that trigger was created. This site and the F-150 site have been full of the magic method to get an OTA update, but they are as far as I can see just correlation, not causation. I have had two vehicles, the F-150 and MME, that get OTA updates. If this worked then I wouldn't have received my BlueCruise OTA on the F-150 3 months after others did because I definitely key cycled at least 90 times in that period.

Anyway, do whatever you want obviously, it's not like this is harmful. But I don't believe it for a second. I bet if I reviewed the VIN for those that think this works I will find the same Trigger created message that just happene to fall on the day in question.

 

[Mach-Lee]

Yeah I wouldn't buy into the 10 key cycle thing, sounds like someone on BEV support was just confused about a process. The OTA updates are triggered by your VIN being set to get an OTA update on Ford's end, nothing your car does matters.

Here is the OTA Status Log from one of our MMEs recent OTAs.

Note the "Trigger created on TMC", that means Ford designated our VIN as able to retrieve an OTA update.

Then at 4:26PM when my wife left work, the car acknowledged that an OTA Trigger is Available.

Then the update started "delivering" to the car at the next power cycle at 6PM.

That "Trigger created on TMC" is on Ford's end, it has nothing at all to do with how many times you cycle your car. She was working at the time that trigger was created. This site and the F-150 site have been full of the magic method to get an OTA update, but they are as far as I can see just correlation, not causation. I have had two vehicles, the F-150 and MME, that get OTA updates. If this worked then I wouldn't have received my BlueCruise OTA on the F-150 3 months after others did because I definitely key cycled at least 90 times in that period.

Anyway, do whatever you want obviously, it's not like this is harmful. But I don't believe it for a second. I bet if I reviewed the VIN for those that think this works I will find the same Trigger created message that just happene to fall on the day in question.

I agree. Correlation does not mean causation.

The 10 key cycle is a very specific fix for a lack of a GWM update in regards to expired BlueCruise maps. If your HF BlueCruise works, you don’t need to do that.

When the maps update, I believe the GWM also updates the server manifest with the current module software versions. Once the server gets that update or ping from the car, more updates may be allowed by the server if it hasn’t gotten a recent manifest update. So that’s indirectly why it may trigger more updates, but it only works on cars with a “stuck” gateway module. A reminder that’s only one of many reasons why a car might not update.

I can see this devolving into a superstitious Mach-E rain dance for OTAs, but most people just need to drive their car more and it will happen as Vulnox said. If that doesn’t work, then somebody needs to look at it, because the causes of no updates are varied and there is not going to be one fix that works for everyone stuck on old software.

Sponsored