BC1.3 for 2021s: How Thoughtful is Ford’s Process on the Backend?

[SonicBlue]

I have said this for a while. They'll really stop bothering soon, if they havn't already. No one wants to maintain yet another list of growing issues and work unless theres something to get out of it (read: money, only money). Now that the 21's are 'done' they'll probably push 1.3's roll out to most (because I don't think they'll come close to 75% of 22's ever getting 1.3 for one reason or another) and put a plug in that OTA spigot by the end of next year.
Thoughtfully plugging the damn up.
I just hope someone down the road figures out a way to get the files for a FAUX-TA in the future or these cars will become recyclable material before they hit ~6 years old.

I’m pretty close to agreement with you. I’ve given up hope of another major enhancement to SYNC 4A.

I do think we’ll get 1.3, eventually. But probably not until next year.

Sponsored

 

[SonicBlue]

Well, if you've got a 2021 job 1 (or even an early job 2 at this point) you're already out of warranty. I would suspect that neither you nor Ford want you to have to pay to fix a FUBARed OTA. So in that context, yes I think they are being THOUGHTFUL in making sure that all the kinks are worked out with cars they're going to be able to fix under warranty when the OTAs go south.

In fact, I would not be surprised if they stop sending OTAs at all to out of warranty cars for that reason.

But rest assured that the criticisms are terribly witty in the interim.

I’m a little skeptical that Ford would require you to pay for a bricking caused by OTA out of warranty.

Yes, yes, I know people have posted horror stories about one bad dealership experience or another, and I have no doubt we’ve disclaimed all liability in one scroll&tap or another, but I suspect if push came to shove Ford would make it right.

Pretty sure this thoughtful process on the backend has nothing to do with looking out for us, warranty-wise. Of course Ford doesn’t want to incur additional expense of bricking cars. But I wouldn’t know specifics because the decision was made, and remains, on the backend. Thoughtfully.

 

[SonicBlue]

I’ll be taking my car in soon for the 24B42 CSP update to fix the 1PD faults.

I’m going to ask the service center to update my BC while I’m there. What, exactly, do I need to ask for?

@chesteroberto @avdonr @Blue highway - what are the files available to 2021s that need to be installed via FDRS, and then what config changes need to be made via Forscan?

The ship may refuse to do the Forscan tinkering, but if I at least get the files updated from FDRS, that seems to be the difficult/expensive part.

 

[avdonr]

I’ll be taking my car in soon for the 24B42 CSP update to fix the 1PD faults.

I’m going to ask the service center to update my BC while I’m there. What, exactly, do I need to ask for?

@chesteroberto @avdonr @Blue highway - what are the files available to 2021s that need to be installed via FDRS, and then what config changes need to be made via Forscan?

The ship may refuse to do the Forscan tinkering, but if I at least get the files updated from FDRS, that seems to be the difficult/expensive part.

The dealership will certainly not do any as built edits via FORScan. That is something you would have to do yourself.

As for the modules that need to get updated for BC 1.3:

• IPMA (approx 2-3 hours)
• PSCM (approx 10 min)
• CMR (approx 2-3 hours - only if required/available)

Some 2021s had their CMR updated in the past, if that is the case then you will only need the IPMA and PSCM updated. However, if a CMR update is pending for your vehicle then you will also need to get that updated for BC 1.3.

 

[Blue highway]

I’ll be taking my car in soon for the 24B42 CSP update to fix the 1PD faults.

I’m going to ask the service center to update my BC while I’m there. What, exactly, do I need to ask for?

@chesteroberto @avdonr @Blue highway - what are the files available to 2021s that need to be installed via FDRS, and then what config changes need to be made via Forscan?

The ship may refuse to do the Forscan tinkering, but if I at least get the files updated from FDRS, that seems to be the difficult/expensive part.

I ended up going through all the FDRS updates available and updating everything. Depending on how far along your car is, the updates can take a number of hours. The last push that got BC1.3 working took ~4 hours from memory. The Forscan settings vary depending on which year/model you have. If the dealer updates all the modules, they will have access to the correct Forscan settings. When you have the modules updated, there are people here that can provide the correct settings for your car.

 

[HuntingPudel]

What’s BlueCruise? ??

 

[rugedraw]

@SonicBlue To add to what @avdonr mentioned above, the SCCM must be updated to the latest version, too. I believe that was OTA 6.5.0.

FORScan is 3rd party software that is not officially supported by Ford. Dealers will not use it. That part will fall on you IF you can get them to update the relevant modules.

 

[avdonr]

@SonicBlue To add to what @avdonr mentioned above, the SCCM must be updated to the latest version, too. I believe that was OTA 6.5.0.

FORScan is 3rd party software that is not officially supported by Ford. Dealers will not use it. That part will fall on you IF you can get them to update the relevant modules.

Ah yes, good catch. I was going off what’s in the BC 1.3 OTA but SCCM would also be required if it was not yet updated in the past. Time flies, that SCCM OTA came out a long time ago ?

 

[Dw0413]

I've updated my 21 job 1 with FDRS. Who can help me with the needed FORScan changes? Or is it posted somewhere that I haven't discovered?

 

[rugedraw]

I've updated my 21 job 1 with FDRS. Who can help me with the needed FORScan changes? Or is it posted somewhere that I haven't discovered?

It is not posted publicly. Message me your VIN so I can verify the software levels of the relevant modules.

 

[TruWrecks]

End of August and not a peep from @Ford Motor Company

EA is no longer a thing. That website is gone. My MME is no longer showing as an EA vehicle on the Ford website.

This is Ford's middle finger to the Early Adopters.

 

[azerik]

And so it goes.

I’m a little skeptical that Ford would require you to pay for a bricking caused by OTA out of warranty.

The dealer surely will, until Ford admits fault. As It's going to take a bunch of cars bricking before they lift a finger to help. Which means the first few people that have a bricked car will shovel $ to the dealer to fix because they have no other option or recourse. Heck they don't even have a real solid way to say the OTA bricked it, until Ford says. Remember how many 23's ended up locked out a few weeks ago. That roll out is all over the place and some of us got it well in advance of the locked out posts. How many tow trucks and hours burned on that. How long would it take for those people to get reimbursed for that if out of warranty. (I know those were 23's but fast forward 2 more years and play out that scenario. We only know of those on here, wonder how many were actually affected.)

 

[SonicBlue]

End of August and not a peep from @Ford Motor Company

EA is no longer a thing. That website is gone. My MME is no longer showing as an EA vehicle on the Ford website.

This is Ford's middle finger to the Early Adopters.

Agree that is the end of August and still no love for the 2021s.

This website still appears to be running…

https://www.earlyaccess.ford.com/

 

[JCHLi]

I was thinking this morning and wondered, how is the backend process coming along?

 

[jeffMachE]

Well, "thoughtful backend process" is 24 letters, and at 1 letter a month, we still have to get through "oughtful" before we get to the backend.

This is like waiting for The Winds of Winter. Excitement, anticipation, slowly turning to exasperation and then simple acceptance that things aren't happening.

Sponsored