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

[medriver]

So it would seem occasionally doing these updates actually helps, but then again it seems like there might some unintended side effects such as with the new sync update.

It would seem every year and job has its weak spots, very hard to keep track.

What is a safe waiting period? Or just wait for the complaints to come into the forum?

Sponsored

 

[Mike G]

........ but then again it seems like there might some unintended side effects such as with the new sync update.

Ummm... Saywhatnow?

There's an unintended side effect of Sync 1122? I must have missed that.

 

[rugedraw]

I’m not sure it’s quite that straightforward. Enabling dealers to resolve the issues is also an issue in and of itself. Far too many, albeit a distinct minority, are rather intransigent in their ways. Personally, I’d rather do it myself annyway, although BC in and of itself is of no interest to me — no Bc roads here. The features that bleed over to ACC (Hands on BC) such as slowing down around the corners of interest me though.

The lack of dealer competence is what led me to the Mongoose (Somehow fitting considering I live in Hawaii), the power supply and a new laptop. And an occasional FDRS license of course.

Not trying to be argumentative, but I think it is that straight-forward. All the 21G01 guided routine does is add the config to enable BC 1.0 once the modules have been updated to the proper level. This would literally be the same thing, only the it would need to add the config for 1.4 instead of 1.0 once the ADAS modules in said vehicle are updated. The problem with this is the money and not the execution. Three hours of labor multiplied by "x" amount of vehicles as opposed to getting the OTA process to do it for free?

Like you, incompetence is what led me down the FDRS/FORScan path. It was very different back then; both Ford and dealers have gotten better over time with these things. We as a community have also learned a lot over the past 2-3 years, too. In the short history that Ford has been offering OTA's, I have yet to see a successful OTA campaign for the IPMA on any vehicle platform in Ford's line-up and I don't expect that to change any time soon. It simply has to stay in inhibit mode way too long and these EV's in particular have a tiny 12v battery that I don't think can take the stress.

So it would seem occasionally doing these updates actually helps, but then again it seems like there might some unintended side effects such as with the new sync update.

It would seem every year and job has its weak spots, very hard to keep track.

What is a safe waiting period? Or just wait for the complaints to come into the forum?

A lot of people do that; they let others be the guinea pig for new updates. Not me......I live to dive right in. However, I have the resources to go back to the previous software if something goes wrong which not everyone can do, so I understand the apprehensions some have to not install an update as soon as it is released.

 

[Snakebitten]

Well said.
I have crossed the 100 FDRS updates mark at some point in the past. I'm not saying I never experienced a head scratcher now and then. And certainly the Mach-E presented me a couple of challenges. But there's so much documentation now, as well as fellas that are incredibly generous with their aid and desire to see you succeed.

I've got a combined 6.5 years of OTA Ford ownership across multiple vehicles and a dealership has never touched a single one of them except for a sheared axle bolt recall on a truck. Less than a man hour.

 

[medriver]

Ummm... Saywhatnow?

There's an unintended side effect of Sync 1122? I must have missed that.

SSM 52574 that you posted? The latest sync update is not available to me I am assuming this is why, because its broken, that's not right as my Sync functions perfectly at this time? My inference from the bottom of that post where it said if updating it doesn't help ford would fix it in the future made me think that the update is not for everyone....maybe why it's not been OTA'd widely? Maybe I've got this wrong by sync I mean APIM update, not quite the same thing?

 

[Mike G]

SSM 52574 that you posted? The latest sync update is not available to me I am assuming this is why, because its broken, that's not right as my Sync functions perfectly at this time? My inference from the bottom of that post where it said if updating it doesn't help ford would fix it in the future made me think that the update is not for everyone....maybe why it's not been OTA'd widely? Maybe I've got this wrong by sync I mean APIM update, not quite the same thing?

Ah so..okay you're referring to the stuff like Carplay and Android Auto and the Alexa thing..etc.. gotcha.

Sorry, I've been using Sync 1122 for a little while now and haven't noticed anything. In fairness I don't use Alexa, and stopped using Carplay (I do use it on long trips).

I'm not having any issues that are show-stoppers with the latest Sync though.

Did you notice in that SSM that they don't mention a specific revision of Sync that's of concern? Just Sync 4 in general. All of Sync 4 is what they're talking about.

If you're happy with the Sync version you have that's fine. But seeing as how not updating your Sync would mean you might not get other features (like BC 1.4 whenever it arrives), that may not be a good strategy.

As to why it hasn't been OTA'd to everybody..well that's a function of a general slowdown in the rollout of all OTAs...for everybody. And don't forget...the new Sync 1122 (or any of them for that matter) have prerequisite updates that have to go out first...like an updated gateway, TCU, sometimes powertrain modules. Most updates are incremental. They walk the car forward on the software update path step by step so that all the software modules work together. It's not like Windows updates where you get a quarterly cumulative update that brings everything up to the correct level in case you missed a few patches.

The process Ford uses inches forward by degrees in an attempt to ensure that all the various modules are working with compatible software revisions of the other modules.

 

[medriver]

Ah so..okay you're referring to the stuff like Carplay and Android Auto and the Alexa thing..etc.. gotcha.

Sorry, I've been using Sync 1122 for a little while now and haven't noticed anything. In fairness I don't use Alexa, and stopped using Carplay (I do use it on long trips).


The process Ford uses inches forward by degrees in an attempt to ensure that all the various modules are working with compatible software revisions of the other modules.

I'm on 1049 and no APIM update is available to me AFAIK.

 

[Sikkun]

Working through my list and I keep getting could not communicate with vcm when trying remote function actuator. Have done several other modules without any issues.

Any thoughts?

 

[Mike G]

Working through my list and I keep getting could not communicate with vcm when trying remote function actuator. Have done several other modules without any issues.

Any thoughts?

Clear and retest all modules to make sure you're starting with a green board. Even if FDRS says they're all green now...clear and retest just to make sure.

 

[rugedraw]

Working through my list and I keep getting could not communicate with vcm when trying remote function actuator. Have done several other modules without any issues.

Any thoughts?

To add to what Mike suggested: Restarting the laptop will solve little annoying issues like this sometimes, too.

 

[LeanneL]

To add to what Mike suggested: Restarting the laptop will solve little annoying issues like this sometimes, too.

Restarting fixed errors for me on 2 different occassions!

 

[Sikkun]

Hmm still no go, going to do CMR and the other 2 long modules and loop back around to it later.

I also did not receive any updates to sync or anything after updating gateway. Is that normal?

Was hoping for Tesla Plug and Charge.

 

[rugedraw]

Hmm still no go, going to do CMR and the other 2 long modules and loop back around to it later.

I also did receive any updates to sync or anything after updating gateway. Is that normal?

Was hoping for Tesla Plug and Charge.

Yea, I see the RFA is not taking. Even after restarting the laptop? I would tell you to try a PMI and select "no" when FDRS asks if it is the original module, but if the problem is it can't communicate with the module, I am not sure that would help, but it won't hurt to try it.

No, it is not normal for it to show more updates after you did the GWM. I'll see if I can get you the next update. I'll get back to you tomorrow.

 

[Sikkun]

Yea, I see the RFA is not taking. Even after restarting the laptop? I would tell you to try a PMI and select "no" when FDRS asks if it is the original module, but if the problem is it can't communicate with the module, I am not sure that would help, but it won't hurt to try it.

No, it is not normal for it to show more updates after you did the GWM. I'll see if I can get you the next update. I'll get back to you tomorrow.

Tried restarting, clearing, etc. PMI gets the same error. But I guess I managed to reprogram the module, now the update isn’t on my list anymore…(clearly was able to communicate while doing that).

Have cleared everything from my update list though.

 

[rugedraw]

Tried restarting, clearing, etc. PMI gets the same error. But I guess I managed to reprogram the module, now the update isn’t on my list anymore…(clearly was able to communicate while doing that).

Have cleared everything from my update list though.

Oh good. I'll get back to you tomorrow and let you know if I can help with what you're missing or not.

Sponsored