I am using two Felicity FLA48230-EU battery packs, each 48V/11.7kWh. Both are connected in parallel to a Lynx IN and are connected via a Lynx Distributor to three Victron Multiplus 6k5s configured in 3-phase. The Felicity battery packs are configured as device 1 (DIP switch settings 1.5 to ON) and device 2 (DIP switch settings 2.5 to ON) and are connected to the Cerbo GX via device 1 on LAN 0. The entire system is connected using the VE.Can bus 2 protocol CAN-bus BMS LV (500 kbit/s). The communication protocol on the Felicity is set to PYLON2.
However, I notice that the battery packs are not being charged evenly (currently there is a difference in SOC of 79% vs 82%) and that the Cerbo dashboard alternately displays the SOC of device 1 or device 2. I wonder if this is a problem with the Felicity or the Cerbo, or if it is not a problem at all. I would appreciate hearing from anyone who has experience with this.
Sorry, can’t write Dutch… I would not worry about the SoC difference, once the batteries get fully charged they’ll even out again… the BMS in that battery is probably less than great, also, what can make a difference, not one to panic about, but still, is, if the battery cable lengths are different for the 2 batteries, by a significant amount, half a meter or more, then the battery with the shortest cable is likely to provide more of the power…
I have 4 batteries and only use the SmartShunt for SoC, I do have the bateries indicated ion Home Assistant and the %ages do not line up at the best of times, except when things get to full…
Can’t upload a 33kb screenshot, but the gist is, right now:
I believe the Smart Shunt more, although it underestimates, by around 1.6% I saw last time after the battery bank came back up to full, after having turned around at 22%.
It does. Thanks for your quick response. It definitely helps to understand battery behavior. However, the question was more about the fact that Victron apparently switches between the two batteries other than leveling them out to an average soc which means I get different readings on my console depending on which battery gets displayed. Not sure if that is by design or not.
I found the solution. When checking the ve.can port errors I noticed quite a lot of errors on the can bus. TEC went up to 130 sometimes which caused the bus to go into ERROR-PASSIVE mode some times.
The felicity BMS cable was connected to ve.can port 2 while nothing was connected on ve.can port 1. The ve.can port 1 was earlier disabled by me on the Cerbo as it seemed easier for me to use the outside ve.can port and on some pictures on the internet I noticed that at that position on earlier models this used to be a specific ve.can BMS port, so I did not consider this to be an issue. However, when trying different options I noticed that, when I moved the (home made) felicity BMS cable to ve.can port 1, the felicity BMS now shows up on the Cerbo with a combined (added up) load of both battery packs which did not happen when I used the same cable with the same configuration on ve.can port 2.