Cerbo GX – Strom des DC-Systems wird bei CCL=0 ignoriert

Bit of a niche one but wondered if anyone else has run into this with their Cerbo GX setup.

When CCL drops to 0 (charge current limit, usually when the BMS is saying "stop charging"), the DC system current reading seems to get ignored or zeroed out entirely on the dashboard. Noticed this on my garden office setup — the loads are still drawing from the DC bus but the Cerbo just shows nothing, like it's decided if there's no charging there's no point reporting anything.

Running a Victron SmartShunt alongside the Cerbo and the shunt itself still shows accurate figures, so it's not a hardware issue. Feels like a firmware/logic thing where the GX device is tying DC system calculation to the charge state somehow.

Had a similar (though not identical) quirk on the boat last season — Cerbo doing odd things with displayed values when the Fogstar 12V battery's BMS was asserting limits. Makes me wonder if the GX software just handles edge cases around BMS communication a bit inconsistently.

A few things worth checking if you're seeing this:

• VRM portal vs local display — do they show the same thing?
• Which firmware version are you on? (I'm on v3.30 currently)
• Are you using VE.Can or VE.Bus to connect the BMS?

Raised it loosely on the Victron community forum before but didn't get a clean answer. Curious whether this is a known quirk or something that needs a proper bug report raising with Victron.

Anyone else seen DC loads disappearing from the overview when CCL=0? Would be good to know if there's a workaround or if it's just something to live with.

@CE_Builds yes, seen this exact behaviour on my cabin setup running a Victron Multiplus-II with a Fogstar Drift 200Ah and a JK BMS.

When CCL hits zero the Cerbo essentially treats the DC system current as irrelevant to its power calculations — the displayed DC load figure goes a bit odd. From what I can tell it's less a bug and more an edge case in how the DVCC logic handles the transition: once CCL=0 the charge path assumptions break down and the current measurement context gets lost.

Worth checking in VRM whether your DC system power is being reported against the correct shunt. If you've got a SmartShunt on the DC loads rail rather than the battery main, the Cerbo can lose track during that CCL=0 window entirely.

Victron's DVCC documentation is genuinely thin on this scenario — raised it on the Victron community forum months ago, still no clear answer.

Seen this one crop up a few times with lithium setups on my narrowboat. When CCL hits 0, the Cerbo essentially stops polling DC current contributions from non-Victron devices because it assumes the system is in a "no charge" state — it's a known quirk rather than a true bug.

Worth checking your DVCC settings — specifically whether "Limit charge current" is enabled and whether your BMS is correctly flagged as the charge current control source. If your DC loads are being misreported, it's often because the Cerbo is suppressing that data path when it receives the CCL=0 signal via CANbus.

On my boat I run a Victron Lynx Shunt alongside the Cerbo which keeps DC system monitoring independent of the charge control logic — separating those two data streams sorted the display anomaly entirely. @CE_Builds worth trying that approach if you haven't already.

Classic edge case this one. The Cerbo's DC system power calculation leans heavily on the DVCC charge current data — so when CCL=0, it essentially loses its reference point and the displayed consumption figures go haywire.

What fixed it on my motorhome setup was making sure "Has DC system" was properly enabled in the Cerbo settings and that I had a SmartShunt wired as a dedicated DC monitor rather than relying on the BMS figures alone. The shunt doesn't care what CCL is doing — it's measuring actual current flow regardless.

@ExSquaddie49's point about polling is on the right track. The real issue is the Cerbo prioritising BMS-reported data over measured data when they conflict.

Worth checking your VRM data sources hierarchy too — sometimes it's just a misconfigured input priority rather than a genuine firmware bug.

Ran into something similar on my garden office setup — Victron Cerbo GX with a 280Ah LiFePO4 bank.

What I noticed is the DC system figure goes a bit meaningless during that CCL=0 window, but the VRM portal logs still capture the underlying data reasonably well if you dig into the raw feeds rather than relying on the dashboard overview.

Not sure it's purely a Cerbo issue though — feels like it might be more about how the BMS communicates state over DVCC when it's asserting a hard stop. My Daly BMS was particularly patchy about this.

@LiFePO4Nerd makes a fair point about the DVCC dependency. Worth checking whether your BMS is actually sending proper telemetry during that state or just going quiet, because that changes where the fault actually sits.

Backing up what @LiFePO4Nerd is getting at — the DC load reading essentially becomes unreliable the moment CCL zeros out because the Cerbo's calculation depends on current flow assumptions that no longer hold.

What I've found useful on my emergency backup setup is keeping an eye on the VRM portal's raw data rather than the dashboard readout during those BMS cutoff events. The underlying shunt data (if you've got a SmartShunt wired in) stays accurate even when the DC system display goes wonky.

Worth checking:

• Is your SmartShunt configured as the battery monitor in DVCC settings?
• Are you on the latest Venus OS? There were some fixes around DC system calculations in recent builds

If the SmartShunt is properly set up, you can at least trust that figure even when the calculated DC system power is garbage.