POST Recall Software HVBJB Failure

[DevSecOps]

Helmets? ? ?

We could probably draw a squiggly line connecting "helmets" to "twinkies" in the UK ... I'll stop there.

Sponsored

 

[ProximusAl]

LOL. My kid does go karting ??. Honest Guv ?

 

[Miteleets]

Not giving me confidence for my trip to Vegas on Sunday!

Mine just malfunctioned last night. Good thing is the parts are avaliable and has been replaced by a new number. At least for the PE.

Still Love the Car!!!!!!

 

[Neil4Real]

So a little update: I convinced the service manager to overnight the part last night, thankfully. He said it still relies on the foreman but he'll do me a favor and get the part there as he at least sees in the service manual where it does say to drop the pack and basically replace the HVBJB after simple checks. The shop foreman, last night, was still saying he has to get the DTC to reappear but will oblige and open a hotline request with Ford corp.

I asked the service manager to order "-C" HVBJB, he said it is showing up but is not available. He was only able to "order -A" but it places the order for "-B" since it has been superseded. I'll trust the people here who said you cannot get -A and that -B is really going to arrive.

This morning I get a text from the foreman that he hasn't heard back from Ford and is going to take the car to try and get it to fail again... yay... I hear back from him shortly after saying that he got a response from the hotline saying a bunch of bullshit that if the car was fine BEFORE I updated the modules and he was able to clear the DTCs and nothing returned, then the car is fine. I then called him and didn't even really try as he is so set on "Ford is telling me to do this" blah, blah and now, I can't really fault him, I mean, Ford did say don't do anything if the BECM DTC does not return after being cleared. They essentially are saying I did the module updates wrong and to re-program them and I'll be set.

Well, the dealer still hasn't heard from Ford corp. even though I keep being assured they'll reach out and set this straight. I would have to say, as much as it is nice to have some Ford guys on here, it clearly has quite the lag, so hopefully they get this sorted. I don't understand how the system is setup, but I wish Ford could have just put notes on my VIN since I provided that right away, seems odd there is even the possibility of miscommunication.

Thankfully, or not?, the foreman drove the 73 like a bat out of hell, I guess, and managed to trip the DTC AGAIN! Holy cow. It defaulted to exactly the same as what happened to me, according to him, he said the same messages popped up (the same messages also popped up in FordPass) and he can see the power is severely limited. He called me while in the car right after it happened.

I think this is the first confirmed back to back failure with the new recall software, so clearly all those that got their DTCs cleared and back on their way will just get the DTC again even easier. Keep in mind I had this software since last week and have been doing the commute for a few days with it, same driving style, without an event. Then I had an event and another was immediately triggered again.

 

[Neil4Real]

I'm at work and took a little too long drafting the above it seems, I've now had confirmation that Ford corp has finally been able to connect with the dealer and they're working on it properly, with the expectation that the service will be completed by Monday evening.

Hopefully this is just a learning experience and everyone, including the people who handle the Ford hotline, get up to date with how to handle these cases!

 

[Mach-Lee]

1. Codes should be logged OTA so the dealer/engineers should be able to see the P0ADA/P0ADE code happened previously even if someone cleared then out.
2. Driving the car hard (WOT) will probably re-trigger the code.
3. If the dealer clears the codes without a repair and returns the car, perform #2 and bring it right back.
4. You should open a case with Ford right away if you haven’t yet.
5. Emphasize the code should be looked up in the workshop manual (search) and the pinpoint test instructions should be followed (which direct replacement).

 

[DevSecOps]

1. Codes should be logged OTA so the dealer/engineers should be able to see the P0ADA/P0ADE code happened previously even if someone cleared then out.
2. Driving the car hard (WOT) will probably re-trigger the code.
3. If the dealer clears the codes without a repair and returns the car, perform #2 and bring it right back.
4. You should open a case with Ford right away if you haven’t yet.
5. Emphasize the code should be looked up in the workshop manual (search) and the pinpoint test instructions should be followed (which direct replacement).

They are taking care of him now. There's people overseeing it. Originally there was just a lot of failures between the dealer and Ford. I think that's something they are working on making sure doesn't happen anymore.

 

[ProximusAl]

I must admit, I don’t have a GT, BUT do have an AWD standard (no idea what that is in America speak)…Small battery but AWD. I’ve been driving her gently because here in the UK, even armed with all the SSM/TSB for this, my local dealer has sold probably 5 MMEs, and the idea of a pack drop is likely to be the very last thing they’d ever do. I asked them how many windscreen recalls they’ve had done, and they said 3. ?

 

[ARK]

So a little update: I convinced the service manager to overnight the part last night, thankfully. He said it still relies on the foreman but he'll do me a favor and get the part there as he at least sees in the service manual where it does say to drop the pack and basically replace the HVBJB after simple checks. The shop foreman, last night, was still saying he has to get the DTC to reappear but will oblige and open a hotline request with Ford corp.

I asked the service manager to order "-C" HVBJB, he said it is showing up but is not available. He was only able to "order -A" but it places the order for "-B" since it has been superseded. I'll trust the people here who said you cannot get -A and that -B is really going to arrive.

This morning I get a text from the foreman that he hasn't heard back from Ford and is going to take the car to try and get it to fail again... yay... I hear back from him shortly after saying that he got a response from the hotline saying a bunch of bullshit that if the car was fine BEFORE I updated the modules and he was able to clear the DTCs and nothing returned, then the car is fine. I then called him and didn't even really try as he is so set on "Ford is telling me to do this" blah, blah and now, I can't really fault him, I mean, Ford did say don't do anything if the BECM DTC does not return after being cleared. They essentially are saying I did the module updates wrong and to re-program them and I'll be set.

Well, the dealer still hasn't heard from Ford corp. even though I keep being assured they'll reach out and set this straight. I would have to say, as much as it is nice to have some Ford guys on here, it clearly has quite the lag, so hopefully they get this sorted. I don't understand how the system is setup, but I wish Ford could have just put notes on my VIN since I provided that right away, seems odd there is even the possibility of miscommunication.

Thankfully, or not?, the foreman drove the 73 like a bat out of hell, I guess, and managed to trip the DTC AGAIN! Holy cow. It defaulted to exactly the same as what happened to me, according to him, he said the same messages popped up (the same messages also popped up in FordPass) and he can see the power is severely limited. He called me while in the car right after it happened.

I think this is the first confirmed back to back failure with the new recall software, so clearly all those that got their DTCs cleared and back on their way will just get the DTC again even easier. Keep in mind I had this software since last week and have been doing the commute for a few days with it, same driving style, without an event. Then I had an event and another was immediately triggered again.

Glad to hear they are replacing it after all. It seems then this is some additional confirmation that the software update does cause Service Vehicle Soon to trigger more easily then Stop Safely Now?

Because pre-software update, I don't think people who got a HVBJB replaced could count on getting Stop Safely Now with their HVBJB welding just by driving it hard a single time?

 

[Neil4Real]

Glad to hear they are replacing it after all. It seems then this is some additional confirmation that the software update does cause Service Vehicle Soon to trigger more easily then Stop Safely Now?

Because pre-software update, I don't think people who got a HVBJB replaced could count on getting Stop Safely Now with their HVBJB welding just by driving it hard a single time?

I would assume so, as pre-update your contactors would already be toast and you couldn't do anything. Whether the software is premature, which it seems to be a bit since my car was able to get the DTC twice, so it had 2 events the software determined were about to fry the component and it still was drivable. I'd have figured the second time the dealer would have gotten the stop safely now message rather than another service vehicle soon and it still be operable.

 

[Neil4Real]

We are getting there, my dealer has received the HVBJB today, thank goodness the manager put it in last night, we are both shocked it came today since he put in the order after 5pm yesterday, but yay!

They hope to be done today, but it might bleed into tomorrow/early Monday.

He is doing the weather stripping TSB for me as well and adjusting my driver passenger door that has a gnarly misalignment and I'm hoping is the main reason for my wind noise on that side as my Premium was loads quieter. The weather strip was ordered yesterday but won't come until Monday, so I'm hoping they get everything done by Monday end of business so I can pick it up, but will plan on Tuesday in my head so I'm not disappointed.

Pretty quick turnaround if they stay on it and don't break anything. I am fortunate for all the help given and the connect I had at the dealer, I hope others in this situation get a much improved experience and don't have to fight so hard for proper resolution of the problem.

 

[DevSecOps]

I would assume so, as pre-update your contactors would already be toast and you couldn't do anything. Whether the software is premature, which it seems to be a bit since my car was able to get the DTC twice, so it had 2 events the software determined were about to fry the component and it still was drivable. I'd have figured the second time the dealer would have gotten the stop safely now message rather than another service vehicle soon and it still be operable.

Next month I'll have the Neil/Scoop combo test. Sacramento to Newport with plenty of driving on 73 and also Tejón Pass.

I could take the Audi, but I'm okay with a little extra excitement in life.

 

[Neil4Real]

Next month I'll have the Neil/Scoop combo test. Sacramento to Newport with plenty of driving on 73 and also Tejón Pass.

I could take the Audi, but I'm okay with a little extra excitement in life.

Live on the wild side, Todd! Do the update and then you'll ensure you just get the beefier part out of the gate. Just call a dealer somewhere around one of the spots and have them be ready with your HVBJB, express service!

 

[emersonsdad]

Not giving me confidence for my trip to Vegas on Sunday!

I just did Bakersfield to Vegas to Pismo and then back to Bako this past week for vacation. DCFC five times without issues. No issues but it was in the back of my mind until I got home.

 

[DevSecOps]

Live on the wild side, Todd! Do the update and then you'll ensure you just get the beefier part out of the gate. Just call a dealer somewhere around one of the spots and have them be ready with your HVBJB, express service!

Knowing my luck, I probably wouldn't be able to get the service you and Scoop got.

Sponsored