Can an incorrect CANBus cable drain the battery?

Q&A and troubleshooting
, ,
1

Need some preliminary advice on a rather weird incident if someone with knowledge can help?

I have a friend that has run a DIY Victronsystem with a 6kWh LiFePo 48V battery offgrid and it has worked without issues for a year or so. Venus GX, CANBus BMS, Multiplus.
He today called me after uploading an (incorrect?) veconfigurefile after which the battery voltage dropped pretty quickly, from 53.5 to 49V in maybe two minutes according to the logs. This could be causality/correlation I guess, but it did happen after this upload.

My question:
Could this be caused by an incorrect CANbus cable only?

I can think of some other external things which the troubleshooting will hopefully tell
but for now, since the system was working well, is this a possibility?

2

4kwh drain in 2 minutes ?

Not possible, all wiring would be burning.

So the measurement side must err.

1 Like
3

Thanks for reply, appreciated!
I understand that the voltage drop can not be due to a 4kWh draw but I guess I am wondering if it could be caused by an incorrect veconfigure file that might have affected the readings in the GX via the Multiplus. Might be a long shot, but if that is not it, I guess we suspect a damaged battery or cabling via rats or water or something. No one at the site at this time that can check physically.

4

Loading new firmware into a multiplus deletes all user data and programming, so you’ll have to check there first.

5

The battery could have tripped on the restart with the inrush.
It is usually best to theae things with no loads.

6

Thanks for your replies!
An engineer has been to the site and although no visible damage, the battery is not accepting a charge, the app that comes with the battery says nothing is wrong and reports 100% SOC and correct voltages but the Victron gear is displaying low voltage warnings.
I suspect a faulty battery or the onboard BMS and can not see how any of the actions taken might have caused this. Not uploading the veconfigure file and not any faulty can bus cable or such could have caused this.
Or am I missing something obvious?

They will try a reset of the BMS and if that does not help, it is probably warranty time.

7

It was not a plain firmware file, but some veconfigure file.