I just got BlueCruise 1.3 on my 2022

[67 Stang Convertible]

Not yet, they will come later.

Don't you mean "Soon" ? ?

Sponsored

 

[SonicBlue]

Yes. If you have some module that's updated that blocks some other module from being updated based on the OTA I can see it being 'stuck'. They don't seem to have decent logic in the PU updates to updates to level the playing field to what the updates need. From what I've seen they find that out a little late and then just block the release until there's a minor update to address that logic. It would make sense that at least if you have all modules updated to 'current' you shouldn't have any issue. But if you CAN force push some module to something other than the baseline they need to have logic to allow that. (I don't know if that's actually possible with FDRS) They may well block the update because the module is newer than expected if possible. This happens in software all the time and it's the sole reason why I havn't updated my car via FDRS at all. My luck and stupid requirements don't go together.


I wonder how the OTA for BC handles this, or is there an OTA just to toggle BC to the newer version?
I'd play with this software if I didn't already play with code for 10+hrs a day. And if I had an ounce of faith in something that takes as long as FDRS to update.

This. Or, in layman’s terms, Ford has a big enough problem already making official releases play nice… without me tinkering on the back end. I wouldn’t chance it.

 

[rugedraw]

Yes. If you have some module that's updated that blocks some other module from being updated based on the OTA I can see it being 'stuck'. They don't seem to have decent logic in the PU updates to updates to level the playing field to what the updates need. From what I've seen they find that out a little late and then just block the release until there's a minor update to address that logic. It would make sense that at least if you have all modules updated to 'current' you shouldn't have any issue. But if you CAN force push some module to something other than the baseline they need to have logic to allow that. (I don't know if that's actually possible with FDRS) They may well block the update because the module is newer than expected if possible. This happens in software all the time and it's the sole reason why I havn't updated my car via FDRS at all. My luck and stupid requirements don't go together.


I wonder how the OTA for BC handles this, or is there an OTA just to toggle BC to the newer version?
I'd play with this software if I didn't already play with code for 10+hrs a day. And if I had an ounce of faith in something that takes as long as FDRS to update.

The PU updates are not the ones that need to be installed in sequence. And there is a fail-safe system within the OTA process to prevent updates that are not supposed to install from installing. I have seen countless OTA's fail due to manifest, software and hash mismatches.

This new OTA seems to be just that......it just gives you the newer version. I've been busy since this new OTA came out and have not been following this closely....has anyone on BC 1.0 reported getting this? If not, then then they are upgrading 1.2 users to 1.3 which is a much easier task than going from 1.0 to 1.3. I would assume to update from 1.0 to 1.3 will require some kind of APIM update to add the config needed for the toggle switches to appear in the driver assist menu which vehicles on 1.2 would already have.

 

[azerik]

My ‘21 had 6.14

You're much closer than I am at the moment, but I don't think the 21's will see BC 1.3 for a while. Like rugedraw mentioned they're taking the easy route first 22's -> 1.3. We first year contestants are currently on the C team roster for getting much of OTAs. I can see this going to X fairly soon that BC 1.3 has been delivered. So as to save face with the 1 year fiasco of ''soon' and 'summer' they're count any win they can. I'd put money on the majority of 21's left to wilt. Maybe next year, maybe. Right now if I had to guess there's not a whole lot of owners with 21's that got the BC coming soon mail that still own 21's. For those of the 21's that FDRS'd or got hella luck in the OTA lottery that are at 6.14 I really hope there's some FDRS way to push them into BC1.3. I have just lost faith in this model year roll out and see a mounting wall of blockers for out of warranty cars. Which is what the 21's are at this point.

Oh you have a different model. My front passenger device warns me when I'm going too fast for her comfort or a traffic light 1/2 mile ahead is red.

Yeah, this nanny drives me bonkers. Mine alerts me to cross traffic that might exist next Tuesday as well.

 

[Mr67gta]

So, I just got the 6.13. eye nanny camera update on 6/30. could this mean that bluecruise 1.3 will be soon? not in ea

 

[azerik]

6.13, 6.14 have been out for months. More likely they just turned the OTA tap back on and people are getting available updates. Until groups of NON EA people (I guess with 22's) start chiming in I'd stick with the open ended 'soon'.

 

[that_macheguy]

Well this came out of left field.

@elmedico27 IPMA update. Vehicle was in inhibited for 44 minutes. SoC was 53% when it started and 62% when it finished which makes no sense, but hey....it went through! Awesome!

how did you get this?

 

[Brons2]

Newbie question, what version of BlueCruise do the 2023s have? We just took home a new 23 last week. It seems to work fine on the freeway, in fact it seems eager to take over when you're on the freeway and the adaptive cruise is already on.

The FDRS report did not seem to say anything about BlueCruise. I just looked at it again.

This is not really a huge concern as it seems to work fine as is.

 

[rugedraw]

how did you get this?

PTS which is Ford's dealer technician website.

Newbie question, what version of BlueCruise do the 2023s have? We just took home a new 23 last week. It seems to work fine on the freeway, in fact it seems eager to take over when you're on the freeway and the adaptive cruise is already on.

The FDRS report did not seem to say anything about BlueCruise. I just looked at it again.

This is not really a huge concern as it seems to work fine as is.

FDRS will not mention that. The window sticker of your car says it shipped with 1.2.

 

[CarGuy11]

The PU updates are not the ones that need to be installed in sequence. And there is a fail-safe system within the OTA process to prevent updates that are not supposed to install from installing. I have seen countless OTA's fail due to manifest, software and hash mismatches.

This new OTA seems to be just that......it just gives you the newer version. I've been busy since this new OTA came out and have not been following this closely....has anyone on BC 1.0 reported getting this? If not, then then they are upgrading 1.2 users to 1.3 which is a much easier task than going from 1.0 to 1.3. I would assume to update from 1.0 to 1.3 will require some kind of APIM update to add the config needed for the toggle switches to appear in the driver assist menu which vehicles on 1.2 would already have.

All 2022s shipped with BC 1.0 so they are starting with the hardest.

 

[garyd9]

Newbie question, what version of BlueCruise do the 2023s have? We just took home a new 23 last week. It seems to work fine on the freeway, in fact it seems eager to take over when you're on the freeway and the adaptive cruise is already on.

Either 1.2 (job 1) or 1.3 (job 2).

 

[agoldman]

and what ver do 2024's just delivered have?

 

[garyd9]

and what ver do 2024's just delivered have?

1.3? It should state on your window sticker.

Edit: I guess they took the version off the window sticker for 2024's.

 

[agoldman]

just says blue cruise trial. is there a place in the diag screen or something that says versions?

 

[azerik]

All 2022s shipped with BC 1.0 so they are starting with the hardest.

Na, the hardest is the Job1 21's. They probably have Raspberry Pi's and old Android phones running most of the module functions in the cobbled together covid box of parts. Software coded by the only people that bothered to show up that week, drunk or sick, who quit the following week without committing the code to anywhere useful. The 22's might actually have some sort of a baseline or software and hardware.

Sponsored