For 15S Pylontecs, the balancing will start as soon as both of the followings are true:
At least this is the way they are coming configured from factory and I doubt that many are messing with these parameters.
Maybe there are some differences in different version of firmware. Their newer stuff behaves like this?
I have a seen a couple that sit high for over 20 minutes sometimes until the whole pack voltage goes up but these are on bigger banks and also on the famous daisy chain ones, so from what i have see it is not as cut and dry as that. And the whole bank voltage needs to be much higher before anything starts to happen.
They have passive balancers that are balancing with about 70mA max. (50 ohm resistors).
So, in order to balance a cell that, for example, itās about 1A behind, it takes about 14 hours topsā¦
As for the balance parameters, older, newer, all the same.
Anyone can see them by connecting to the console port of the battery and using the config command.
Standard: 3.36V, 30mV.
Hereās also some quotes from their technical department, on a discussion about a heavily unbalanced battery:
When the voltage difference is between 100-200mV, it means the battery could be balanced.
The balancing is successful when the voltage difference is below 30mV. It may take 12h to balance the battery.
If the cells voltage difference is over 200mV, most of batteries couldnāt be repairable.
When the voltage difference is over 30mV and cell voltage is over 3.36V, it will start balancing automatically.
Thanks for the input.
What I am hearing is, since it is not behaving like that, we are taking a battery (or maybe batteries) in for a warranty check.
As it is not doing that at all.
I have learned some interesting things from @alexpescaru today @DuivertNL. Appreciate the confidence though.
Is Pylontech still using 15S configuration ?
If Iām not mistaken my BYD (B-Box Premium LVL) is 16S, my Pytes (E-BOX 48100R) set certainly is.
Most of their batteries are 15S. Only the UF5000 is 16S.
Take a look at this Pylontechā¦
The charging current was set low, at about 8A, because the low the current is, the better the battery will behave when it has problems and you try to solve them.
Look how strange the min and max voltages have behaved, when the limiting charging algorithm kicked in at 23:00 in order to keep the max cell voltage below 3.52V.
At that moment the min cell voltage dropped and stayed even below 3.36V for a long period of time, with a voltage delta of 190mV !!!
Look at the charging current, when voltage was limited. Is only 100mA, the balancing current and some for the BMS.
But slowly the low voltage cell recovered and ultimately balanced, after 5 hours !!
Ignore the spike at 23:20, as it was a test from my part to see how the low voltage cell will behave.
So patience is gold in this caseā¦ In the end, all good things come to those who waitā¦ 
The scaling makes it look terrible. Lol
So the bank goes through a hub. A lot in the monitoring is not passed on interestingly enough. I any case i have re engaged Pylontec
Thats great bit 5 hours of high voltage warnings is not.
Update on the issue. Looks like overload was caused by voltage stabilizer. Tested several stabilizers with different firmwares, some behave more adequate some less. In the end, removing the stabilizer completely solved the issue.
As an FYI it works better if the voltage stabiliser are on the output of the inverter
I thought it is better to put it before, just for sake of charging battery with constant voltage, or it is doesnāt matter?
From the grid, the victron can control what to connect to and what to reject and how much to load it. The LOM detection and avrs donāt do well. But for your load side the voltage is important to keep stable use the avr
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
