Several Mach-E Service Actions [Resumed] - Powertrain Software Issue

[leehinde]

How do I check?

There's a sticker inside the front door. (not the tire pressure sticker.)
Mine says it was built 12/22.

Sponsored

 

[phil]

My only issue would be there is a certain group of owners who have not received OTA’s since last August. If an OTA is the fix then we won’t receive it.

I briefly worried about that. But I think Ford really does not want to do that because it would severely interfere with the service actions they want to implement. Lots of HVBJB warranty replacements would have to wait till (optional) OTA software was brought up to date, either by owners or by dealers, who don't have time for that.

This will need to be something that is readily taken care of by dealers. Probably.

 

[BigMach-E]

Jesus Christ, Ford can’t get software right, 4 years later.

 

[MME72BB]

 

[GatorGrowl]

Ford is completely lost when it comes to software. And, from the adapter, hardware too.

To be fair, the adapters are made by Tesla.

 

[Timelessblur]

Well shit. I just dropped my car off and part of it was for the HVBJB work alone with everything else.

 

[AKgrampy]

I briefly worried about that. But I think Ford really does not want to do that because it would severely interfere with the service actions they want to implement. Lots of HVBJB warranty replacements would have to wait till (optional) OTA software was brought up to date, either by owners or by dealers, who don't have time for that.

This will need to be something that is readily taken care of by dealers. Probably.

My car is fine though. Think I am more bummed that I most likely have to look for something other than a Ford as my next EV. I know some have had issues but my Mach has worked great since day one.

 

[phil]

My car is fine though. Think I am more bummed that I most likely have to look for something other than a Ford as my next EV. I know some have had issues but my Mach has worked great since day one.

Mine has been great also. A few minor issues, nothing major. I figure I'll just keep the Ford, until something much better comes along.

 

[AKgrampy]

Mine has been great also. A few minor issues, nothing major. I figure I'll just keep the Ford, until something much better comes along.

My only issue is our local dealer opted out and nearest dealer is 300 miles away.

 

[Timelessblur]

wow, thanks for posting.... !

makes me glad I disabled OTAs months ago once I had a stable build and known functionality after my HVBJB replacement.

@Ford Motor Company is going to have to make some real improvements to software testing and release process to get me to turn updates back on. The ONLY update I would like is Navigation data, and I refuse to pay $80 for that, so.... Unless Ford enables a user display of custom dashboard info on the main console, I don't see myself updating any modules, ever.

I am hoping that maybe this time around, after Ford gets all modules talking to each other again, that they capture and number ALL modules versions with a 'major' release, and version numbers in a package so that the entire system could be reset and reloaded at some known version after testing. Until there is a way to skip all the intermediate alpha/beta releases, and jump right to a fully tested major release with documented fixed/enhancements.... I'll stick with the software I have.

I will say as a software developer with over 10 years experience doing testing is honestly hard and setting it up right is very hard. Plus diminishing returns on automation and regression testing kick in fast.

I can see them getting better but right now the gains are going to be slow and expensive. I say all this as I believe it is very important and am dealing with some of these issue on what I am working on.
It is a very slow and difficult process and one sees little gains. The hardest part is getting engineering leadership and leads who both understand how to do it, understand how the project works and understand what pitfalls there are to make sure they are not put in. They need the time and oversight to review the code and force the culture. It is like 3/4 of my time having to just review code and push back against more junior devs who don’t fully see the picture of why the unit testing and seeing edge cases. It is a skill that is very rare.
This made even harder for something like the Mach E because of the physical hardware requirements and making sure it is all setup right. I am saying it is hard and it appears they are learning. It is new edge cases to get put in to the unit test. It is why they do slower roll outs and are prepared to stop things.

 

[RMoore]

I just love how my timing flips from good to bad to good again. My car was built days before the switch to the better HVBJB at the factory. I was able to take delivery before the "stop sell" when they instituted the software fix. I finally got around to taking it in for the new HVBJB and 40K checkup last Wednesday.

My timing is very similar to yours and I have an appointment for my HVBJB replacement next week. Guess that won’t happen…

 

[VindictivePantz]

What a cluster.

They stopped that one too. The one that moves the speedometer location ?

 

[azerik]

Jesus Christ, Ford can’t get software right, 4 years later.

Oh they got it right. I guess the last objective was to piss everyone off so they wouldn't try to buy another Ford EV ever. I think that was supposed to be BC1.3. But you know software.. better to push out some packages and break a lot of things than wait until the release and break it all.

How can this be this unstable. Death by 1000 bandaids.

 

[Mr. Toejam]

Just had my HVBJB recall performed 3 weeks ago. 1 time, I turned on my car and it still had my profile loaded but instead of Engaged, I was in Whisper and 1PD was switched off. But it used to do this before because that was how my guest/PAAK profile was set. So I saved that profile as Engaged/1PD and have not had an issue since.

 

[dtbaker61]

I will say as a software developer with over 10 years experience doing testing is honestly hard and setting it up right is very hard. Plus diminishing returns on automation and regression testing kick in fast.

I can see them getting better but right now the gains are going to be slow and expensive. I say all this as I believe it is very important and am dealing with some of these issue on what I am working on.
It is a very slow and difficult process and one sees little gains. The hardest part is getting engineering leadership and leads who both understand how to do it, understand how the project works and understand what pitfalls there are to make sure they are not put in. They need the time and oversight to review the code and force the culture. It is like 3/4 of my time having to just review code and push back against more junior devs who don’t fully see the picture of why the unit testing and seeing edge cases. It is a skill that is very rare.
This made even harder for something like the Mach E because of the physical hardware requirements and making sure it is all setup right. I am saying it is hard and it appears they are learning. It is new edge cases to get put in to the unit test. It is why they do slower roll outs and are prepared to stop things.

I know it' hard to do right....

I was in software development, then management for 15 years... 80 developers writing/maintaining 8 million lines of code in three computer languages (fortran, c, C++) on 4 hardware platforms, each with their own OS.

It is a difficult balance to develop new functionality, fix bugs, and test for regressions all at the same time.

@Ford Motor Company has a LONG way to go before I will trust them to manage the OTA process and version management.

Sponsored