Way too DANGEROUS!

[Ravensfan1996]

Hmm I have ‘21 Premium and have been holding off having the HVJB replaced. At the beginning it was just about my dealer not having the parts, now I’ve just been waiting for a good time to do it. Now I’m thinking i should wait to do it. I dont want the 1P gremlin added in the software updates that they do. It seems like maybe since they have done hundreds or no thousands and just a few have it, maybe it’s not a widespread issue. How long do we have to do the recall?

Sponsored

 

[Pedro Diaz]

Imagine driving down the road. You pull off the accelerator on your Mach E to slow down and eventually brake. It works. As you creep closer to the stopped car in front of you, your mach e continues to slow until OUT OF NOWHERE your one-pedal regen braking fails and your mach e -- at a time when it should be stopping -- lurches foward, throwing you into whatever is in front of you! It's scary. And Ford NEEDS to fix this known issue immediately.

After I got the HVBJB recall last month, my mach e would randomly lose the ability to slow and brake using one-pedal regen. It's a terrifying experience thinking you are about to slow but suddenly you're going faster. luckily, it hasn't resulted in an accident like the one described above. But I dont feel safe having my family drive a car that doesn't stop the way it's supposed to. I took my vehicle into the dealer three times. After updating every available module, they escalated the matter to Ford national techs. As communicated to me by my dealer, ford is aware that the HVBJB recall causes one-pedal drive faults and they do not have a solution. Yet they are posting here about available goodwill "gifts" for those who go get the recall within a certain time. Is Ford encouraging Mach e owners to get the HVBJB recall knowing that it will result in an unsafe car with a whole other problem?

I had zero issues with this vehicle before this recall. I guess the honeymoon period is over. What can I do? The dealership said there is literally nothing they can do and Ford acknowledges this. @Ford Motor Company I just want this car to work as it should and did before the recall.

This happen to mine '22 CR-1. My wife had been complaining of this happening at random times. But during a trip to Florida, and I had more time to drive it, I experience a front sensor alarm popping up often. Specially when breaking.

Then I loaned the car to my in-laws who had a fender-bender with the car in front of them. They alleged the car accelerated after a full stop and without warning the car accelerated hitting the car in front. Insurance paid for all of it as FORD didn't want to give up.

Do you know that aside from the plastic, frunk inners, hood and paint, they replaced all the bumper sensors and the problem never showed up again. I bet these sensors help the car estimate the space between cars and the slight glitch will reset to normal operation.

 

[avdonr]

I’ve read over this thread and thought I should share some insight. Like @Mike G mentioned earlier, this is a powertrain software issue.

About a month ago, Ford released updated powertrain software for what appears to be every model year. These modules include the PCM, BECM, SOBDM, and SOBDMC and they must all be updated one after another in a set (FDRS forces this actually).

When you go in for a HVJB recall/replacement, the powertrain software must be updated/re-initialized. This is why everyone who’s had a HVJB replaced recently is facing this issue and those that had it replaced months ago are not. Technically when any module is replaced, this same software update/re-initialization happens.

The only thing those that had their HVJB replaced/software updated already can do is wait for Ford to release new software. You could technically manually downgrade the firmware for all modules with FORScan but that is certainly not a procedure I would endorse or recommend for system critical or coordinated modules.

I do not know why Ford has not pulled these new powertrain updates from FDRS yet, only they can answer that question.

 

[Ravensfan1996]

I’ve read over this thread and thought I should share some insight. Like @Mike G mentioned earlier, this is a powertrain software issue.

About a month ago, Ford released updated powertrain software for what appears to be every model year. These modules include the PCM, BECM, SOBDM, and SOBDMC and they must all be updated one after another in a set (FDRS forces this actually).

When you go in for a HVJB recall/replacement, the powertrain software must be updated/re-initialized. This is why everyone who’s had a HVJB replaced recently is facing this issue and those that had it replaced months ago are not. Technically when any module is replaced, this same software update/re-initialization happens.

The only thing those that had their HVJB replaced/software updated already can do is wait for Ford to release new software. You could technically manually downgrade the firmware for all modules with FORScan but that is certainly not a procedure I would endorse or recommend for system critical or coordinated modules.

I do not know why Ford has not pulled these new powertrain updates from FDRS yet, only they can answer that question.

I wondered why its just now being reported when the recalls have been going on for awhile and just recently ive seen these posts. Are those module updates powerups? or only updated at dealer when they do the software part of the recall? I have had mine done yet. but think ill wait. I like my 1P drive

 

[avdonr]

I wondered why its just now being reported when the recalls have been going on for awhile and just recently ive seen these posts. Are those module updates powerups? or only updated at dealer when they do the software part of the recall? I have had mine done yet. but think ill wait. I like my 1P drive

It has not yet gone out via OTA as a power up which is likely why it’s not *super* widespread at this point.

Only those that have gone in for HVJB or other powertrain related repairs have had it applied.

Yeah, I would wait to do any HVJB recall if yours hasn’t actually failed yet. At least until they fix this software. I normally update my car via FDRS as soon as new software drops there, but I’m glad I waited on this one.

 

[YunniorO]

Hmm I have ‘21 Premium and have been holding off having the HVJB replaced. At the beginning it was just about my dealer not having the parts, now I’ve just been waiting for a good time to do it. Now I’m thinking i should wait to do it. I dont want the 1P gremlin added in the software updates that they do. It seems like maybe since they have done hundreds or no thousands and just a few have it, maybe it’s not a widespread issue. How long do we have to do the recall?

I have a 21 premium AWD extended range and have the most recent part and have not experienced any issues with one pedal.

 

[Mike G]

Powertrain updates seem to come out 5-6 times a year. So the latest iteration is the version that's causing 1PD faults and un-commanded drive mode switching. So people who had the HVJB done before this latest release of powertrain updates won't see these issues. It's mostly just folks who went in for the HVJB or the stuck powercord fix within say the last month that got the latest updates (and those of us who rabidly update our cars as soon as something new comes along ?‍). It's not the worst update I've done...and I don't use 1PD anyway. And frankly there for a while (over the last two years) I'd kinda gotten used to my car dropping out of Unbridle every now and then. Just to keep me on my toes...sort of like Cato sneaking up on the Pink Panther to make sure he stays in shape and is always looking out for trouble. It's a symbiotic relationship.

 

[NewGuy]

Great. Glad I finally have my recall scheduled for next week.

 

[Duncs]

Great. Glad I finally have my recall scheduled for next week.

In fairness, some people have said they don't have this problem post recall. So it's not guaranteed. But as you can see from the responses, it's a real possibility. Good luck.

 

[Duncs]

I had it once that it decelerated close to a stop, taking the foot from the pedal expecting OPD to do the rest, but the car made a "jump" forward instead.

This was while approaching a pedestrian crossing with people approaching it. A bit frightening indeed.

I was not able to reproduce this a 2nd time since then.

Yeah that's really scary. Should not be happening.

 

[LF-X]

At least the issue seems to be something other are experiencing too.

Only thing to mention: In contrast to the OP, I have a SR RWD - So no recall for the HVBJB on my car. Yet it did pretty much what was written in the first post.

So I would rule that out of the investigations. Might be more related to the time some OTAs (or manual module updates during the recall) were deployed.

 

[Silver Surfer]

Just got my vehicle back from the dealer two days ago for a new 12v and parking brake issues.They also applied some updates, yesterday and today I've had the 1pd fault and I didn't get the hvbjb because my car is standard range.

 

[kdonnel]

I do not know why Ford has not pulled these new powertrain updates from FDRS yet, only they can answer that question.

I have two theories.

1. Someone high up at Ford thrives on drama. Leaving the updates in FDRS creates more drama in their job and makes them happy.

2. There is so much bureaucracy in Ford that someone down really low in the organization is screaming to have the updates pulled but it has not filtered up through the 987 levels of management.

 

[Mirak]

My charge port was fixed at the same time as the HVBJB recall so this is definitely possible.

Same for me. I suspect that most people who are getting the HVBJB recall work done are getting the charge port software recall at the same time (why Ford never pushed this OTA is weird - oh wait… Ford sucks at OTA).

I haven’t experienced the fault, but it’s definitely related to one or both things above, or maybe a combination of both.

 

[Ravensfan1996]

I have a 21 premium AWD extended range and have the most recent part and have not experienced any issues with one pedal.

But when did you have it done? its not the part its the current software update done at the time that seems to be causing it.

Sponsored