CCL wird von Venus 3.80 beim Laden über MPPT überschritten

Anyone else seeing CCL being breached on Venus 3.80? Updated my Cerbo last week and now the MPPT (SmartSolar 150/100) is regularly pushing past the charge current limit coming from my Pylontech stack during solar absorption — never saw this on 3.75.

Setup for context:

• Multiplus-II 5000
• Cerbo GX (just updated, regrettably)
• Pylontech US3000C × 6
• SmartSolar MPPT 150/100

The Pylontechs are sending the CCL via CAN bus as normal, Cerbo's receiving it fine according to the console, but the MPPT just seems to... ignore it occasionally? Gets maybe 15-20A over the limit before it pulls back. Not catastrophic, but not ideal when you're trying to keep the batteries happy long-term.

Wondering if it's a timing/handshake issue introduced in 3.80 — like the DVCC is lagging behind a bit before it clamps the solar down properly.

Workaround so far: manually knocked the MPPT max charge current down in VictronConnect as a hard ceiling. Bit naff but it's keeping things behaved for now.

Raised it on the Victron community forum too but curious if anyone here's hit the same thing, particularly those running Pylontech with dual MPPTs — might be worse with more panels chucking power in at once.

Could just be a dodgy update on my end but feels a bit coincidental with the version bump. Anyone stayed on 3.75 deliberately? Starting to think I should've left well alone. 🙄

Hey @Curly38, yeah this is a known issue that cropped up with 3.80. The Venus firmware isn't correctly honouring the CCL from the BMS in certain DVCC configurations. Worth checking your DVCC settings first - make sure "Limit charge current" is properly enabled and that "SVS" (Shared Voltage Sense) is ticked if your setup supports it.

Quickest fix for now is rolling back to 3.79 via the remote console - Settings > Firmware > Stored backup firmware. Victron are aware and there's a bug report open on their GitHub already.

Also double-check your Pylontech firmware is current, as older stack firmware can sometimes send dodgy CCL values that compound the issue. What's your DVCC page showing for the actual CCL figure being received?

Rolled back to 3.79 on my Cerbo last month for exactly this sort of nonsense. Victron's changelog always sounds brilliant until you're actually living with the fallout 😅

Worth keeping an eye on the Victron Community forum — they usually push a hotfix pretty sharpish when Pylontech comms go wonky. That said, @Curly38 how long have your Pylontechs been running past CCL? If it's brief spikes that's one thing, but sustained overcurrent is a different conversation entirely for battery longevity.

Rollback procedure is straightforward via the Venus remote console if you haven't already — just grab the 3.79 .swu file from Victron's repo.

Has anyone logged exactly how far over CCL it's going? Curious whether we're talking a cheeky 2-3A overshoot or something more alarming. My Pylontech stack gets a bit dramatic about overcurrent and I'd rather know before I update my own Cerbo!

Is there a ticket open on the Victron Community forum yet, or just grumbling here? Victron are usually pretty decent at pushing a hotfix when something's actively hammering battery comms — presumably they'd want to sort this before anyone's BMS starts throwing a wobbly and disconnecting mid-day.

@StormyWelder — on my narrowboat setup (Pylontech US3000C stack, SmartSolar 150/85, Cerbo GX) I'm seeing consistent 8-12A overshoot above CCL under strong solar conditions. Worth noting it correlates with high irradiance and high battery SOC simultaneously — that's when the MPPT algorithm seems to ignore the DVCC-communicated limit most aggressively.

Logging via VRM shows the breach is repeatable, not random noise.

@KevClark has the right idea. 3.79 is stable. Until Victron push a hotfix, rolling back is the pragmatic call rather than risking repeated overcurrent stress on the BMS.

One practical mitigation if you can't roll back immediately: artificially cap your MPPT charge current in VictronConnect below where CCL typically sits. Clumsy, but it protects the cells while you wait.