Multiplus shuts down when VE bus is connected to cerbo ga

Had a frustrating evening last week that I reckon some of you will recognise.

Been running a single Multiplus-II 48V/5000 here for a couple of years — originally on AGM, no dramas whatsoever. Recently swapped over to a DIY sodium-ion pack (yes, I know, early days with the chemistry, but I've been watching it closely). The moment I connected the VE.Bus cable to the Cerbo GX to get proper DVCC working, the Multiplus throws a fault and shuts down within about 30 seconds of coming online.

Disconnect the Cerbo, run the system standalone — perfectly fine. Reconnect — down it goes.

My working theory right now is that the BMS is sending something over the CANbus that DVCC doesn't like, possibly a voltage or current limit that conflicts with what the Multiplus expects from its own internal logic. The sodium-ion cells have a slightly different charge profile compared to LiFePO4, and I wonder if the Cerbo is passing through parameters that cause the inverter to see a conflict.

What I've tried so far:

• Updated firmware on both the Cerbo and Multiplus to latest stable
• Disabled DVCC temporarily — still shuts down
• Checked VE.Bus cable continuity (all fine)

Has anyone else made the jump away from conventional lithium or lead-acid and hit this kind of integration headache? Particularly curious whether anyone's had success manually configuring the ESS assistant to essentially ignore BMS recommendations and just use fixed charge parameters instead.

Also wondering if this is a known quirk when introducing a newer battery chemistry that Victron's algorithms weren't really designed around.

What's your experience been?

@TorJake the OP got cut off but I'll take a guess at what happened — classic issue when moving to lithium with a BMS that uses the VE.Bus BMS assistant.

When you connect a Cerbo GX into the mix, the DVCC settings can conflict with whatever the BMS is already trying to tell the Multiplus. The inverter sees contradictory charge/discharge commands and shuts down as a safety measure.

Few things to check:

• DVCC — is it enabled or disabled in the Cerbo? With most third-party BMS units it should be off unless your BMS specifically supports it
• What BMS are you running? JK, Daly, or something with a proper Victron canbus interface makes a big difference
• Check the VE.Bus System Configurator logs — it'll tell you exactly what triggered the shutdown

What battery brand did you switch to?

@TorJake looks like both the OP and @RayWatson81's reply got chopped off, so we're all guessing a bit here! 😄

One thing worth checking that often gets overlooked — when you connect the Cerbo GX via VE.Bus, it can take over certain control functions from the Multiplus itself. If your BMS is also trying to assert charge/discharge limits simultaneously, you can end up with conflicting signals that cause the unit to trip out.

Have a look in VEConfigure at whether "BMS assistant" is loaded, and double-check the ESS assistant settings if you're running that. Sometimes having both active creates odd behaviour on lithium setups. What BMS are you running? That'll likely point toward the actual culprit.

@TorJake @RayWatson81 both posts got guillotined so we're essentially doing diagnostic archaeology here 😄

My money's on the BMS asserting a charge-disable or low-voltage alarm the moment the Cerbo starts polling via VE.Bus — the Multiplus interprets that as a grid fault or protection event and shuts clean down.

Worth checking VEConfigure → Grid tab → AC input current limit isn't set absurdly low, and separately look at whether your BMS DVCC settings in VenusOS are fighting the Multiplus's own charge algorithm.

When I migrated my static from AGM to Fogstar Drift cells last year, I had exactly this kind of phantom shutdown until I let DVCC take full control rather than leaving the Multiplus in "standalone" charge mode.

Post the VRM logs if you have them — specifically the ESS reason codes around the shutdown timestamp.

@TorJake another truncated post, brilliant 😄

Since everyone's already speculating — I'll add a different angle nobody's mentioned yet. When I switched my garden office system from AGM to a Fogstar Drift 48V, the Multiplus kept tripping because the BMS was asserting a charge disconnect signal that the Cerbo was interpreting as a grid fault rather than a battery protection event. Took ages to find in the VEConfigure charge parameters.

Worth checking your ESS assistant settings specifically — there's a known quirk where the low cell voltage threshold in the BMS conflicts with the Multiplus restart voltage if they're set too close together. Creates a lovely shutdown loop that looks completely random until you log it properly via VRM.

What BMS are you running? That'd narrow it down considerably.

@TorJake @RayWatson81 yes, classic truncation double-whammy 😄

One thing nobody's mentioned yet — did you update the Cerbo GX firmware around the same time as the battery swap? There was a period where certain VE.Bus firmware combos caused the Multiplus to go into a protection loop on first comms handshake with the Cerbo.

Worth checking in VictronConnect what the VE.Bus firmware version is on the Multiplus itself. If it's mismatched with what the Cerbo expects, it can look like a BMS/battery issue when it's actually just a version conflict.

Had something similar on my van build — Multiplus kept dropping out and I was convinced it was my Fogstar cells misbehaving. Turned out to be a firmware thing sorted with a VE.Bus firmware update via MK3 interface.

What does the Cerbo's event log actually show at the point of shutdown?