Multiple Battery Info on DVCC

Got me thinking about this after fiddling with my Victron setup at the cabin last weekend — when you've got multiple batteries in a bank, the Remote Console is a bit like that one mate who only tells you half the story.

Mine shows total capacity and quantity fine, but the voltage and temperature readings feel suspiciously like they're just parroting one battery rather than giving me a true picture across the whole bank. Bit sketchy when you've got Fogstar Drift cells that could each be doing their own thing.

A few questions worth thrashing out:

• Is DVCC actually averaging across your batteries, or is it just pulling from the "loudest" BMS on the VE.Can network?
• Anyone managed to get per-battery breakdowns visible on the dashboard without resorting to third-party integrations or Node-RED witchcraft?
• Does it actually matter in practice, or am I just going full nerd over something the BMS handles quietly in the background?

The cynic in me suspects Victron's dashboard was designed for a nice tidy single-battery setup and the multi-bank reality is a bit of an afterthought — happy to be proven wrong though, because I'd love a proper SOC per unit rather than one number that's basically vibes.

Anyone with a parallel Lithium setup on a static caravan or similar seen this behave differently? Curious whether it's a firmware version thing or just how DVCC fundamentally works. Reckon there's a rabbit hole here worth jumping down together.

@DailyWanderer yeah DVCC with mixed battery info is a bit of a rabbit hole innit. The Remote Console just aggregates everything so you lose visibility of individual cells pretty fast.

What I've found useful is getting each battery's BMS talking to the Cerbo via separate VE.Can or USB adapters if they support it — my Fogstar Drift cells actually show up individually in VRM that way which is dead handy for spotting a weak one.

Otherwise you're flying blind and just hoping the weakest cell doesn't drag the whole bank down without you noticing.

Worth checking if your BMS supports Victron comms properly before assuming DVCC is actually doing what you think it is 👍

@DailyWanderer had exactly this headache building my van conversion. Running two Fogstar Drift 100Ah batteries and the Remote Console was showing me one blended SOC figure that was essentially useless when the cells weren't balanced.

The bit nobody warns you about — if your batteries have separate BMS units talking over VE.Can, Victron's DVCC will prioritise whichever BMS screams loudest about charge limits. Had one battery throttling the whole bank because it ran slightly warmer in summer.

What actually sorted it for me was using Victron's battery monitor aggregation properly rather than relying on individual BMS broadcasts. Still not perfect, but at least the Multi stopped making weird decisions at 3am.

Anyone running more than two banks with separate BMS units — I'd genuinely want to know how you're keeping tabs on individual battery health without buying another GX device.

@DailyWanderer this is something I've been digging into for my static caravan setup. Worth knowing that DVCC pulls state-of-charge data from whichever battery is communicating via the VE.Bus or CAN — if only one battery has a BMS talking to the Cerbo, that's the only one being "listened to."

Few questions that might help narrow it down:

• Are your batteries wired in parallel or series?
• How many of them have active BMS-to-Cerbo comms (VE.Can, USB, Bluetooth)?
• Are you using a shared current sensor or individual ones?

In my experience, the aggregated SOC figure in Remote Console is only as reliable as the data feeding it. If one BMS is silent, Victron is essentially guessing on that unit's behalf. Proper BMS communication from every battery in the bank is the only clean solution.

@DailyWanderer my garden office setup taught me the hard way that the Remote Console showing one SOC figure for your whole bank is basically just the Victron's best guess dressed up in a suit — individual cell-level drama stays firmly behind the BMS curtain unless you've got something like a Cerbo GX pulling proper data through.