I just got BlueCruise 1.3 on my 2022

[SonicBlue]

2023s shipped with 1.2, 2022s had 1.0. If I had to guess, they are giving it to the people with the least first.

Well the 21s have had the least for far longer…

Sponsored

 

[SonicBlue]

My point was that EA gets it first. In year order. Then non-EA. So if a 2022 got it and a 2021 says "I didn't", maybe the 2022 is EA and the 2021 is not.

Nope. I’m a 2021 EA. And I’ve not heard any other 21 EAs getting it, either.

 

[RickMachE]

Nope. I’m a 2021 EA. And I’ve not heard any other 21 EAs getting it, either.

So, Ford's email that said "by model year" is BS...

 

[SonicBlue]

So, Ford's email that said "by model year" is BS...

Well no, it just means that the 22 model year is going first.

 

[Just Lurking]

For folks that have 1.3, how does it handle stop-and-go traffic while in Unbridle and One Pedal?

That's the setting I typically use, but I find in stop-and-go traffic BlueCruise is very herky-jerky.

When I get to slow traffic I usually throw it in Whisper mode and turn off one-pedal drive, which is much smoother. I'm hoping they fixed this in 1.3.

I find that it’s fine.

But it also depends on how many following distance bars you have set. It’s a range: Unbridle with 1 bar is the most aggressive, Whisper with 4 bars is the least aggressive. The aggressiveness (herky-jerky) of the acceleration and deceleration will vary on that spectrum. You have to find the right balance of drive mode and following distance for you.

Interesting that it varies by setting, I hadn't considered that. Unbridled 1-pedal is my standard driving mode and I find BC too abrupt and jerky to use in traffic.

I'll experiment with different modes, but I do hope this is something that can be improved so that I don't need to fuss with drive mode settings while driving. My other (non-Ford) car has much smoother cruise control in traffic.

 

[Digitalsteve]

Interesting that it varies by setting, I hadn't considered that. Unbridled 1-pedal is my standard driving mode and I find BC too abrupt and jerky to use in traffic.

I'll experiment with different modes, but I do hope this is something that can be improved so that I don't need to fuss with drive mode settings while driving. My other (non-Ford) car has much smoother cruise control in traffic.

I use BC 2 all the time in traffic and it is very smooth, usually in comfort mode. Distance set to 2 or 3.

 

[Mantastic]

Great that we're finally getting 1.3 after a year's wait, but that really makes me wonder what happened with 1.4 and what's apparently been so unfixable for it that they didn't go straight to that like they advertised.

I know that there were some concerning issues with some people experiencing car charging lockouts, but you're telling me that bug couldn't have been fixed and tested by now?

 

[azerik]

But I’m leery of making any changes that could impact future OTAs.

Exactly.

Is this a setting or does it just do it? I looked in the settings and I couldn’t find it.

Sadly there isn't a setting to turn this off. Once again a feature gets enabled with some dumb ass requirement that'll piss of the other half.

I know that there were some concerning issues with some people experiencing car charging lockouts, but you're telling me that bug couldn't have been fixed and tested by now?

It's only been a year. The fix will require another dev group to get up to speed on why 1.4 doesn't 1.4 anymore. That'll be another couple years if I had to guess. Perhaps in 2030 BC will be logical and they might have a handle on how software used to work in 2024 so they can start using that deployment style in 2030. /rant off

 

[Just Lurking]

I use BC 2 all the time in traffic and it is very smooth, usually in comfort mode. Distance set to 2 or 3.

Good to know. You mean BC 1.2, right? I have BC 1.0 and perhaps when I get BC 1.3 it will be improved, even in unbdridled / 1-pedal. I forgot to mention I usually have follow distance set to max or sometimes 1 less than max.

 

[rugedraw]

I don’t recall the original 1.3/1.4 features mentioning the suggested lane changes. Am I recalling incorrectly? I’ve used FDRS and Forscan to get BC 1.3456 and haven’t seen this prompt yet.

You may be missing the IPC update that gives you the animations associated with the new features.

 

[hybrid2bev]

Interesting that it varies by setting, I hadn't considered that. Unbridled 1-pedal is my standard driving mode and I find BC too abrupt and jerky to use in traffic.

I'll experiment with different modes, but I do hope this is something that can be improved so that I don't need to fuss with drive mode settings while driving. My other (non-Ford) car has much smoother cruise control in traffic.

Yeah, give it a try. I used to switch drive modes/distance too with BC 1.0, but now I mostly use Unbridle and 1 bar and it's fine.

But keep in mind it also depends on the person in front of you too. If their driving style is only full throttle and full braking then it can lead to a 'jerky' experince for you in stop and go traffic. (This is the situation where a greater following distance can help mitigate. )

 

[DaddyDeuce]

But I’m leery of making any changes that could impact future OTAs.

Is that possible? Changes made using FDRS or Forscan blocking OTAs?

 

[rugedraw]

Is that possible? Changes made using FDRS or Forscan blocking OTAs?

FDRS supersedes OTA's. If you fully update with FDRS, there is nothing for the OTA process to do.

Unless you makes some FORScan changes to the TCU that disables connectivity, then no, FORScan changes will not prevent updates from coming in.

 

[azerik]

Is that possible? Changes made using FDRS or Forscan blocking OTAs?

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.

FDRS supersedes OTA's. If you fully update with FDRS, there is nothing for the OTA process to do.

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_machinist]

I'm assuming those getting this were already on or really close to 6.14. Unlike the majority of 21's that are on something less than 6.8. I think the 21's are still far away from the soon timeline. The 22's have been close since like January. But this is rolling out to EA, which means we could well have months more silence before it rolls out publically.

My ‘21 had 6.14

Sponsored