Wenn du Hilfe benötigst, 🔍 suche bitte, bevor du einen neues Thema oder Beitrag erstellst.
Hallo zusammen,
ich habe aktuell eine Anlage mit folgendem Aufbau:
- Wechselrichter: Deye SUN-15K-SG01HP3-EU-AM2
- Batteriespeicher: Deye GB-L Hochvolt
- 4 Batteriemodule (16,36 kWh brutto / 14,72 kWh nutzbar laut Datenblatt)
Die Kommunikation läuft über BMS Lithium Batt (CAN).
Nun zu meinem Problem:
Der Speicher beginnt bei ca. 10 % SOC zu laden und erreicht anschließend 100 % SOC. Im Batteriebericht bzw. Logger werden für diesen Ladevorgang jedoch nur ca. 7 kWh Ladeenergie angezeigt.
Folgende Punkte habe ich bereits geprüft:
- PackNum = 4 (alle Module werden erkannt)
- Batteriespannung bei 99–100 % SOC: 438–448 V
- Unterer SOC: 6 %
- Speicher lädt bis 100 %
- Keine offensichtlichen BMS-Fehler
- BMS-Kommunikation funktioniert grundsätzlich
Eigentlich würde ich erwarten, dass von 10 % auf 100 % deutlich mehr als 7 kWh geladen werden – eher im Bereich von ca. 13 kWh DC.
Jetzt stellt sich mir die Frage:
- Ist die Anzeige bzw. der Batteriebericht im Deye-Portal fehlerhaft und die Batterie arbeitet tatsächlich korrekt?
- Oder könnte der Speicher tatsächlich nur einen Teil seiner Kapazität nutzen?
- Hat jemand dieses Verhalten bereits bei einem GB-L in Verbindung mit einem SUN-15K-SG01HP3-EU-AM2 beobachtet?
- Gibt es bekannte Firmware- oder BMS-Probleme?
Über Erfahrungen oder Hinweise würde ich mich sehr freuen.
Vielen Dank!
Your modules are most likely unbalanced.
That means the SOC of one module is higher or lower than SOC of other ones.
Did you ever expand the battery by adding more modules?
If yes, this could be the consequence of not following the right procedure for expansion.
If no, then this is just a consequence of long term battery use without proper balancing.
Because all modules are effectively wired in series, your usable capacity is reduced, if one module is out of balance.
If one of the modules is at 100%, while the other is for instance at 85%, that means you loose 15% capacity "at the top". And then when you discharge the second module will be at 10% while first one is at 25%.
You can check the cell voltage data on Cloud, to see what is the voltage difference at 100% and when battery hits 10% SOC.
To fix this you can disassemble the battery and use a DC charger to "top up" all modules to same voltage. For instance, if you charge all the modules to 108V-109V, you should be quite close to 99-100% on all modules. But you must wait until charging current drops down to 0A at 109V.
Don't charge higher as you might overcharge the cells.
But that is usually not a permanent solution.
Write to Deye support, tell them that they should install firmware that enables modules balancing.
They usually do not want to do it right away (I don't know why), but that firmware is only thing that will prevent this from happening again, and should be installed on all GB-L batteries sooner or later... otherwise we will have much more problems like this very soon.
@tribesman So that means they have a separate piece of software that can be installed for such cases, independent of the current battery firmware MCU3_HVCUE16XXXXXXXX.bin?
Write to Deye support, tell them that they should install firmware that enables modules balancing.
Yes, there is a specific version of FW that enables module balancing.
But it works in a peculiar way. It does not balance while the battery is sitting at 100%.
You need to cycle the battery for balancing to work...
Don't ask me why is that... or why is that FW not a "standard issue".
@tribesman That’s complete nonsense you’re talking. I’ve been in touch with DEYE—there is no separate software that does this. Why are you spreading such rubbish here? If this software really exists, then name it clearly and specifically.
I guess this does not exist... fine then 🙂
Ask Deye support why are they unwilling to install this FW as a "standard issue".
It is available for weeks now, but you have to argue with them and if you want to get it installed. ¯\_(ツ)_/¯
It just the way this company works.
And it is really not nice of you to accuse me of talking nonsense, when you obviously have limited knowledge about the issue and no direct contact with Deye engineers.

