Hi,
last summer I installed a fairly easy setup:
- Cerbo GX MKII
- 2x MPPT 150/35
- 1x Battery (Felicity Solar with Pylontech compatible BMS, connected via CAN to the Cerbo GX)
The setup works quite well, however since it is installed in a garden shed, the temps now dropped below 0° C a couple of times.
I konw that the battery’s BMS has a low temperature protection and therefore I was not surprised to see the message “ESS #3 BMS disabled charging” or “ESS #4 BMS disabled discharging” if the battery is empty). However the reported temperature of the battery has once again risen to about 8° which is plenty above what the manufacturer says is fine for charging, however ESS #3 stays.
If I look at the Remote Console of the Cerbo GX it also shows ESS#3 on the main screen. However, if I go to the Pylontech Battery and select “Alarms”, all Alarm states say “OK”. I would have imagined, that the LowTempWarning would have tripped?!. The battery itself also shows no alarms on its LED-display.
Where is ESS #3 pulled from and does it need manual resetting?
regards,
Darky
The message is triggered by the battery itself. So is reason 4. And no, neither need manual intervention.
See the ESS manual here.
1 Like
What conditions trigger the ESS #3 to go away or reset? Does the battery voltage need to drop below the float value AND the SOC needs to drop below some value, say 95%? Then does the condition goes away as the BMS says that it’s ok to charge again?
#3: BMS disabled charging
#4: BMS disabled discharge
The bms itself is making the call here. it varies between manufacturers so i can’t say for sure what your ones - felicity solar ones do.
For some manufacturers the disabled charging is when the battery is full and is balancing or has balanced and doesn’t want more power. Not necessarily when it discharges drops to float voltage. Possibly as it drops under that.
One battery i had from a random manufacturer actually waited until 50% soc before allowing a charge again.
Does the felicity solar us Current Control and Voltage control or just current control? (Bms widget in vrm advranced)
Thanks for the quick reply. Very helpful! I am using a REC-BMS 1Q that protects a 2P8S 24 V 480 aH LiFePO4 battery built from CALB cells. What I am experiencing is that the BMS is apparently telling the Wakespeed WS500 to start alternator output because the battery has reached 100%. This is expected behavior. The BMS stop charging command is being expressed as a ESS #3 code that is showing on the VRM/Cerbo GX summary page. What is NOT happening is that the ESS #3 appears to be sticking and not being reset. This implies that the BMS is NOT re-enabling the charging command. This is the problem I am trying to solve. My assumption is that the BMS needs to see a certain voltage drop (below float?) and a certain reduction in SOC (95%?). I am checking the settings in the BMS webpage to determine if there is a mis-configuration. I am still digging into all of this