OTA 1.7.1 Stuck, anyone else have issue updating?

[theganyo]

Call Ford's engineering support team at 1-800-392-3673 and open a case. The more voices on this, the better. When I spoke with them, they basically told me it was a rare issue and they haven't had many complaints about it -- I beg to differ.

I haven't received a successful OTA update yet (of any version) and I've had the car since July. I haven't called to open a case because: 1. It doesn't seem to do anyone any good, 2. it seems like updates are totally random and failures are common, and 3. I figured they can see the failure(s) in their logs anyway.

Sponsored

 

[Jonrd2000]

Some progress, still says 1.7.1 installed and no new features, but Automatic updates is now set to 'on', and I now have a Sync version instead of dashes

Update:
I messaged the Ford Social Media account on here, and they made a case for me. I called the number they gave me, and the person there said this is a known issue and that if you have been stuck for more than 2 weeks, take it to the dealer. I called my dealer and apparently there are several updates available for my vehicle for 'customer experience' that fixes the ability to get updates, range in cold weather, and other things. I have my dealer appt next Thursday and I will update as to whether this is successful.

 

[Logal727]

I haven't received a successful OTA update yet (of any version) and I've had the car since July. I haven't called to open a case because: 1. It doesn't seem to do anyone any good, 2. it seems like updates are totally random and failures are common, and 3. I figured they can see the failure(s) in their logs anyway.

Do you have Securialert available? My July build was the same way with no OTA for 2 1/2 months and I finally got 1.6, then 1.4 last week. Looks like they are still catching up. Hopefully the gap to get 1.7.1 is shorter.

 

[Logal727]

My car was built 3/2021. I have received 3 OTA updates, a "bug fix" soon after buying the car, followed by Powerup 1.4 and 1.6. All went with no issues. I then brought the car to the dealer to perform the PaaK update, along with DSP and the loud fan while charging update.

What is strange to me is that when I pressed update on the second 1.7.1 install attempt, it downloaded "stuff" over a 2 day period, first was ~2GB, and then ~2.5GB the next day. The first time it failed, it downloaded almost 5GB in one go. From the other 1.7.1 thread, IIRC it should be nearly 8GB.

It seems everyone with the failed 1.7.1 has the Chinese character in place of the TM, and gets cutoff at "yo". I'm curious to know if the update notes get straightened out if/when 1.7.1 does get installed successfully. And how about those who got it installed successfully the first time, were the update notes also messed up?

Seems this is a trend with earlier builds (June 20 to June 21), but that's just anecdotal, but I'm just wanting to see if we can get more data on that.

 

[darinminter]

Mine too. How do we get the update to complete the installation?

 

[darinminter]

A word of caution before you take that update. Seriously. I have a 2021 Mach E 1st Edition AWD / Extended Range. It has 11k miles. It took the 1.7.1 on 11/9/21. All features appear to be working as described. However, now I am having a catastrophic issue. In the software business we call this a Severity 1 SHOWSTOPPER software defect. (Yeah, I am former software engineer and used to test and "break" very large communications systems for a living.) Here's the issue...

Came out to my car first thing this morning here in balmy Arizona. Overnight temp in garage was 55F. Charge was about 90% last night, and car was parked off charger overnight. When I went to start it first thing, all systems started to flake out. The vehicle started sending pulses of energy throughout the electrical system, pulsing the lights and sending a bursts of energy through the sound system about once per second. No systems work, app thinks car is plugged in (which it is not), not charging, and asleep. Pulses of energy continuing unabated. There is nothing I can do to stop it, and of course, the car is inoperable.

I contacted roadside assistance and am awaiting the truck to arrive now. Meantime I called the dealership in advance to get them ready for my arrival, so to speak. (First thing was I simply wanted to know if they had a qualified Mach E tech on staff. They have two.) The service manger there took my call and has been extremely helpful so far. He ran my VIN and discovered that Ford's 1.7.1 release caused the issue and that Ford has already released patches to fix it. These must be dealer installed.

Where I come from, this constitutes an abject failure to regression test new a software release to ensure it did not break anything with addition of new features. This is a common practice in the software industry, and any software dev organization with any process maturity level whatsoever would know this. Very unfortunate that Ford has let this issue escape their labs, made their customers software testers.

Long story short, my advice is take control of your OTA updates. Don't let them just send them automatically. You schedule each one yourself. 99.999% of the time these types of issues are generally discoverable BEFORE the update goes out to the customers - if Ford, or any other OEM for that matter, has a mature software development operation that knows how to architect, write, integrate and test complex system software such as that required to run an electric vehicle . (6 sigma, anyone?) So before scheduling that update, do your research on the latest software version to identify if any catastrophic issues have resulted. Ford clearly does not have the mechanism in place to prevent such an issue from going out to the field / its customers. My car is a brick right now. So not cool.

 

[Logal727]

A word of caution before you take that update. Seriously. I have a 2021 Mach E 1st Edition AWD / Extended Range. It has 11k miles. It took the 1.7.1 on 11/9/21. All features appear to be working as described. However, now I am having a catastrophic issue. In the software business we call this a Severity 1 SHOWSTOPPER software defect. (Yeah, I am former software engineer and used to test and "break" very large communications systems for a living.) Here's the issue...

Came out to my car first thing this morning here in balmy Arizona. Overnight temp in garage was 55F. Charge was about 90% last night, and car was parked off charger overnight. When I went to start it first thing, all systems started to flake out. The vehicle started sending pulses of energy throughout the electrical system, pulsing the lights and sending a bursts of energy through the sound system about once per second. No systems work, app thinks car is plugged in (which it is not), not charging, and asleep. Pulses of energy continuing unabated. There is nothing I can do to stop it, and of course, the car is inoperable.

I contacted roadside assistance and am awaiting the truck to arrive now. Meantime I called the dealership in advance to get them ready for my arrival, so to speak. (First thing was I simply wanted to know if they had a qualified Mach E tech on staff. They have two.) The service manger there took my call and has been extremely helpful so far. He ran my VIN and discovered that Ford's 1.7.1 release caused the issue and that Ford has already released patches to fix it. These must be dealer installed.

Where I come from, this constitutes an abject failure to regression test new a software release to ensure it did not break anything with addition of new features. This is a common practice in the software industry, and any software dev organization with any process maturity level whatsoever would know this. Very unfortunate that Ford has let this issue escape their labs, made their customers software testers.

Long story short, my advice is take control of your OTA updates. Don't let them just send them automatically. You schedule each one yourself. 99.999% of the time these types of issues are generally discoverable BEFORE the update goes out to the customers - if Ford, or any other OEM for that matter, has a mature software development operation that knows how to architect, write, integrate and test complex system software such as that required to run an electric vehicle . (6 sigma, anyone?) So before scheduling that update, do your research on the latest software version to identify if any catastrophic issues have resulted. Ford clearly does not have the mechanism in place to prevent such an issue from going out to the field / its customers. My car is a brick right now. So not cool.

Damn, that’s crazy. I wonder if the service manager is referring to the new CSP that updates all the modules on builds up to June 21, sure seems like it.

 

[theganyo]

Do you have Securialert available? My July build was the same way with no OTA for 2 1/2 months and I finally got 1.6, then 1.4 last week. Looks like they are still catching up. Hopefully the gap to get 1.7.1 is shorter.

My build is 11/2020, but bought it as a demo in July. The SecureAlert option does show up in the app, (although it says FordPass isn't responding).

 

[Jonrd2000]

Damn, that’s crazy. I wonder if the service manager is referring to the new CSP that updates all the modules on builds up to June 21, sure seems like it.

I'm wondering the same thing too. I think that is what I am getting updated next week. My build week was in May.

 

[Illinibird]

A word of caution before you take that update. Seriously. I have a 2021 Mach E 1st Edition AWD / Extended Range. It has 11k miles. It took the 1.7.1 on 11/9/21. All features appear to be working as described. However, now I am having a catastrophic issue. In the software business we call this a Severity 1 SHOWSTOPPER software defect. (Yeah, I am former software engineer and used to test and "break" very large communications systems for a living.) Here's the issue...

Came out to my car first thing this morning here in balmy Arizona. Overnight temp in garage was 55F. Charge was about 90% last night, and car was parked off charger overnight. When I went to start it first thing, all systems started to flake out. The vehicle started sending pulses of energy throughout the electrical system, pulsing the lights and sending a bursts of energy through the sound system about once per second. No systems work, app thinks car is plugged in (which it is not), not charging, and asleep. Pulses of energy continuing unabated. There is nothing I can do to stop it, and of course, the car is inoperable.

I contacted roadside assistance and am awaiting the truck to arrive now. Meantime I called the dealership in advance to get them ready for my arrival, so to speak. (First thing was I simply wanted to know if they had a qualified Mach E tech on staff. They have two.) The service manger there took my call and has been extremely helpful so far. He ran my VIN and discovered that Ford's 1.7.1 release caused the issue and that Ford has already released patches to fix it. These must be dealer installed.

Where I come from, this constitutes an abject failure to regression test new a software release to ensure it did not break anything with addition of new features. This is a common practice in the software industry, and any software dev organization with any process maturity level whatsoever would know this. Very unfortunate that Ford has let this issue escape their labs, made their customers software testers.

Long story short, my advice is take control of your OTA updates. Don't let them just send them automatically. You schedule each one yourself. 99.999% of the time these types of issues are generally discoverable BEFORE the update goes out to the customers - if Ford, or any other OEM for that matter, has a mature software development operation that knows how to architect, write, integrate and test complex system software such as that required to run an electric vehicle . (6 sigma, anyone?) So before scheduling that update, do your research on the latest software version to identify if any catastrophic issues have resulted. Ford clearly does not have the mechanism in place to prevent such an issue from going out to the field / its customers. My car is a brick right now. So not cool.

The OTA Update Team from Ford gave up trying to load version 1.7.1 and told me to have the dealer do it. They are supposed to do the CSP Software Update first which is supposed to address OTA update problems. I hope this all works and my car isn't "bricked" like yours was. They will do this in conjunction with the 2 glass recalls. I'm scheduled to leave my car with them Monday at 7 am. The Service Writer told me the last Mach E recall they did for the windshield/panoramic roof took the body shop 3-4 days and 1 day for CSP Software Calibration/OTA 1.7.1 update. Hopefully he is right.

 

[Kabish]

I had high hopes that 1.7.1 was going to actually install this time. So far all its done is change my sat radio favorites, turned off the camera delay, and keeps shutting off the option to not ask about the alarm when you get out.

I had the grayed out Auto Update for a day or two, now its back and when I check the version it just says something along the lines of Your car is up to date, won't display version numbers.

I can deal with the other stuff (although annoying), but it continually shutting of the camera delay is annoying the hell out of me. The cameras in this car shut off WAAAAAAAAY too damn fast.

 

[theganyo]

I can deal with the other stuff (although annoying), but it continually shutting of the camera delay is annoying the hell out of me. The cameras in this car shut off WAAAAAAAAY too damn fast.

Interesting. I've set the rear camera delay setting on several times, but it never sticks... and that has nothing to do with 1.7.1, since I don't have that.

 

[sockmeister]

A word of caution before you take that update. Seriously. I have a 2021 Mach E 1st Edition AWD / Extended Range. It has 11k miles. It took the 1.7.1 on 11/9/21. All features appear to be working as described. However, now I am having a catastrophic issue. In the software business we call this a Severity 1 SHOWSTOPPER software defect. (Yeah, I am former software engineer and used to test and "break" very large communications systems for a living.) Here's the issue...

Came out to my car first thing this morning here in balmy Arizona. Overnight temp in garage was 55F. Charge was about 90% last night, and car was parked off charger overnight. When I went to start it first thing, all systems started to flake out. The vehicle started sending pulses of energy throughout the electrical system, pulsing the lights and sending a bursts of energy through the sound system about once per second. No systems work, app thinks car is plugged in (which it is not), not charging, and asleep. Pulses of energy continuing unabated. There is nothing I can do to stop it, and of course, the car is inoperable.

I contacted roadside assistance and am awaiting the truck to arrive now. Meantime I called the dealership in advance to get them ready for my arrival, so to speak. (First thing was I simply wanted to know if they had a qualified Mach E tech on staff. They have two.) The service manger there took my call and has been extremely helpful so far. He ran my VIN and discovered that Ford's 1.7.1 release caused the issue and that Ford has already released patches to fix it. These must be dealer installed.

Where I come from, this constitutes an abject failure to regression test new a software release to ensure it did not break anything with addition of new features. This is a common practice in the software industry, and any software dev organization with any process maturity level whatsoever would know this. Very unfortunate that Ford has let this issue escape their labs, made their customers software testers.

Long story short, my advice is take control of your OTA updates. Don't let them just send them automatically. You schedule each one yourself. 99.999% of the time these types of issues are generally discoverable BEFORE the update goes out to the customers - if Ford, or any other OEM for that matter, has a mature software development operation that knows how to architect, write, integrate and test complex system software such as that required to run an electric vehicle . (6 sigma, anyone?) So before scheduling that update, do your research on the latest software version to identify if any catastrophic issues have resulted. Ford clearly does not have the mechanism in place to prevent such an issue from going out to the field / its customers. My car is a brick right now. So not cool.

That sounds very much like a dead 12v battery. Almost the exact same symptoms have followed others in this forum who had this problem earlier in the year.
Granted, the car should be charging the 12v, but I don't think the 1.7.1 update is to blame here.

 

[Logal727]

That sounds very much like a dead 12v battery. Almost the exact same symptoms have followed others in this forum who had this problem earlier in the year.
Granted, the car should be charging the 12v, but I don't think the 1.7.1 update is to blame here.

Yeah will probably be addressed through the CSP I’m guessing.

 

[Kabish]

Interesting. I've set the rear camera delay setting on several times, but it never sticks... and that has nothing to do with 1.7.1, since I don't have that.

This seems to be the entire issue. You get 1.7.1 (without any type of notification) and it takes three weeks for it to actually install fully. I don't have 1.7.1 either, but when I got the first attempted install about a month or so ago I had four symptoms that led me to look at what was going on.
-Main Display went dark (not had this issue with the current attempt)
-Alarm always asking to turn off motion
-Camera delay
-Channel presets changing

Prior to the recent attempt of 1.7.1 my camera delay worked just fine. So you car could be in the same limbo where 1.7.1 is trying to do something but having issues.

Sponsored