Cutoff date for software update

[buffasnow]

I want to be concise and non-whiny here, but this has been bugging me since I saw the 21B02 Program announcement. Perhaps someone with actual knowledge can help me understand without divulging anything they should not.

1. Ford seems to know that vehicles built before a certain date should get a software update to address these battery issues. Apparently it took some research and testing to determine the fix for some forum members. All good.
2. If they know that the fix/patch should be applied to cars built through 1/09, does that mean that Ford started doing something different in Mexico on 1/10?
2a. If so, and that was a software change, would it be reasonable to think that the issues with pre-1/10 builds might have been foreseeable and perhaps addressed before/at delivery?
2b. If so, and the change was hardware, would it be reasonable to believe that post-1/09 builds will not have this same issue?
2c. if neither hardware nor software changed on 1/10, I'm confused about how the 1/09 date was chosen. If there was a possibility in Ford's mind that MMEs built on/after 1/10 might need the software update, why not have the 21B02 program cover all new cars as they are delivered, with no end date?

I guess this may or may not be the issue addressed at Speedway. I really don't even need to know, that stuff will probably come out at some point in the future. I would really like to have a level of confidence that this particular issue is behind us once all these cars are updated, but I also realize that I can't always have what I want. Maybe it's too much to ask, or maybe I am missing something.

I am definitely buying my FE when it arrives in a few weeks, and I have no interest in bashing Ford or anyone else.

Sponsored

 

[Maric]

@ChasingCoral posted the Ford bulletin that specified the cars affected (by build date). Check out his post history.

 

[buffasnow]

@ChasingCoral posted the Ford bulletin that specified the cars affected (by build date). Check out his post history.

Yes, thanks, I saw that bulletin. Trying to understand why 1/09 was chosen as the end date.

 

[Kamuelaflyer]

Far too many ifs in that post. Far too much information is missing to be making assumptions.

The QA stop ship in KC was, though, almost assuredly for something different.

 

[Maric]

Yes, thanks, I saw that bulletin. Trying to understand why 1/09 was chosen as the end date.

Ahh gotcha. I assumed the cars in Coral’s grouping left MX. and then a new software build was released that all cars after just received as part of the process. Totally a guess. No idea.

 

[methorian]

I don't have a lot to add, other than my Mach-E, who went into production in December, but wasn't listed as "complete" until Jan 5th has had no battery issues. No "Speedway QC" and no updates from the dealer before I took delivery. I have evidence that it's doing what it's supposed to do as far as keeping the LVB topped up.

 

[JellyBelly]

Yes, thanks, I saw that bulletin. Trying to understand why 1/09 was chosen as the end date.

we will never know - we have to trust Ford knows what to do more than us.

 

[RonTCat]

I want to be concise and non-whiny here, but this has been bugging me since I saw the 21B02 Program announcement. Perhaps someone with actual knowledge can help me understand without divulging anything they should not.

1. Ford seems to know that vehicles built before a certain date should get a software update to address these battery issues. Apparently it took some research and testing to determine the fix for some forum members. All good.
2. If they know that the fix/patch should be applied to cars built through 1/09, does that mean that Ford started doing something different in Mexico on 1/10?
2a. If so, and that was a software change, would it be reasonable to think that the issues with pre-1/10 builds might have been foreseeable and perhaps addressed before/at delivery?
2b. If so, and the change was hardware, would it be reasonable to believe that post-1/09 builds will not have this same issue?
2c. if neither hardware nor software changed on 1/10, I'm confused about how the 1/09 date was chosen. If there was a possibility in Ford's mind that MMEs built on/after 1/10 might need the software update, why not have the 21B02 program cover all new cars as they are delivered, with no end date?

I guess this may or may not be the issue addressed at Speedway. I really don't even need to know, that stuff will probably come out at some point in the future. I would really like to have a level of confidence that this particular issue is behind us once all these cars are updated, but I also realize that I can't always have what I want. Maybe it's too much to ask, or maybe I am missing something.

I am definitely buying my FE when it arrives in a few weeks, and I have no interest in bashing Ford or anyone else.

1. "Seems to know" is a good description. If Ford knew what the root cause of the issue was, cars would be flashed and Mark would have his car back in a few hours. In reality, it is likely they are looking at which vehicles are "phoning home" with problems, and put some bookend dates around it.
2. Maybe. Continuous updates are common, but sometimes the update to side mirror adjustment software inadvertently breaks something else. Sometimes suppliers need to change sub-suppliers.

Why doesn't Ford just test every software update before release? It does, but there are well north of 100 million lines of code to test (which is far, far more complex than any phone ever made, for example). There are only a few hundred vehicles to validate software on, and automated software tests are only so useful when the input is more complicated than a touchscreen. To go down every code path every time might take years, and I doubt many owners want to wait a year to get an update to the driver display to show kW consumed. So critical code paths are tested, and sometimes bugs hide elsewhere.

 

[benk016]

Its interesting that I have a build date that falls in the TSB, but I haven't had the issue. I Wonder if mine got updated at some point before delivery?

 

[ChasingCoral]

2. Maybe. Continuous updates are common, but sometimes the update to side mirror adjustment software inadvertently breaks something else. Sometimes suppliers need to change sub-suppliers.

And sometimes suppliers make a change in their sub-suppliers or code without telling the automaker and it doesn't end up working out so well.

Why doesn't Ford just test every software update before release? It does, but there are well north of 100 million lines of code to test (which is far, far more complex than any phone ever made, for example). There are only a few hundred vehicles to validate software on, and automated software tests are only so useful when the input is more complicated than a touchscreen. To go down every code path every time might take years, and I doubt many owners want to wait a year to get an update to the driver display to show kW consumed. So critical code paths are tested, and sometimes bugs hide elsewhere.

Especially when a bug causes a LVB to drain or a car to not go into drive. At that point, new code is needed fast!

 

[ChasingCoral]

Its interesting that I have a build date that falls in the TSB, but I haven't had the issue. I Wonder if mine got updated at some point before delivery?

Entirely possible.

 

[GoGoGadgetMachE]

To go down every code path every time might take years, and I doubt many owners want to wait a year to get an update to the driver display to show kW consumed. So critical code paths are tested, and sometimes bugs hide elsewhere.

just write a few more unit tests. some of my development colleagues are convinced that this solves all bugs forever!

(yes those people are wrong and dangerous)

 

[caca_on]

I want to be concise and non-whiny here, but this has been bugging me since I saw the 21B02 Program announcement. Perhaps someone with actual knowledge can help me understand without divulging anything they should not.

1. Ford seems to know that vehicles built before a certain date should get a software update to address these battery issues. Apparently it took some research and testing to determine the fix for some forum members. All good.
2. If they know that the fix/patch should be applied to cars built through 1/09, does that mean that Ford started doing something different in Mexico on 1/10?
2a. If so, and that was a software change, would it be reasonable to think that the issues with pre-1/10 builds might have been foreseeable and perhaps addressed before/at delivery?
2b. If so, and the change was hardware, would it be reasonable to believe that post-1/09 builds will not have this same issue?
2c. if neither hardware nor software changed on 1/10, I'm confused about how the 1/09 date was chosen. If there was a possibility in Ford's mind that MMEs built on/after 1/10 might need the software update, why not have the 21B02 program cover all new cars as they are delivered, with no end date?

I guess this may or may not be the issue addressed at Speedway. I really don't even need to know, that stuff will probably come out at some point in the future. I would really like to have a level of confidence that this particular issue is behind us once all these cars are updated, but I also realize that I can't always have what I want. Maybe it's too much to ask, or maybe I am missing something.

I am definitely buying my FE when it arrives in a few weeks, and I have no interest in bashing Ford or anyone else.

@ChasingCoral posted the Ford bulletin that specified the cars affected (by build date). Check out his post history.

How can I check my build date? Is there hidden on some menu?

I got delivery of my FE two weeks ago and so far no issues at all.. Cheers!

 

[agoldman]

How can I check my build date? Is there hidden on some menu?

I got delivery of my FE two weeks ago and so far no issues at all.. Cheers!

just put your vin number in the tracker link on this forum.

 

[caca_on]

just put your vin number in the tracker link on this forum.

Did not work with my vin, but thanks anyways!

Sponsored