HVBJB advice/questions

[TheQ42]

So, I got the error shown below:

The power was reduced, and these were thrown when I was going fairly fast on the highway (was passing someone). So, I took it to the dealership, and here's what happened:

1. They noticed that, while I had the initial recall installed to prevent the car from bricking itself when an issue with the HVBJB was detected, I didn't have the one following that software update.
2. The dealership installed the new software update related to the recall, and the codes cleared. They told me that part of the reason for the latest update was because false codes could be thrown with the previous version of the software.
3. I was skeptical, but took the car back . . . when driving it this morning, I swear I smelled burning electronics for a minute or so after getting off the highway, but no codes were thrown, and the car is behaving normally.

So, my question is this: is the dealer explanation possible? I know there are techs on here more familiar with this than I am . . . or, was there an actual fault detected in my HVBJB and updating the software (and rebooting the system a bunch of times) just cleared the codes and I can expect them to come back the next time I am on the highway in rush hour going 80 with the flow of traffic?

I'm just wondering if I should push Ford harder to replace the HVBJB or just drive it and not worry about it until/unless the codes are thrown again? My main concern is that I don't want to get the SSN error on the highway, during winter, with my kids in the back seat :-(

I did read the summary post on the megathread (thank you so much @DevSecOps ) and man, I just want to say that this community is awesome.

Sponsored

 

[Mach-Lee]

Nope, they did it wrong. If you set the P0ADA/P0ADE code you need a new HVBJB, not a software update. Says TSB 22-2178. Unfortunately you will get SVS and the power limit again so you will be back at the dealer for a HVBJB replacement. Clearing codes is not the fix here, unfortunately many dealers peddle that lie in hopes that they can avoid working on it.

 

[Ford Motor Company]

So, I got the error shown below:

The power was reduced, and these were thrown when I was going fairly fast on the highway (was passing someone). So, I took it to the dealership, and here's what happened:

1. They noticed that, while I had the initial recall installed to prevent the car from bricking itself when an issue with the HVBJB was detected, I didn't have the one following that software update.
2. The dealership installed the new software update related to the recall, and the codes cleared. They told me that part of the reason for the latest update was because false codes could be thrown with the previous version of the software.
3. I was skeptical, but took the car back . . . when driving it this morning, I swear I smelled burning electronics for a minute or so after getting off the highway, but no codes were thrown, and the car is behaving normally.

So, my question is this: is the dealer explanation possible? I know there are techs on here more familiar with this than I am . . . or, was there an actual fault detected in my HVBJB and updating the software (and rebooting the system a bunch of times) just cleared the codes and I can expect them to come back the next time I am on the highway in rush hour going 80 with the flow of traffic?

I'm just wondering if I should push Ford harder to replace the HVBJB or just drive it and not worry about it until/unless the codes are thrown again? My main concern is that I don't want to get the SSN error on the highway, during winter, with my kids in the back seat :-(

I did read the summary post on the megathread (thank you so much @DevSecOps ) and man, I just want to say that this community is awesome.

Hey there! If you send over a DM with your VIN and Ford dealer info, I can look into your concerns on my end.

 

[TheQ42]

Hey there! If you send over a DM with your VIN and Ford dealer info, I can look into your concerns on my end.

Sent.

@Mach-Lee that was my concern . . . their argument is that the previous version of the software on my car threw the code in error, and they can't do anything with the car to repair it unless it throws codes again now that I've had my recall software update. That seems . . . weird to me? But I also work in software development, so it's not completely impossible that the codes could be thrown by a glitch?

Even if that's the case, I don't understand why the HVBJB shouldn't just be replaced to be safe? What if it WASN'T an error? Why the hell would Ford risk that? I'd go from "mild inconvenience that I can shrug off" to "absolutely furious, and looking for compensation for my time on top of the repair."

I don't think replacing the part is unreasonable, known bug or not.

Ugh. After reading the actual bulletin (thank you for posting that), it seems they definitely screwed up. It doesn't say "flash the software and hope it goes away." It clearly says if I throw a P-code to replace the HVJBJ. And now I'm more irritated :-(

 

[Mach-Lee]

Ugh. After reading the actual bulletin (thank you for posting that), it seems they definitely screwed up. It doesn't say "flash the software and hope it goes away." It clearly says if I throw a P-code to replace the HVJBJ. And now I'm more irritated :-(

Yup, you got it. If you want to trigger it again you probably just need to perform a few passing maneuvers again. I guess you can plan a week or two period when you want to be be without the car for repairs. And you might see the dealer repair turnaround map on here to find a better dealer.

 

[TheQ42]

This is just a stupid way to address the problem. They should be erring on the side of "replace it so I don't piss off the customer."

 

[scoopman]

you shouldn't need to trigger it again -- when they plugged your car into FDRS there should now be a record on Ford's servers of the DTC. Have someone here look up your car and confirm they can see the DTC. Take a screen shot of that and the TSB mentioned earlier here to your dealer and tell them they are full of $%^#$% and they need to order a new HVBJB for you asap before your contactors fry and you are stranded.

 

[Mach-Lee]

you shouldn't need to trigger it again -- when they plugged your car into FDRS there should now be a record on Ford's servers of the DTC. Have someone here look up your car and confirm they can see the DTC. Take a screen shot of that and the TSB mentioned earlier here to your dealer and tell them they are full of $%^#$% and they need to order a new HVBJB for you asap before your contactors fry and you are stranded.

It has to be scannable in order to approve the ticket for the part order FYI. They have to submit a code report from inside FDRS. I wish they could do it from code history but Ford’s not set up that way.

 

[TheQ42]

It has to be scannable in order to approve the ticket for the part order FYI. They have to submit a code report from inside FDRS. I wish they could do it from code history but Ford’s not set up that way.

But in this case, the dealership definitely screwed up--they had the codes, scannable before they reset them with the software update. I'm hoping that I can use that to negotiate with Ford to get them to replace the module without me having to risk getting stranded.

 

[scoopman]

It has to be scannable in order to approve the ticket for the part order FYI. They have to submit a code report from inside FDRS. I wish they could do it from code history but Ford’s not set up that way.

Sounds like someone needs to shred their car in the mountains listening to Blippi this weekend!

 

[Rob S]

i really hope the ford contact who responded earlier can do something for you. the more i read these issues, the more disappointed in Ford I get. Our family has purchased 9 Fords so far, and rely on our cars to be trouble-free and supported by the Manufacturer AND the dealer.

 

[TheQ42]

i really hope the ford contact who responded earlier can do something for you. the more i read these issues, the more disappointed in Ford I get. Our family has purchased 9 Fords so far, and rely on our cars to be trouble-free and supported by the Manufacturer AND the dealer.

I'll definitely update the thread when I hear back . . . so far, they've just collected my information.

 

[TheQ42]

Just to update the thread, the Ford rep that I PMed here on the forums has opened a case with the "BEV Team." I'm now waiting "a few business days" for the BEV team to contact me.

I definitely wish it were a bit easier to get directly in contact with the BEV team (they need a dedicated number that we can call), but I feel reasonably confident that a case was actually opened.

If I don't hear back by EOB Wednesday, I'll start making some noise to see if I can escalate things. Should be an easy case to review since all of the records are accessible by Ford. The chain of events is:

1. Car threw codes typical of HVBJB problems
2. I took it to the dealer who didn't follow the instructions in the SB
3. One software update later (not fixing the problem) I'm driving around waiting for the codes to be thrown again risking a tow.

Logically, doesn't seem like a hard problem for Ford to solve for me. I appreciate the rep finding the thread here and jumping on it so quickly though!

 

[TheQ42]

Next update!

I got a dealer satisfaction survey in my email which I filled out honestly. My ratings were low, but I tried to be very specific in my feedback (highlighting the instructions in the TSB and the general lack of EV knowledge by the guy that checked me in).

The next day I got a call back from the service manager who has ordered the part. I'm going to chat with him today to make sure everything is covered under warranty and I can get my rental or loaner car, and I should be good to go.

 

[TheQ42]

Further update:

The dealer is going to replace the part and see about getting me a loaner on Monday. Huzzah!

I also learned something new--there are further instructions in the TSB that apparently say to clear the codes before repairing. So that means that, as long as the codes showed up in the last 60 days of vehicle code history, they can continue with the warranty repair (replacing the HVBJB) without trouble.

Hopefully that last bit of info can help others that get stuck in my situation. I'm actually impressed with how quickly this particular dealership responded to my complaint and how quickly they're working to resolve it.

Sponsored