Hubble Batteries

Referring back to my emails with hubble, I believe those settings have no effect unless you change battery type to AGM and battery operation to voltage.
 
Referring back to my emails with hubble, I believe those settings have no effect unless you change battery type to AGM and battery operation to voltage.
and then it explodes or at least warranty is void.
 
Mine is set as follows by the installer :/

Battery float charge voltage
55.2 V
Battery absorption charge voltage
57.6 V
Battery equalization charge voltage
57.6 V
Why aren't you guys using battery comms? Surely that's the better way of handling this?
 
What facts?

The batteries are AM2s - hence the question - the specs on the battery are also different to the above.
View attachment 1710023
Your installer was Drunk when they put in AM5 Voltage settings for AM2 Batteries - lucky your BMS ignores it but it's far from ideal,glad you updated it at least
 
Why aren't you guys using battery comms? Surely that's the better way of handling this?
Could be the BMS port's in use by something else,Cloudlink/Solarassistant/ICC/Sunsynk being a toss/incompatible/whatever
 
Your installer was Drunk when they put in AM5 Voltage settings for AM2 Batteries - lucky your BMS ignores it but it's far from ideal,glad you updated it at least
Think it was pre-AM5 (2022) - maybe he just left them default?
 
Can see why mines was set as 53.6, because it's the same as @xrapidx label and that's what my installer used , even though the comms protocol is BMS.

Still have no Eskom grid (fsck eskom) and the batteries got down to 10% overnight and battery 2 was at 4% and batt 1 was at 35% or something. I will do the 0 test when I get back home.

This is the SoC history overnight.

The voltage of both batteries are identical

Screenshot_20240516_141247_Home%20Assistant.jpg
 
Can see why mines was set as 53.6, because it's the same as @xrapidx label and that's what my installer used , even though the comms protocol is BMS.

Still have no Eskom grid (fsck eskom) and the batteries got down to 10% overnight and battery 2 was at 4% and batt 1 was at 35% or something. I will do the 0 test when I get back home.

This is the SoC history overnight.

The voltage of both batteries are identical
My labels vary by generation,Hubble support said SET THEM ALL TO 53.8 so that's the mantra
 
Think it was pre-AM5 (2022) - maybe he just left them default?
There was never a time to default to that for AM2 - they could have just read the battery label,those are very specific to LFP values too,maybe they assumed it's an LFP not NMC?
 
I had that same issue last winter with the large (not as large as yours) SOC variance (its actually why I have communication with hubble)... they recommended the following

1. Disconnect the CAN communication cable.
2. Change the battery type of the inverter to AGM V.
3. Please input the Float, Bulk and equalization Voltage (Eg. AM2 = 53,8Vdc).
4. Then set the DC Low Voltage to 44Vdc (For AM2).
5. .Kindly charge up battery until the inverter stops charging the battery at 53.8Vdc, this may take some time as the BMS will do a cell balance or equalization at full voltage i.e. 100% SOC.
6. Once inverter has stopped charging, reconnect your CAN cable, go back into your inverter battery menu setup and activate the Lithium settings and CAN communications.

I never got round to doing it - set my batteries to maintain 100% with grid charging for a few hours resolved my issue.
 
Last edited:
There was never a time to default to that for AM2 - they could have just read the battery label,those are very specific to LFP values too,maybe they assumed it's an LFP not NMC?

Rather annoying then... fortunately it would have been resolved if I actually did the above post.
 
Can see why mines was set as 53.6, because it's the same as @xrapidx label and that's what my installer used , even though the comms protocol is BMS.

Still have no Eskom grid (fsck eskom) and the batteries got down to 10% overnight and battery 2 was at 4% and batt 1 was at 35% or something. I will do the 0 test when I get back home.

This is the SoC history overnight.

The voltage of both batteries are identical

View attachment 1710189
What is your SOC Cut off?
Does anyone else set their SOC cut off so low?

I have my AM5 set at 23% SOC Cut off.
 
If you're using comms, you guys do realise that the voltage sessions only come into play when something goes wrong, like a rat eats the cable?
 
Top
Sign up to the MyBroadband newsletter
X