HVBATT Errors

[mongo]

They keep telling me this is nothing, but I am getting multiple times and hour HVBATT MIa. See the attached log. It has been increasing since December. Yes, my screen needs cleaned

Are you already in the queue for the PCS replacement ? (a136 error)

Sponsored

 

[BlueLightning]

“Well? We just have no idea what it could be so we are replacing the most expensive item first and see if that fixes it?!”

So sad to see this, had similar errors on my Lightning, Ford could never figure it out, just kept replacing parts in hopes that it would correct itself.

In own defense of what was said above, Tesla in fact probably has a better idea how to correct the errors, then again maybe not?

LOL

 

[cyberHoward]

Are you already in the queue for the PCS replacement ? (a136 error)

Yep, July 20th. Rescheduled twice. It coincides with free supercharger. Was most recently July 6 moved two weeks. My service note still says parts in transit. They are replacing both the PCS and the harness. I really want to know what this MIa is. It seems something can't be right if constant errors.

 

[mongo]

Yep, July 20th. Rescheduled twice. It coincides with free supercharger. Was most recently July 6 moved two weeks. My service note still says parts in transit. They are replacing both the PCS and the harness. I really want to know what this MIa is. It seems something can't be right if constant errors.

MIA can be a momentary loss of communication. If it doesn't show up in active alerts then it could be an intermittent or start up sequencing issue.

 

[JCERRN]

My truck has the same errors (VCLEFT_a096_HVBATTCON_MIA) every few hours. No limp mode, charging fine. No active alerts each time I check.

 

[cyberHoward]

I am sure TESLA doesn't track that error for no reason. While it is harmless for now, I had several powershare issues and may not restart or charge in December/January and Tesla said it was nothing. Then in April my PCS failed after one more of those warnings. I even asked them to check my PCS when it was in for noise issue and they said I had nothing to worry about.

 

[Outdoors]

I am sure TESLA doesn't track that error for no reason. While it is harmless for now, I had several powershare issues and may not restart or charge in December/January and Tesla said it was nothing. Then in April my PCS failed after one more of those warnings. I even asked them to check my PCS when it was in for noise issue and they said I had nothing to worry about.

That always frustrates me when when I get an error on the service menu that seems serious and Tesla says nope if it's not customer facing it's not a big deal.

I don't know. Some part of me thinks that when I get those momentary loss of communications, it's a piece that's not connected well or a harness that might have an abrasion on it that eventually will not communicate at all.

 

[mongo]

That always frustrates me when when I get an error on the service menu that seems serious and Tesla says nope if it's not customer facing it's not a big deal.

I don't know. Some part of me thinks that when I get those momentary loss of communications, it's a piece that's not connected well or a harness that might have an abrasion on it that eventually will not communicate at all.

From my former automotive electronics days, "if the driver didn't notice, was there really an error?"
Also had the opposite end of the spectrum, calibration status flag was interpreted as a hard module fault.

Based on the wiring schematics, a cable issue seems like it would cause more errors than just PCS complaining about the BMS.

Sponsored