Low voltage and BMS Communication Error

4 comments started 2025-07-17 last 2025-07-17
GivEnergy Products
S
#1 StephenSuffolk

Hi - we’re away on holiday but I noticed yesterday that we weren’t generating anything. Our son got home and confirmed that the MCD for our solar install (GivEnergy AC 3.0 with a 5.12kWh battery) had tripped. He flicked it back up and I could see from the portal that we started generating again yesterday evening.
However, the app still reports “We couldn’t detect any battery packs connected to this inverter” and the inverter logs show both Low Battery Voltage (now below 3V) and BMS Communication Failure.
I’ve restarted the inverter and so far neither of the errors has cleared. We’re on Octopus Intelligent Flux, so they are controlling our battery. I can see them issuing API calls to charge the battery but apparently without effect.
Is there anything else I can do remotely to figure out what’s going on?

S
#2 SteveCook

Has the BMS cable come out of the bottom port of the inverter, There is no mechanical restraint (or clip like an RJ45) on my Gen1, and the plug used to drop out and I would get BMS comm failure.

S
#3 StephenSuffolk

SteveCook thanks - will ask our son for a video call when he gets home later to see if that’s it. Sounds like a flaky design if a cable can just drop out …. ?
To check my understanding - if that is the problem there will be a cable running from the battery (on the floor) with a loose end that should be connected to the inverter (mounted immediately above the battery)?

S
#4 SteveCook

I dont know about AC 3.0
On my Hy Gen1, there are power cables connecting the battery to the inverter and a comms cable for the BMS (Battery Management System). My comms cable went up inside a plastic shroud that screws onto the bottom of the inverter to cover the various ports. There is no clip on the comms cable plug (unlike RJ11 or RJ45), or any mechanical restraint, and as the port is on the underside the weight of the cable (or if it gets knocked) allows the plug to fall out, casing the error. I took the shroud off, pulled some slack through, folded the cable and wrapped tape around it so it formed a small "ball" and pulled it back into the shroud to act as a mechanical restraint. I then plugged the connector in and put the shroud back on. No problems now in nearly 3 years.
Suggest anything you do is with everything powered off and shut down