OTA 1.7.1 Stuck, anyone else have issue updating?

[SashaLondon]

Get excited everyone its MARCH!!!! Where is the fix??

Sponsored

 

[MrRossKeys]

Get excited everyone its MARCH!!!! Where is the fix??

...

 

[aevans17]

Just got off the phone with my dealer. They read me the exact text from SSM-50383. So no new updates from Ford and the Ford Tech couldn't give them any additional information on when the fix is coming.

 

[Kangio]

Just spoke to my dealership, who are currently working on the wind noise remediation (which got worse AFTER doing the windshield recall fix). They spoke with Ford today who told them my car qualifies for a "gateway module" replacement, which they said would fix the OTA update issue. Not sure yet how long for the part. I am very skeptical this will work. BTW, the service guys at this dealership had no knowledge of any of this.

 

[benk016]

Just spoke to my dealership, who are currently working on the wind noise remediation (which got worse AFTER doing the windshield recall fix). They spoke with Ford today who told them my car qualifies for a "gateway module" replacement, which they said would fix the OTA update issue. Not sure yet how long for the part. I am very skeptical this will work. BTW, the service guys at this dealership had no knowledge of any of this.

I've been speculating that this was actually a GWM issue for a while. There is a good chance that will actually fix the issue.

 

[Kamuelaflyer]

Ford Tech couldn't give them any additional information on when the fix is coming.

At this point, if I were in this position, I’d be inclined to add an “or if” to that sentence right after the “when”.

 

[Blue highway]

It is likely an issue of software combined with a specific version of one or more modules. If it was only a software issue, then the Job 2 vehicles would have the same issues as Job 1.

Lets assume that it is indeed both the APIM and GWM. This would actually compound Fords supply problems.

If there were no semiconductor shortage, its reasonable to presume that Ford would/could take a different route.

Development teams and Electrical Engineer teams get expensive really really quickly. But when the alternative is to reduce production of a high margin product with a typical $50k-70k selling price multiplied by a few hundred thousand vehicles. You can see why Ford prefers to wait and see if they can fix the software first.

I can imagine the conversations in Ford... "this isn't that big of a problem" "most people don't even notice" "All the new cars are fine, let's not go overboard here"

 

[hybrid2bev]

https://www.macheforum.com/site/thr...ance-feature-concerns-and-or-ipma-dtcs.15055/

A IPMA fix may be available this month.

 

[Blue highway]

honestly, they'll just tell you the fix ain't available yet because Ford hasn't released anything on FDRS for them to apply on the car.

I have very good hopes until tomorrow at midnight, then we can get the pitchforks and go to Michigan.

 

[gnaark]

https://www.macheforum.com/site/thr...ance-feature-concerns-and-or-ipma-dtcs.15055/

A IPMA fix may be available this month.

I have read through it and I don't see how it's relevant to the car getting no OTA

 

[Smolinski]

So, I think I made this recommendation before. Every week, we take our car in for repair, they cannot fix, we rate the experience a 1, poor. Enough poor ratings may get their attention.

The other approach would to find the auto show in your city and sit by the Mustang at the Ford booth and tell folks that Ford does not stand by their products

 

[Illinibird]

Once again it's communication by Ford (or lack thereof). I have tried 3 times now to reach out to one of my contacts at Ford who told me mid January that the fix was coming "soon" and then I haven't heard a word from her since. It seems Ford is "stonewalling" all of us with this problem and won't at least tell us what the delay is (I've heard the conjecture about the first "fix" not working on all cars but nothing official by Ford). I've written to my contact again today pleading with her to at least acknowledge me and answer my e-mail to let me know what is really going on. The goal post keeps on being moved back while all of us affected sit here frustrated at there being no solution. Like I said before, Ford needs to admit defeat if a software/firmware update/flash won't fix this problem in ALL the Mach E's affected. I know there is a microchip shortage and the APIM modules may be in short supply however it does no good waiting for a solution which doesn't correct the problem and Ford might as well begin making arrangements to try a different fix. Of course, I'm whistling in the dark as we all are because I don't know what they are trying or when a realistic date will be. I'm just extremely frustrated and want my Mach E to perform as advertised. The Startup updates are well along from the 1.6 update I am stuck with (2.5?). ??

Finally, I received some communication from a Ford insider on this issue and people aren't going to be happy. Ford is testing a NEW solution to our 1.7.1 update with the Ford Management Lease vehicles and once they are satisfied the "fix" works on all cars and doesn't cause additional problems they will release the fix by the end of March (maybe sooner). The goal post keeps moving back I'm afraid. This problem must be a a lot bigger then what we all thought originally. Bottom line, continue to wait and hope that the March date(s) finally put this whole problem to rest.

The last line read "We truly appreciate your patience and willingness to participate as one of our Ford Early Access Program Members. It is because of customers like you that we were able to get this issue identified sooner and work towards a fix. We realize it has taken too long and that, we will also address." At least they appear to have copped a mea culpa in stating that this has taken too long (yah think?) and they will address that. I'd like Ford to come clean and explain what exactly is wrong and causing this problem.

 

[Kamuelaflyer]

At some point either this gets fixed or Ford does a mass buy back. Just when that theoretical point is would likely be if this crosses a safety threshold. It’s been fortunate that nothing has been safety related in the various updates yet. But having a car that can’t receive OTAs and can’t get patched at the dealer is “less than desirable.” I sincerely hope a solution is pushed very soon for all of you.

 

[gnaark]

I can’t wait to get my free 50kwh of free EA charging as reparations

 

[sid234]

Finally, I received some communication from a Ford insider on this issue and people aren't going to be happy. Ford is testing a NEW solution to our 1.7.1 update with the Ford Management Lease vehicles and once they are satisfied the "fix" works on all cars and doesn't cause additional problems they will release the fix by the end of March (maybe sooner). The goal post keeps moving back I'm afraid. This problem must be a a lot bigger then what we all thought originally. Bottom line, continue to wait and hope that the March date(s) finally put this whole problem to rest.

The last line read "We truly appreciate your patience and willingness to participate as one of our Ford Early Access Program Members. It is because of customers like you that we were able to get this issue identified sooner and work towards a fix. We realize it has taken too long and that, we will also address." At least they appear to have copped a mea culpa in stating that this has taken too long (yah think?) and they will address that. I'd like Ford to come clean and explain what exactly is wrong and causing this problem.

Thanks for the update. I'd be shocked if we hear anything close to a proper explanation or apology from Ford for this whole debacle. It seems like they weren't really taking this issue seriously. I remain skeptical

Sponsored