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

[Mike G]

I think we are in dependency purgatory from that July IPC update.

"We" as in all model years and trims?

Sponsored

 

[WyldStallyn]

"We" as in all model years and trims?

I should have mentioned @Neil4Real specifically instead of just quoting, I'm not sure which model years had the IPC update in July but I know we both installed it. We have had the same issues since with unusual FDRS GWM updates and delays on OTA for GWM. May just be paranoia.

 

[HuntingPudel]

I should have mentioned @Neil4Real specifically instead of just quoting, I'm not sure which model years had the IPC update in July but I know we both installed it. We have had the same issues since with unusual FDRS GWM updates and delays on OTA for GWM. May just be paranoia.

It’s not paranoia if they really are out to get you. ??

 

[Neil4Real]

I should have mentioned @Neil4Real specifically instead of just quoting, I'm not sure which model years had the IPC update in July but I know we both installed it. We have had the same issues since with unusual FDRS GWM updates and delays on OTA for GWM. May just be paranoia.

Yep, total bummer. I have no GWM still.

 

[Mike G]

Yep, total bummer. I have no GWM still.

Are you still at "-NAE" or are you now at "-PAE"?

 

[WyldStallyn]

Are you still at "-NAE" or are you now at "-PAE"?

I don't recall but @benk016 said -LKC which sounds right.

 

[Mach-Lee]

I think we are in dependency purgatory from that July IPC update.

Yes, it's looking like if you updated back then and have PJ8T-14C026-AA for IPC your dependency chain is broken for GWM updates. They probably released that update into FDRS by mistake. Unfortunately, releasing the wrong updates in FDRS seems to keep happening with regularity, and it messes up future OTAs. They really need to implement a more robust auditing process that makes it virtually impossible to release the wrong software in FDRS (or OTA because that can happen too). I've been screwed over by it several times and it takes ages to fix (or never).

Pro tip - because you can never trust if a new update is a mistake, always wait a week or longer before applying it. If it was a mistake, hopefully it gets removed in that time.

Also try to archive your downloaded software files so you can manually restore correct versions if necessary. This has proven invaluable in some cases.

 

[Neil4Real]

Yes, it's looking like if you updated back then and have PJ8T-14C026-AA for IPC your dependency chain is broken for GWM updates. They probably released that update into FDRS by mistake. Unfortunately, releasing the wrong updates in FDRS seems to keep happening with regularity, and it messes up future OTAs. They really need to implement a more robust auditing process that makes it virtually impossible to release the wrong software in FDRS (or OTA because that can happen too). I've been screwed over by it several times and it takes ages to fix (or never).

Pro tip - because you can never trust if a new update is a mistake, always wait a week or longer before applying it. If it was a mistake, hopefully it gets removed in that time.

Also try to archive your downloaded software files so you can manually restore correct versions if necessary. This has proven invaluable in some cases.

Damn, so it was the IPC that done bunked me! I thought I waited a few days, but maybe not since I posted what changes were part of it. Hopefully they can un-bork our situation so we get them rolling again!

 

[benk016]

Yes, it's looking like if you updated back then and have PJ8T-14C026-AA for IPC your dependency chain is broken for GWM updates. They probably released that update into FDRS by mistake. Unfortunately, releasing the wrong updates in FDRS seems to keep happening with regularity, and it messes up future OTAs. They really need to implement a more robust auditing process that makes it virtually impossible to release the wrong software in FDRS (or OTA because that can happen too). I've been screwed over by it several times and it takes ages to fix (or never).

Pro tip - because you can never trust if a new update is a mistake, always wait a week or longer before applying it. If it was a mistake, hopefully it gets removed in that time.

Also try to archive your downloaded software files so you can manually restore correct versions if necessary. This has proven invaluable in some cases.

FYI, this IPC update is still available to cars that haven't updated yet. So if anyone sees an IPC update, I would hold off for the time being.

 

[HuntingPudel]

<SNIP>
Hopefully they can un-bork our situation so we get them rolling again!

Un-borking is similar to re-virginizing in that it is very time-consuming and often doesn’t result in the desired outcome. ??

 

[Eric_C_Boston]

Un-borking is similar to re-virginizing in that it is very time-consuming and often doesn’t result in the desired outcome. ??

Yeah, the car needs to be shipped to the Ford Unbork Center in the Virgin Islands.

 

[Mike G]

Yeah, the car needs to be shipped to the Ford Unbork Center in the Virgin Islands.

Sounds like it’s time to do a server rollback.

 

[Mike G]

Yes, it's looking like if you updated back then and have PJ8T-14C026-AA for IPC your dependency chain is broken for GWM updates. They probably released that update into FDRS by mistake. Unfortunately, releasing the wrong updates in FDRS seems to keep happening with regularity, and it messes up future OTAs. They really need to implement a more robust auditing process that makes it virtually impossible to release the wrong software in FDRS (or OTA because that can happen too). I've been screwed over by it several times and it takes ages to fix (or never).

Pro tip - because you can never trust if a new update is a mistake, always wait a week or longer before applying it. If it was a mistake, hopefully it gets removed in that time.

Also try to archive your downloaded software files so you can manually restore correct versions if necessary. This has proven invaluable in some cases.

I apparently did do this IPC update according to the revision number you referenced.

But I did subsequently receive notification of a GWM update in FDRS, applied that update, and then coincidentally was notified the next day that OTA 5.1.1 had been applied.

I am now at "-EAL" GWM rev on my GT.

So you're saying that I won't get whatever OTA 6.1.0 rev is supposed to be for my GT until we fake the server out by doing a make-believe rollback on the IPC, like we had to do on the PCM back at the start of the year?

 

[WyldStallyn]

I apparently did do this IPC update according to the revision number you referenced.

But I did subsequently receive notification of a GWM update in FDRS, applied that update, and then coincidentally was notified the next day that OTA 5.1.1 had been applied.

I am now at "-EAL" GWM rev on my GT.

So you're saying that I won't get whatever OTA 6.1.0 rev is supposed to be for my GT until we fake the server out by doing a make-believe rollback on the IPC, like we had to do on the PCM back at the start of the year?

I believe this is a 2021 issue only. We haven’t had a successful GWM since the IPC update.

 

[Mike G]

I believe this is a 2021 issue only. We haven’t had a successful GWM since the IPC update.

Ahh so Lee's statement needed a bit of qualification then. I knew the IPCs on GTs were not the same as all other trims, and so in addition to that, there's a model year dimension to this particular dependency knot as well I guess.

Sponsored