In sunny weather today, I noticed in the Remote Console that the batteries’ charging current (200 A) is significantly higher than the CCL value (80 A), which shouldn’t happen.
I just checked this again in VRM (15-minute log interval).
As far as I can tell from VRM, the CCL is exceeded (often by a lot) more frequently with Venus 3.80; with 3.75, everything seems to be working correctly.
Until this issue is resolved, I’ve rolled back to 3.75 for now.
Yes, that’s true, but it also applies to older versions — it was already like that here in 3.66, for example. If you read carefully, it’s also mentioned in the DVCC documentation.
There shouldn’t be any problems with an off-grid system that isn’t connected to the grid.
The known issues affect systems that are grid-connected and have DC surplus feed-in enabled.
Is the battery selected as the controlling BMS in DVCC?
Try manually limiting the charge current in DVCC as a test.
I’ve checked the settings in DVCC again. I can’t find anything wrong.
I only noticed this because a charging current of 200 A was flowing at 98% SOC.
The current Pylontech firmware normally throttles down much earlier.
So I took a look at the CCL value.
The system only has the components listed in the text.
I ran another test today and booted up with FW 3.80 at 98% SOC.
Immediately after booting up (remote console accessible via VRM), the CCL was once again NOT maintained (target 40A, actual 107A). I aborted the test to protect the batteries and rebooted with FW 3.75.
Immediately after restarting (remote console accessible via VRM), the CCL was maintained without any issues with FW 3.75.
What firmware are the batteries on? Were they recently updated?
As a test, does it behave without dc feed in enabled?
Please confirm that with no other changes it honours ccl on 3.7x?
Same here — my Pylontech bank on 3.80 also charged past the BMS CCL on low-SOC mornings, and 3.75 behaves correctly. Good to hear a fix is on the way; I’ll hold off updating my systems until then.
