BlueCruise going out OTA to regular plebs (non-EA owners)!

Mathington

Well-Known Member
Joined
Jul 6, 2021
Threads
20
Messages
882
Reaction score
868
Location
Canada
Vehicles
Mach-E Premium SR AWD
Country flag
You're seeing the same as me. No retry listed. Date of last try on 5/16. I went and set my car to not automatically install so hopefully I'd get the chance to manually tell it a good time versus when I'm in the middle of a bunch of starts and stops. But waiting sucks when so many people in these threads reported near immediate retries.
Did you have any APIM or install issues with 1.7.1?
Sponsored

 

Dnorwood98

Well-Known Member
First Name
D
Joined
Mar 18, 2021
Threads
16
Messages
330
Reaction score
269
Location
WA
Vehicles
2025 Shadow Black AWD Ext Range/2021 Carbonized Gray AWD Ext Range (Previous)
Occupation
Education/Healthcare
Country flag
Got 2.6 on Monday, 2.7.1 on Tuesday (did significant driving both days). So far I have not seen 2.7.2 pending in JSON. Might just go for a drive today after work just to see if that might trigger the download.
 

Logal727

Well-Known Member
First Name
C
Joined
Aug 23, 2021
Threads
101
Messages
7,351
Reaction score
11,347
Location
Florida
Vehicles
‘21 Carbonized Gray Mustang Mach-E Premium AWD Ext
Country flag
Just based on checking several people's OTA failures over the last few months, It seems like if you get a failure, and it doesn't retry, it is either because Ford cancelled the deployment, or your car already had that update and it won't try again.
It’s one of these reasons I think
 

Mathington

Well-Known Member
Joined
Jul 6, 2021
Threads
20
Messages
882
Reaction score
868
Location
Canada
Vehicles
Mach-E Premium SR AWD
Country flag
It’s one of these reasons I think
If my car had some of the updates and that caused 2.6.0 to fail, why wouldn't I get the other 2.7 and later updates?

I would love to have a way to get more information on why it failed.
 

ZuleMME

Well-Known Member
First Name
Zule
Joined
Apr 23, 2021
Threads
10
Messages
1,018
Reaction score
1,487
Location
Denver, CO
Vehicles
21' Job1 P4X MME, 22' MYP
Occupation
Implementation Engineer
Country flag
Did you have any APIM or install issues with 1.7.1?
Oh yes, I have the weird state of being one of the only (if not THE only) Mach-E that failed on 1.7.1 but managed to take the update without the "fix" via timing it during the GWM timeout. Essentially my understanding is my car's internal database is likely still completely fubar'd but I'm running the 1.7.1 APIM software. I do NOT have the 2.3/2.6 APIM as proven by only having the original drawing app.

It's possible my TCU is already updated, unknown.
 


Mathington

Well-Known Member
Joined
Jul 6, 2021
Threads
20
Messages
882
Reaction score
868
Location
Canada
Vehicles
Mach-E Premium SR AWD
Country flag
Oh yes, I have the weird state of being one of the only (if not THE only) Mach-E that failed on 1.7.1 but managed to take the update without the "fix" via timing it during the GWM timeout. Essentially my understanding is my car's internal database is likely still completely fubar'd but I'm running the 1.7.1 APIM software. I do NOT have the 2.3/2.6 APIM as proven by only having the original drawing app.

It's possible my TCU is already updated, unknown.
I had my APIM replaced and the dealership did a ton of updates (some which failed a bunch) and then they had to update the GWM, to fix a missing serial number, before I was finally updated to what I think is 2.3.0.

My Sync version is 2.4.4 and I have full screen CarPlay and the ability to schedule updates every day of the week.

It's very possible that our APIM and OTA issues were not entirely fixed with the updates via FDRS.
 
Last edited:

Logal727

Well-Known Member
First Name
C
Joined
Aug 23, 2021
Threads
101
Messages
7,351
Reaction score
11,347
Location
Florida
Vehicles
‘21 Carbonized Gray Mustang Mach-E Premium AWD Ext
Country flag
I had my APIM replaced and the dealership did a ton of updates (some which failed a bunch) and then they had to update the GWM, to fix a missing serial number, before I was finally updated to what I think is 2.3.0.

My Sync version is 2.4.4 and I have full screen CarPlay and the ability to schedule updates every day of the week.

It's very possible that our APIM and OTA issues were not entirely fixed with the updates via FDRS.
I haven’t had any of the previous issues with OTA
 

GrisGris

Well-Known Member
Joined
Dec 29, 2020
Threads
2
Messages
198
Reaction score
148
Location
Tampa
Vehicles
'21 Premium RR ER AWD
Country flag
https://en.wikipedia.org/wiki/Ford_Power-Up_Version_History

Once you hit 2.8.2 BlueCruise should start working. The final update is 2.8.3.
Interesting. I just got my car back from the dealer after they took a couple days to do the BC and (the rest of what they previously missed of) the 21P22 updates.

I noticed in the widget that OTA status changed today from a 2.60 update failure to a 2.8.2 update failure. I assumed that this was because the dealer just installed it. I haven't jumped on the interstate yet but found it interesting that when I turned on ACC on a local road on the way home, it told me that BC was now going to activate (which it of course didn't). I also just got a FordPass message indicating that my free BC period has now started.

All of that is to ask...shouldn't 2.8.3 have also been installed if the latest?
 

BMT1071

Well-Known Member
First Name
Mike
Joined
Mar 21, 2021
Threads
65
Messages
3,197
Reaction score
4,377
Location
Glendale, AZ
Vehicles
21 MME SR RWD, 23 MME GTPE
Occupation
EV Technical Trainer
Country flag
Anyone know what to make of the 'Final Action: "Not Set"'??
Ford Mustang Mach-E BlueCruise going out OTA to regular plebs (non-EA owners)! Screenshot_20220519-184503_Ford Status Widget


Trying to figure out why my update train stopped after Monday's successful install of 2.6
 

Logal727

Well-Known Member
First Name
C
Joined
Aug 23, 2021
Threads
101
Messages
7,351
Reaction score
11,347
Location
Florida
Vehicles
‘21 Carbonized Gray Mustang Mach-E Premium AWD Ext
Country flag
Anyone know what to make of the 'Final Action: "Not Set"'??
Screenshot_20220519-184503_Ford Status Widget.jpg


Trying to figure out why my update train stopped after Monday's successful install of 2.6
That field for failure is where it says “General Failure will retry”
 
 







Top