Fresh from “the other forum” and battling with the technicalities here…so please excuse if I am not posting correctly.
So I bought three Hubble X-100’s early in 2020 to run with my Sunsynk 8kw.
After running my system for about six months I wanted to add two extra X-100’s.
Surprise surprise. They were discontinued and the replacements were not compatible - different chemistry and voltages I think ? Hubble could not help just saying they were working on a solution.
As far as I could establish, the Leoch/Aveverge LFeLi 4800TB batteries were assentially identical - and bought two units.
The problem is in the communication. The three Hubble batteries communicate through their RS232 Via Riot device over CAN with the Sunsynk.
The two Leoch batteries apparently uses a different protocol.
I am now monitoring the two Leoch batteries and the Sunsynk separately via Solar Assitant while the Inverter reads SOC only from the three Hubble batteries.
They are all connected in parallel to copper busbars in my server cabinet.
Not sure if the use the same BMS.
Externally they are identical - same displays and voltage spec stickers. The Hubble S/numbers even read 48100TB… same as the Leoch/Averge.
Any ideas of how to solve my comms integration ?
Maybe @Louisvdw’s serial driver can be mangled to read from two BMSes and present a 3rd combined device?
Or you’ll probably need to replace or at least reflash one of them.
@mariusm was also thinking reflashing firmware, but that is not my strong point.
Let’s hear what @Louisvdw has to say.
That’s really unfortunate and it’s one of the things that I pointed out in my last post on that forum about Hubble that made them bid me farewell and I’ve mentioned it a few times here as well. You just can’t release a battery and then within a year, change design and not make the new ones compatible or create some options. Scary thing is what happens if they do it again.
Coming back to your problem though, you need to figure out if the bms is the same in both batteries before trying to flash it. Hubble is a local brand, although probably a white labeled battery. @Stanley seems to know a lot about the bms and protocols of the different batterie so maybe he can also help.
We’re not close to something like that. So that would not be a viable short term solution currently.
I’m not sure which BMS they use inside, but the driver is build on top of VenusOS and the dbus system that Victron use, so all that will have to change. Could be done but not the focus currently.
Thank you @Vassen and @Louisvdw
@Stanley is there anythyng you can add ?
Any way for me to establish if the BMS’s are materially identical - except the protocol used - without opening the boxes obviously ?
If the BMSs are the same or at least use the same protocol then the Riot device should have no problem communicating with the Leoch batteries. Alternatively, you could see if the same monitoring software works, but you will need a USB to serial converter and you will have to make up a cable to plug it into the BMS.
On a (slightly) related topic… I’m assisting someone to optimise a Hubble AM-2 in a Victron setup. I’ve come across the RIOT as a comms option but would like to get some independent opinions on how well it would work in this setup…What functionality would the RIOT provide?
So has anyone actually added the current X-101 5.5kWh Hubble batteries to the previous gen X-100 4.8kWh batteries?
Hubble now claim they are compatible
Really? The datasheets make it seem like the X-100 is 15 cell LiFePO₄, while the X-101 is 13 cell NMC (making a couple of assumptions here, so I might be wrong).
I’m sure the BMS is the same, but NMC has a different charge/discharge slope than LiFePO₄. Perhaps it works but the NMC will discharge to the LiFePO₄ voltage, where it will stay more or less until the LiFePO₄ is discharged and then the NMC will take over again.
Yes exactly that - at 48V the X-100 is around 20% SOC, and at 48V the X-101 is still at around 50% SOC, so there will be a 30% “loss” of capacity. That effectively makes the new (added) X-101 have a 3.8kWh capacity.