Quattro 48/15000/200 2 x 100 #24system protection initiated

Been going through something similar with my van build scaled up to a static cabin setup — swapped out an older inverter/charger for a Victron Quattro and it's been a bit of a learning curve tbh.

Anyone else had #24 system protection initiated pop up when running a larger Quattro alongside external solar kit? I'm wondering if it's a comms/coordination issue between the BMS and the Quattro rather than anything genuinely wrong with the cells.

My setup:

• Quattro 48/5000 (smaller than OP's but same family)
• Fogstar Drift 48V battery
• Victron MPPT 150/45
• VE.Bus SmartDongle for monitoring

The Fogstar BMS talks to the Quattro fine under normal load, but I'm getting occasional protection trips when solar input is high and load demand drops suddenly. Feels like the inverter isn't backing off fast enough before the BMS gets twitchy.

Had a mate who ran a Sunny Boy alongside his Quattro and ended up pulling the SB entirely — frequency shifting worked in theory but in practice it caused more headaches than it solved. Sounds like OP landed in the same place.

Is anyone running a clean Victron-only stack and seeing rock-solid stability? Genuinely curious whether mixing brands on the AC-coupled side is asking for grief, or whether it's purely a configuration/ESS assistant issue.

Worth checking your DVCC settings too if you're on a Cerbo — had mine configured wrong for weeks before I spotted it in VictronConnect.

What firmware version is everyone on? Might be relevant here.

@ThingamyBob62 that error's usually the Quattro hitting its system protection limits — often down to DC ripple or the BMS and Quattro not talking properly via VE.Bus.

Few things worth checking:

• DVCC enabled in VenusOS? If your BMS supports it, let it control charge current properly
• Battery cable sizing — undersized cables cause voltage sag under load which can trigger protection
• What BMS are you running? Some cheaper units send dodgy signals that confuse the Quattro
• Check your AC input voltage too, if it's drooping the Quattro can get twitchy

I had similar grief when I first paired mine with a Fogstar Drift pack — turned out DVCC wasn't configured right and the Quattro was essentially fighting the BMS for control. Sorted once I set charge current limits properly in VictronConnect.

What does VRM show for the exact fault timestamp?

@MarineGaz is on the right track but don't overlook your battery cable lengths and cross-sectional area — had the exact same grief on my shepherd's hut build until I realised my 35mm² runs were about 40cm too long each side and the voltage drop was triggering protection before the Fogstar cells even broke a sweat. Quattro 15kVA wants fat cables and short runs, full stop. Check your VictronConnect DC ripple graph — if it looks like a rollercoaster at Alton Towers you've found your culprit. What BMS are you running?

@ThingamyBob62 had this exact gremlin on my cabin setup — turned out the #24 protection was being triggered by a BMS communication dropout over VE.Can, Quattro panicked and shut the party down before anyone got hurt.

Check your VE.Can termination resistors (120Ω at both ends, no exceptions) and make sure your BMS is actually speaking the right DVCC dialect in VEConfig — Fogstar Drift cells with a compatible BMS sorted mine overnight once I stopped ignoring the CCGX warnings I'd been dismissing for a fortnight like an idiot.

Also worth logging via VRM portal during the fault — the pre-alarm data is gold for pinpointing whether it's a voltage sag, ripple issue, or comms fault before you start swapping hardware randomly.

Really interesting thread — been watching this one closely as I run a Quattro on my motorhome and keep it as emergency backup at home too.

@FogstarFan's point about BMS comms is worth digging into further. Worth checking in VictronConnect or VEConfig whether your DVCC settings are actually configured correctly for your specific BMS protocol. A lot of people import a config file and assume it's right, but the #24 protection can fire if the Quattro thinks it's receiving conflicting charge current instructions.

Quick questions that might help diagnose:

• What BMS are you running?
• Are you on the latest firmware (Quattro 500+ series)?
• Any ESS assistant installed?

Also — did this start happening after a firmware update? That caught me out once. Sometimes rolling back one version on the Quattro sorts it whilst Victron push a fix.

@ThingamyBob62 this brings back memories of when I first commissioned my garden office setup — spent a whole weekend chasing #24 faults before realising the Quattro was essentially having a conversation with my Fogstar Drift LiFePO4 pack that neither party fully understood.

The bit nobody mentions: assistant charge current matters as much as the main charge current. My BMS was quite happy with the bulk charge but the absorption phase was causing brief overcurrent spikes that the Quattro logged as system protection events.

Dropped the absorption voltage by about 0.1V and throttled the charge current in VictronConnect — problem vanished completely and the pack has been settled ever since.

Worth checking your ESS or charger profile settings before pulling cables apart. Sometimes it's a conversation issue, not a hardware one.