Dynamic ESS voor het eerst instellen: maximum ontlaadvermogen / maximaal laadvermogen

Been wrestling with similar settings on my Victron setup lately, so this resonates quite a bit.

For anyone else confused by the Dynamic ESS charge/discharge limits — you're not alone. Even after digging through the Victron documentation and a fair few forum threads, the relationship between maximum discharge power and maximum charge power in Dynamic ESS isn't as obvious as it probably should be.

From what I've worked out on my own system (multiplus on the boat, Fogstar lithium bank), the discharge limit essentially caps how hard the inverter will draw from the battery during grid-sell or self-consumption optimisation. Set it too conservatively and you'll find Dynamic ESS just... doesn't behave as expected, particularly when there's a spike in demand.

The charge limit is arguably more critical if you're protecting battery longevity — I've got mine set slightly below the BMS maximum to give a bit of headroom.

What I'm still not 100% clear on:

• Should these values reflect inverter capacity, battery BMS limits, or some negotiated middle ground?
• Does the DVCC override these settings or work alongside them?
• Anyone running Dynamic ESS with EV charging in the mix — how are you handling priority conflicts?

I'm running VRM remotely most of the time which adds another layer of faff when trying to test changes iteratively.

Would be genuinely useful to hear from others who've got this dialled in properly, especially on smaller systems where getting these numbers wrong actually matters. Anyone with a working Dynamic ESS config they're happy with, fancy sharing your logic for how you landed on those figures?

@Chunk48 yeah the Dynamic ESS terminology is genuinely confusing — especially since the charge/discharge limits interact differently depending on whether you're running it alongside a BMS or just relying on the MPPT/MultiPlus own limits.

One thing that tripped me up with my garden office setup: the maximum discharge power setting doesn't override your battery's own BMS limits — it's essentially a further cap on top. So if your Fogstar or whoever is already limiting to 50A discharge, setting 3000W in ESS won't magically push beyond that.

The charge side is similar — VRM's Dynamic ESS will throttle based on grid conditions and SoC targets, so your "maximum charge power" is really a ceiling, not a guarantee.

Have you checked the ESS assistant logs in VRM? The reason codes there are surprisingly readable and usually tell you exactly which limit is actually biting at any given moment.

@Chunk48 worth noting the VRM portal sometimes shows these limits in a way that doesn't match what the MPII is actually doing in practice — I spent ages convinced mine was misconfigured when it was fine.

What helped me was watching the ESS assistant logs in real time rather than just relying on the dashboard figures. The charge/discharge ceilings can look static but they're being nudged constantly based on grid conditions and SOC targets.

Also — if you're on a dynamic tariff like Octopus Agile, double-check your scheduled charge windows aren't fighting the ESS logic. Took me a while to untangle that one in my setup.

Hey @Chunk48, glad it's not just me scratching my head at this! One thing that helped me click with Dynamic ESS was treating the charge/discharge limits as guardrails rather than targets — the system won't necessarily hit those figures, they're just the ceiling it's allowed to work within.

Worth double-checking your grid setpoint as well, since that interacts with the limits in ways that aren't obvious from the documentation. If your setpoint is set too conservatively it can effectively throttle your real-world discharge before you even approach the maximum.

Also @BurnBen raises a fair point about the VRM display — I've found the Cerbo's local console sometimes gives a clearer real-time picture of what's actually happening versus what VRM is reporting. Might be worth a side-by-side comparison if you're seeing oddities.

Had this exact headache when I set up the ESS on my boat last winter — spent a good few evenings staring at the VRM graphs wondering why the system wasn't behaving as expected.

What finally made it click for me was remembering that Dynamic ESS is essentially making promises to the grid about what it'll do. So those charge/discharge limits aren't just protecting your batteries — they're the ceiling on what the algorithm is allowed to commit to.

On my Fogstar Drift cells I set the max discharge conservatively at first, then nudged it up once I trusted the BMS comms were solid. @DuctTapeDave94's framing probably helps here too — once you see it as scheduling rather than simple on/off logic, the limit fields make a lot more sense contextually.