Configure Multiplus II 24/5000/120-50 for Lynx Smart BMS NG 500 and two LFP25,6/200

Been scratching my head over a similar setup in my shepherd's hut build and wondered if anyone here had gone through the same process.

Running a Multiplus II 24/3000 with a Lynx Smart BMS and a pair of 200Ah LFP batteries, and I'm trying to nail down the VE Configure settings so everything plays nicely together. The BMS-to-Multiplus communication is what's tripping me up — specifically around:

• Charge current limits — does the Lynx Smart BMS NG actually push those limits dynamically to the Multiplus via the Cerbo, or do you still need to hard-set them in VE Configure?
• Low battery shutdown — I want the BMS to have final say, but I'm unsure whether to also set cutoff voltages in VE Configure as a belt-and-braces backup, or if that creates conflicts
• ESS vs non-ESS — for a pure off-grid shepherd's hut with no grid connection, I'm assuming ESS assistant isn't the right route, but worth confirming

The Cerbo GX is obviously the hub tying it all together, and I think the DVCC settings in Venus OS are key here, but the documentation jumps around quite a bit between the BMS manual and the Multiplus docs.

Has anyone configured this sort of Victron ecosystem from scratch for a fully off-grid site? Particularly curious whether the Lynx Smart BMS NG handles everything autonomously once DVCC is set up correctly, or whether you still need to babysit the VE Configure charge profile.

Any pitfalls to flag before I start poking around with settings would be brilliant.

@TQ_Builds interesting one — I went through something similar when I wired up my static caravan setup, though I was using the older Lynx BMS rather than the NG variant.

Few things worth checking that caught me out:

• The DVCC settings in VEConfig are critical — make sure SVS and STS are both enabled, otherwise the Multiplus ignores the BMS voltage/temp data entirely
• Your charge current limit needs to come from the BMS to the Multiplus via VE.Can, not manually set in the inverter — easy to double-configure and cause conflicts
• With two LFP25.6/200 packs in parallel, confirm the BMS is seeing combined capacity correctly (400Ah) otherwise your SoC calculations go sideways

The NG variant apparently handles balancing data differently through VE.Can — worth checking Victron's CCGX compatibility matrix for the specific firmware version pairing.

What's your current DVCC configuration showing?

Wait — you said you're running a Multiplus II 24/3000 but the thread title says 24/5000. Which is it? Pedant mode activated, sorry 😅

Assuming it's the 5000: with the Lynx Smart BMS NG you'll want to set up the DVCC properly in V

@CotswoldNomad good catch — worth clarifying before anyone goes down the wrong rabbit hole with settings.

@TQ_Builds assuming you are on the 5000 variant, the key thing with the Lynx Smart BMS NG is making sure VE.Can is properly configured between it and the Multiplus II. DVCC needs to be enabled in VictronConnect/VEConfigure and the BMS set as the charge current controller — otherwise the Multiplus won't respect the BMS charge/discharge limits.

For two 25.6/200 batteries in parallel that's 400Ah at 24V. Set your system battery capacity accordingly in VEConfigure and double-check the charge voltage ceiling matches what Victron publish for those specific cells — don't just leave it at default.

Had a similar headache on my static caravan build before I realised DVCC was the missing piece.

Good spot @CotswoldNomad and @DailyBuild — definitely worth sorting that out before we dig into specifics, as the charge current limits and assistant configurations will differ between the 3000 and 5000 models.

@TQ_Builds while you clarify, it'd also help to know whether your two LFP25,6/200 batteries are wired in series or parallel. With a 24V system and 200Ah cells, I'd assume series to get your 25.6V nominal, but worth confirming. The Lynx Smart BMS NG 500 should handle DVCC comms to the Multiplus nicely via VE.Can, but getting your battery capacity figure correct in VictronConnect matters for the SOC calculations to behave properly.

Also — are you on the latest firmware across everything? There were some meaningful improvements to the BMS NG communication stack fairly recently that are worth having before you start tweaking settings.