TSB 24-2017 - HVBJB Replacement - Service Vehicle Soon or Stop Safely Now Message

[Shayne]

'23 GT-PE.

So I had a SSN (with a P0ADA showing in FDRS) on Jan 12th, and due to scheduling at my dealer I waited to take my car in for about 4 weeks. Car goes in and they do some PTS reading and discover this new updated TSB, and when they do the pinpoint diagnostics and are asked if there are any other codes besides P0ADA, and the tech says "No" because there aren't any, FDRS says 'you're done'. So they consulted with the techline and after much deliberation they were told to reset the BECM counter, test drive the car, and if the SSN doesn't reappear during the test drive, give the car back to the customer, (but tell parts to hold on to the replacement HVJB they ordered, as they may still need it later).

So my wife's a bit out of sorts that she couldn't drive the car for a month or so (yes, I know you can drive it with reduced power, but I had other things to drive) only to be told later that it was a minor glitch, and everything's okay now...but it may happen again.

From the Ford tech line. Evolving Ford service. Reset limp mode for owners a couple of times and see if that works. Does not matter what they put owners through at this stage the damage is done. Selling like hot cakes and the best EV manufacture ever. If they make mistakes rest assured they will fix them. No government body needs to force them to do that.

Sponsored

 

[Mike G]

I wonder if anybody at Ford is looking at how may cars are throwing the P0ADA CMDTC but not throwing any other codes along with it that would specifically identify which condition (contactor open, contactor closed, contactor welded, etc.) caused the P0ADA error.

I would think that would be an interesting number to look at. It would also mean that maybe they need to tune the sensitivity so that these false positives (if that's what they are) don't show up.

I'm sure it's a fine line....

 

[Shayne]

I wonder if anybody at Ford is looking at how may cars are throwing the P0ADA CMDTC but not throwing any other codes along with it that would specifically identify which condition (contactor open, contactor closed, contactor welded, etc.) caused the P0ADA error.

I would think that would be an interesting number to look at. It would also mean that maybe they need to tune the sensitivity so that these false positives (if that's what they are) don't show up.

I'm sure it's a fine line....

Mine said contact stuck open when the HVBJB failed the first time and contact stuck closed when it failed the second which were different codes in the car scanner program. Do not remember the codes but can dig them out if you want from my old saved code dumps but stuck open and stuck closed do not yield the same code (think the TSB has them). I think the A code is closed?

Since this has been going on for over three years now they may have a grasp on how many they have. Maybe it is too high of a sensitivity for limp mode that was put in place instead of bricking it and stranding you. Ever way the HVBJB is not 100%.

 

[Mike G]

Mine said contact stuck open when the HVBJB failed the first time and contact stuck closed when it failed the second which were different codes in the car scanner program. Do not remember the codes but can dig them out if you want from my old saved code dumps but stuck open and stuck closed do not yield the same code (think the TSB has them). I think the A code is closed?

Since this has been going on for over three years now they may have a grasp on how many they have. Maybe it is too high of a sensitivity for limp mode that was put in place instead of bricking it and stranding you. Ever way the HVBJB is not 100%.

Ah well as it turns out I don't think that's the problem I have....well in fact I don't know what the problem actually is, except to say that I got a SVS with a P0ADA code but no additional code(s) that would have provided a clue as to what condition caused the fault. So the tech was instructed by the techline to reset the BECM counter (which made the DTC go away) and test drive the car to see if the condition came back. It didn't. So they gave me the car back.

I'm sure one day I will again get a P0ADA eventually. Maybe then I'll have an additional code that provides a clue that's "actionable".

 

[Shayne]

Ah well as it turns out I don't think that's the problem I have....well in fact I don't know what the problem actually is, except to say that I got a SVS with a P0ADA code but no additional code(s) that would have provided a clue as to what condition caused the fault. So the tech was instructed by the techline to reset the BECM counter (which made the DTC go away) and test drive the car to see if the condition came back. It didn't. So they gave me the car back.

I'm sure one day I will again get a P0ADA eventually. Maybe then I'll have an additional code that provides a clue that's "actionable".

I have not been into it long. I have machines and know tech/mechanics. I limit tech to Swiss army knives to preform a function and until this car never needed an OBD2. I understand the tech you can put into a L2 charger but the dumb one will do and count on the car kind of thought. Wish they would log dates on dumps in car scanner along with the code that would help. Anything that does?

First dump Jan 8 2022. What I notice was each time my 12V was killed I got the stuck open one.

Spoiler

============1==============
P0AA2
Raw code: 0AA2
ECU: 7EC
Status: Confirmed
OBDII: Hybrid battery positive contactor - circuit stuck open
============5==============
P0AA2(00)
Raw code: 0AA200
ECU: 7EC
Status: Pending, Confirmed, Test failed since last DTC clear, Warning indicator requested
OBDII: Hybrid battery positive contactor - circuit stuck open
============44==============
P0AA4(00)
Raw code: 0AA400
ECU: 7EC
Status: Test not completed during this operation cycle
OBDII: Hybrid battery positive contactor - circuit stuck closed
============331==============
P0AA2(00)
Raw code: 0AA200
ECU: BECM
Status: Pending, Confirmed, Test failed since last DTC clear, Warning indicator requested
OBDII: Hybrid battery positive contactor - circuit stuck open

After the first HVBJB (along with the BECM back then) the car has not died once. At the same time however a program was added for mine and it now auto comes on when cold and precondition the car by itself.

Second; No real noticeable change just a bunch of error messages on multiple devises and craps out the cars spunk. The lack of spunk result is also not great.

============18==============
P0AA1(00)
Raw code: 0AA100
ECU: 7EC
Status: Test not completed during this operation cycle
OBDII: Hybrid battery positive contactor - circuit stuck closed

Reset the the counter and give the car back. You get your spunk back. Problem solved.

 

[Luke]

Do you guys know if the HVBJB now is the same exact part as back in 2022? I had this replaced on my 2021 MME back in December 2022. Today I got the same error, and it was diagnosed with that service bulletin above.

 

[Shayne]

Do you guys know if the HVBJB now is the same exact part as back in 2022? I had this replaced on my 2021 MME back in December 2022. Today I got the same error, and it was diagnosed with that service bulletin above.

I put up with a sticking contact from February 2021 to April 2022 at which time the HVJB was replaced. In September 2023 the second one went and that needed to be replaced. I can not speak as to what was going on in December 2022 or your vehicle in particular. There was one here that had multiple HVJB replaced and had some of them installed after the time yours was. They gave up and switched to a different EV manufacture. The A series design was a dud but appears things have gotten a bit better and the design is a bit more robust? There is a number of revisions of the HVJB design but what you had installed in December 2022 who knows? The part number they installed back then should be on your invoice.

 

[Elar]

I had the same code.
I also had the code reprogrammed and knocked out.
I'm going on a 2x500km trip in 4 days, and I'll be careful with the accelerator...
Is there any chance that I will not have a problem?
If, God forbid, it's written off again, but the car is mobile, can I use it?

 

[MrLoganRoss]

Assuming there are no concerns with the ‘23 job 2 vehicles?

 

[Mike G]

I wanted to revisit this thread...simply to let folks know that after getting the BECM Counter reset when I had that P0ADA code (back on the 12th of Jan this year), that I haven't had a SSN since. Zero issues.

 

[Elar]

I wanted to revisit this thread...simply to let folks know that after getting the BECM Counter reset when I had that P0ADA code (back on the 12th of Jan this year), that I haven't had a SSN since. Zero issues.

Hmm. That's good
I read in another thread that someone's fast charging was not good after replacing the relay. It didn't go above 42Kwh.
Some code was not reset
Could this be a real problem?

 

[Mike G]

Hmm. That's good
I read in another thread that someone's fast charging was not good after replacing the relay. It didn't go above 42Kwh.
Some code was not reset
Could this be a real problem?

Haven’t heard that.

 

[Shayne]

I wanted to revisit this thread...simply to let folks know that after getting the BECM Counter reset when I had that P0ADA code (back on the 12th of Jan this year), that I haven't had a SSN since. Zero issues.

On a 2023? So it is not damaged nonfunctioning contacts it is a software reset now? Does that mean they spent a lot on a recall for nothing. Hard to believe they would do that. Wonder how many resets until they replace the part now. Permanent limp mode may be?

 

[Elar]

Haven’t heard that.

https://www.macheforum.com/site/threads/horrible-dc-kw-rate.37000/page-2

 

[Mike G]

On a 2023? So it is not damaged nonfunctioning contacts it is a software reset now? Does that mean they spent a lot on a recall for nothing. Hard to believe they would do that. Wonder how many resets until they replace the part now. Permanent limp mode may be?

This was on a '23 model. and apparently the techs at my dealrship were told that since my car had the latest HVJB there is already, that it might have been a software problem and to do a BECM reset first, and if the problem came back then to proceed with normal diagnostics per the workshop manual. So they did that, and the problem hasn't returned. Yet. It's been nearly a year since they reset the BECM counter.

Sponsored