[BUG] DVCC Charge Current Limit ignores built-in Multi RS MPPT after V1.30 update

Been running into what looks like the same class of issue on my cabin setup and wanted to see if others are hitting this.

My kit: Multi RS Solar 48V/6000VA alongside a SmartSolar MPPT 250/100 VE.Can, all tied together via a Cerbo GX on the latest stable firmware. Battery monitoring via a Lynx Shunt on VE.Can.

Since the last couple of firmware bumps, DVCC's Charge Current Limit (CCL) appears to be correctly curtailing the external SmartSolar, but the built-in MPPT within the Multi RS itself seems to largely ignore the CCL — it just keeps pushing whatever the panels can generate regardless of what the BMS is requesting.

The practical consequence for me is the battery (Fogstar Drift 48V LiFePO4) occasionally seeing charge rates well above what the BMS is comfortable with, particularly in the shoulder seasons when temperatures drop and the BMS tightens its limits aggressively.

A few things I've verified:

• DVCC is enabled, SVS and SCS are both on
• BMS is communicating correctly — CCL values are visible and sensible in the VRM portal
• The external MPPT does respond to the CCL as expected
• Swapping to an older Cerbo firmware didn't appear to resolve it

My suspicion is there's a coordination bug between the Multi RS's internal charge controller and the DVCC layer — possibly introduced when they revised how the Multi RS reports its MPPT as a separate device on the VE.Can network.

Anyone else seeing this, particularly post-V1.30 on the Multi RS firmware? Would be useful to know if this is reproducible across

@SolarCol yes, hitting something very similar on the narrowboat. Since V1.30 the DVCC CCL seems to be applying correctly to the external SmartSolar but the built-in MPPT on the Multi RS is basically doing whatever it likes — saw it pushing well past the CCL limit yesterday afternoon with decent sun.

Worth checking in VRM whether the Multi RS is even reporting as a separate charge source under the DVCC overview, because on mine it sometimes drops off the list entirely after the update. Feels like the internal MPPT isn't being recognised as a managed device the same way an external unit would be via VE.Can or VE.Direct.

Raised it on the Victron Community forum too — there's a dev response suggesting it's a known regression. Might be worth linking your specifics over there to add weight to the bug report.

@SolarCol my Multi RS built-in MPPT has been throwing a similar strop since V1.30 — Victron's changelog reads like poetry but apparently nobody tested whether DVCC actually talks to the integrated controller properly before shipping it. 🙄

Worth checking your VRM portal logs around the timestamp the CCL kicks in — I spotted mine was treating the built-in MPPT as an entirely separate device from the Multi RS itself, like it had forgotten they're literally the same box.

Raised it on the Victron Community forum and got tumbleweeds, naturally.

@SolarCol this one rings a bell — saw similar behaviour crop up on my motorhome rig after a GX firmware jump a while back.

The core problem here is that the Multi RS's internal MPPT is a fundamentally different communication path to an externally networked SmartSolar. When DVCC calculates its CCL budget, it's historically struggled to properly account for both simultaneously — the internal MPPT essentially gets treated as a "free" source outside the VE.Can hierarchy.

Worth checking in VRM whether the built-in MPPT is even appearing as a separate managed device post-update, or whether it's being swallowed by the Multi RS inverter entry. That distinction matters enormously for how DVCC distributes current headroom.

@BoatEwan — when you say "applying correctly," do you mean the CCL is being respected or being ignored? Those are opposite problems and the thread is ambiguous right now.

Sounds like the Multi RS's built-in MPPT has decided it's above the law now that V1.30 gave it a taste of freedom. Classic teenager behaviour — ignore the house rules, do what you like.

Worth checking whether the CCL is actually being broadcast correctly on the VE.Can bus. On my garden office setup I had a situation where the G

@BoxerProject ha, "above the law" — mine's basically become a feral teenager since the update. Does what it likes, when it likes.

Serious note though: I've replicated this on my cabin rig. The SmartSolar 250/100 obeys the DVCC CCL like a good lad, but the Multi RS's built-in MPPT completely ignores it post-V1.30. Watching the BMS scream at a charge current it should never be seeing is not a relaxing afternoon.

Worth checking your VRM diagnostics — look at DVCC System → Max Charge Current vs what the built-in MPPT is actually reporting. The delta tells the story pretty clearly.

Raised a ticket with Victron support. Their response time has been... optimistic shall we say. If you haven't already, flag it on the Victron Community forum directly — the devs do occasionally surface there.