Had this exact issue last winter with my Multiplus-II 48/3000. Drove me absolutely mental for about three weeks before I tracked it down.
The culprit in my case was the battery voltage sense wiring — the Multiplus was reading voltage at the inverter terminals rather than at the battery, and under load the voltage drop across my busbars and cables was enough to trigger the warning even though cell-level voltage was perfectly healthy. Classic case of poor sense wire routing.
A few things worth checking in your setup:
- VE.Configure / VEConfigure 3 — what are your actual DC input low thresholds set to? Factory defaults can be surprisingly aggressive for LiFePO4 unless you've profiled it properly
- Are you using a BMV-712 or SmartShunt with the battery sense enabled? If your BMS is also reporting state of charge over VE.Bus, you can sometimes get conflicting signals confusing the system
- Cable voltage drop — do a load test and measure directly at the battery terminals with a decent multimeter whilst the warning is active. If those readings look fine and the DVCC screen in VRM is showing a different number, you've found your problem
Mine was ultimately fixed by running proper remote voltage sense wires directly from the battery positive and negative terminals back to the Multiplus sense inputs, and reconfiguring the DC input low shutdown to something more appropriate for Fogstar Drift cells specifically.
What battery chemistry and BMS are you running? Makes a big difference to where the thresholds need to sit. Also worth pulling the VRM portal logs if you've got a Cerbo — the data is usually all there waiting to tell you exactly what happened.