Will Ford make it clear when we get the final update for Bluecruise 1.3?

[Space_Pony]

I have a BC subscription until 2026 since I bought the car this spring with BC 1.2. I suspect that there will be no changes from what I have now and that some may say that suddenly I have BC 1.3. With no way to tell what you have in the Sync description how would I ever know, unless somebody just says that's what I have.

Sponsored

 

[ChasingCoral]

What would be the reason to only start more detailed and accurate notes from 7.0 forward? Why not start now?

Perhaps the 6.x are already all written and approved. Would you prefer they write better notes if that means slowing down the updates?

 

[DevSecOps]

Perhaps the 6.x are already all written and approved. Would you prefer they write better notes if that means slowing down the updates?

That's a total fanboy comment if I've ever seen one. Really?? Already approved recycled messages from years ago? Updates will be slowed because copy needs to be written? Give me a break.

When releasing software it's 2 seconds of time to generate a change log of completed bugs, tasks and stories. If they can't summarize that without delay then no one should ever buy another Ford. That's next level incompetency.

 

[milepost1]

Nope says summer, not summer 2023. You mistook it to mean summer 2023. So still on schedule. We just don't know which summer. Lol

 

[RickMachE]

Perhaps the 6.x are already all written and approved. Would you prefer they write better notes if that means slowing down the updates?

Oh come on. My 13 year old granddaughter could write the release notes, after a 15 minute discussion with a person aware of what they contained.

Editing the text file that goes with the updates is simple stuff.

Koolaid anyone?

 

[ChasingCoral]

Oh come on. My 13 year old granddaughter could write the release notes, after a 15 minute discussion with a person aware of what they contained.

Editing the text file that goes with the updates is simple stuff.

Koolaid anyone?

Write, yes. Approved is the big issue here. Ford is a big, old company. Approvals are slow processes.

Of course, they could go with the work fast, break things, and fix them later philosophy. Rivian bricks anyone?

 

[Blue highway]

Write, yes. Approved is the big issue here. Ford is a big, old company. Approvals are slow processes.

Of course, they could go with the work fast, break things, and fix them later philosophy. Rivian bricks anyone?

I like Ford and really like my MME... but come on... they work SLOW and break things.

As for change log, I expect to see what I see in Github for any open source project... a list of what was changed exactly.

 

[RickMachE]

Write, yes. Approved is the big issue here. Ford is a big, old company. Approvals are slow processes.

Of course, they could go with the work fast, break things, and fix them later philosophy. Rivian bricks anyone?

I'll avoid the hyperbole (did words ever break a vehicle?), but Ford knows this is an issue, and could make the word updates much easier / faster if they chose.

At this point in the OTA update process, having incorrect / incomplete descriptions of OTA updates, is well __________ [left blank on purpose]

 

[AKgrampy]

I'll avoid the hyperbole (did words ever break a vehicle?), but Ford knows this is an issue, and could make the word updates much easier / faster if they chose.

At this point in the OTA update process, having incorrect / incomplete descriptions of OTA updates, is well __________ [left blank on purpose]

. . . Is like a range question on the forum!

 

[Womps]

We should have another survey. How many owners think the majority of o.t.a. updates actually make a difference to what they were intended to improve.

 

[doogie63]

When they start there subscription fees. Maybe we should be as slow as their updates with our payments. They them check is in the mail you should get it maybe sometime in the summer.

 

[TheVirtualTim]

A few things

<soap_box_mode>

#1 ... YES ... you WILL see a message with words to the effect of "the update enables BC 1.3". I was part of the rollout of BC 1.0 (I was in the first wave of Early Access for that release) and the update made it clear.

#2 ... the updates are delivered to "batches" of cars at a time and that is intentional. Even INSIDE the Early Access Program things are released to limited batches of cars at a time. As a former software developer ... it's well and good to write code, test it, get a good result, and think it's ready. When you unleash on the world ... you'll will discover all sorts of bizarre "corner-cases" (that is an industry term) of things you would never have thought to test for ... and could never test for everything. So you roll things out slowly to build confidence that it's ready to be opened up to a broader audience.

#3 ... if you are in the Early Access Program (EAP) then keep in mind ... that's EARLY access. Things MIGHT not go well. Ford hopes they go well. We hope they go well. But if they run into issues they will hit the brakes (as they should and we should all want them to do that ... it's the responsible thing to do.)

#4 ... I know we all want the update yesterday. I want the update yesterday (really, I do!). But I don't want it yesterday at the expensive of me, you, or anyone else getting stranded. So I'm ok with the process. It has gotten better over time (it has gotten MUCH better). Are we there yet ... nope ... but the trend is improving and I'm ok with that.

</soap_box_mode>

 

[DevSecOps]

Rivian bricks anyone?

Rivian borked a few cars, less than 1%, on accident. They weren't bricked as you could still drive them. The same day they publicly admitted the error, paused the rollout and fixed it in less than 24 hours.

Ford on the other hand introduced a safety issue in 6.2.0, never admitted it publicly and 1 month later still hasn't fixed it.

There's bound to be issues, but when a company takes responsibility and fixes it immediately that's the company that I trust to keep my best interest at heart.

 

[Space_Pony]

Rivian borked a few cars, less than 1%, on accident. They weren't bricked as you could still drive them. The same day they publicly admitted the error, paused the rollout and fixed it in less than 24 hours.

Ford on the other hand introduced a safety issue in 6.2.0, never admitted it publicly and 1 month later still hasn't fixed it.

There's bound to be issues, but when a company takes responsibility and fixes it immediately that's the company that I trust to keep my best interest at heart.

Our MME has been on 6.2.0 for over a month. What is this safety issue? I'm sure you would like to keep all of your MME friends safe, so could you please reveal what this safety issue is since my wife is driving this car every day.

 

[DevSecOps]

Our MME has been on 6.2.0 for over a month. What is this safety issue? I'm sure you would like to keep all of your MME friends safe, so could you please reveal what this safety issue is since my wife is driving this car every day.

I honestly don't know and didn't ask. But keep in mind that a safety issue in the automotive world can be something as simple as an update not completing properly. The HVBJB failures weren't all safety issues in my opinion, but NHTSA classified all of them as such. I think the MME has other bugs that are safety issues, such as drive mode not available, that should have been addressed long ago, but still remain over 1 year later.

Sponsored