Some friends and I purchased 12 server rack batteries GP-SR1-PC200 with an additional 5A active balancer and we are all struggling with the same problems in combination with the Deye Sun 12k inverter:
1.) Below 15% SOC the battery will be charged again and again. Obviously this is triggered by the BMS.
=> Is it possible to change the BMS firmware to be able to disable/adjust that behavior? Otherwise it is not possible to really use the "usable energy" of 14.3kWh promised in the datasheet/usermanual.
2.) The 5A Active Balancer seems to be always active. This may lead to an imbalancing of the cells in the mid voltage range of the cells because the SOC-U-characteristic is very flat there and even small tolerances in the voltage measurement or the cells itself might have a negative effect. Because of that it is normally state of the art to do only top-balancing.
=> It would be a big improvement if the firmware could be adapted so that e.g. one of the DRY-contacters could be reprogrammed in a way that it is activated always if the internal balancer gets active, too. => In combination with a small HW-change (which we could do on ourselves) this port could be used then to activate the Active Balancer synchronouosly to zhr internal one.
Force charge below 15 SOC + 5A-Active-Balancer always on
Re: Force charge below 15 SOC + 5A-Active-Balancer always on
We are developing a new firmware to modify the 15% Force Charge limit.
For the DRY contacters, we will try to add this function.
For the DRY contacters, we will try to add this function.
Re: Force charge below 15 SOC + 5A-Active-Balancer always on
Hello,
is there any news regarding this post? I would also like to have the opportunity to switch the balancer together with the internal balancer of the BMS.
I received 4 Premium packs recently with 3 different FW versions (one with 1.0.1, two with 2.0.0 and one with 2.0.1) and would like to upgrade them to the same FW. If Gobel permits an upgrade of the FW, I would prefer to upgrade to a version that already supports this function.
Greetings
ASdt
is there any news regarding this post? I would also like to have the opportunity to switch the balancer together with the internal balancer of the BMS.
I received 4 Premium packs recently with 3 different FW versions (one with 1.0.1, two with 2.0.0 and one with 2.0.1) and would like to upgrade them to the same FW. If Gobel permits an upgrade of the FW, I would prefer to upgrade to a version that already supports this function.
Greetings
ASdt
Re: Force charge below 15 SOC + 5A-Active-Balancer always on
New firmware is still under development. Expected to be released this month.
It is not necessary to upgrade firmware right now, new firmware only updated the inverter list and added heat function.
It is not necessary to upgrade firmware right now, new firmware only updated the inverter list and added heat function.
-
- Posts: 2
- Joined: Tue Nov 28, 2023 11:07 am
Re: Force charge below 15 SOC + 5A-Active-Balancer always on
Any news on this new firmware?
Re: Force charge below 15 SOC + 5A-Active-Balancer always on
I just wanted to flash the new firmware. Unfortunately my BMS is a P16S-200A-21606-1.01 but the linked firmware seems to be only for P16S-200A-21606-2.xx. => is there also a new firmware for the V1.xx?
Besides that I read the changelog and I am not very happy with the details of the changes:
Besides that I read the changelog and I am not very happy with the details of the changes:
- it seems that the "Force Charge" is at a fixed SOC-level which is now lower - but neihter adjustable (to 0% SOC) nor completely deactivatable.
=> In my understanding mit does not make very much sense to pin that function to a value which is not measurable but completely calculated. The SOC is calculated by integration of the currents. But as the measuring tolerances are integrated, too and because the ccruent sensor does not even see the current of the balancer (and its losses) the SOC-value will get very inaccurate over the time.
=> Instead it would be much better to pin the force-charge-function to the UV-Protection limits ("Pack UV Protect"/"Pack UVP Release" and "Cell UV Protect"/"Cell UVP Release"). Then the advantage would be that it is adjustable and the value on which it depends is really measurable. - The feature to use the DRY contactors for controlling the active balancer seems to be missing. Or is it just not documemted in the changelog?
Re: Force charge below 15 SOC + 5A-Active-Balancer always on
Please give me more time.
Re: Force charge below 15 SOC + 5A-Active-Balancer always on
DRaichle wrote:The 5A Active Balancer seems to be always active. This may lead to an imbalancing of the cells in the mid voltage range of the cells because the SOC-U-characteristic is very flat there and even small tolerances in the voltage measurement or the cells itself might have a negative effect. Because of that it is normally state of the art to do only top-balancing.
=> It would be a big improvement if the firmware could be adapted so that e.g. one of the DRY-contacters could be reprogrammed in a way that it is activated always if the internal balancer gets active, too. => In combination with a small HW-change (which we could do on ourselves) this port could be used then to activate the Active Balancer synchronouosly to zhr internal one.
i and some friends have the older GP-SR1-RN150 battery. There is the same problem. The 5A Heltec balancer runs always from 2,7-4.5V. The balancer includet in the 150A BMS start an 3.4V (adjustable in the software). The Heltec has a RUN contact.
It was very nice, when the BMS balancer gets active the Heltec goes also active (need cable from BMS contact to RUN contact).
Re: Force charge below 15 SOC + 5A-Active-Balancer always on
Here is updated firmware for V1 version:
https://drive.google.com/file/d/1TH-S2K6W0_DrU26O0djeuhyhP8mPEyau/view?usp=drive_link
Change log:
1. Modify Pylon/Deye Force Charge condition. Force Charge start SOC = Low SOC Alarm + 3, release SOC = Low SOC Alarm + 10
https://drive.google.com/file/d/1TH-S2K6W0_DrU26O0djeuhyhP8mPEyau/view?usp=drive_link
Change log:
1. Modify Pylon/Deye Force Charge condition. Force Charge start SOC = Low SOC Alarm + 3, release SOC = Low SOC Alarm + 10