Victron MultiPlus Not Charging — Charge Parameter, BMS & DVCC Diagnosis
Your Victron MultiPlus or MultiPlus-II has stopped charging the battery. The inverter-charger appears to be running but the battery state of charge is falling or stuck. This is the single most common Victron support question — and it usually has a configuration answer, not a hardware one. This guide covers every common cause.
We review the VRM alarm log, VEConfigure parameters, DVCC status, and BMS communication to identify why your MultiPlus has stopped charging — and fix it remotely.
Book Remote Diagnostic — from £75 → Back to Victron hubIndependent — not affiliated with Victron Energy.
⚡ Safety Warning
Do not open your inverter or interfere with DC cabling. Solar panels produce live DC voltage whenever exposed to light. Always use your DC isolator switch and contact a qualified solar engineer for hands-on fault diagnosis.
Before you start: You need access to VRM (vrm.victronenergy.com) or VictronConnect (Bluetooth app). If you have neither, we can access VRM remotely during a diagnostic session — you just need to share VRM access or provide your installation ID.
5-step MultiPlus charging fault diagnosis
MultiPlus charging faults are almost always configuration — not hardware. The charger section, AC input limit, DVCC settings, and BMS communication all interact. Work through these steps in order to isolate the cause.
Check the MultiPlus charging state in VRM or VictronConnect
Open VRM or connect via VictronConnect over Bluetooth. The MultiPlus device page shows the current charger state:
Also note the AC input power reading. If it shows 0W AC input, the MultiPlus is not receiving grid or generator power — that's a different problem (AC wiring, breaker, or grid relay fault).
Verify the charge voltage and current parameters in VEConfigure
VEConfigure controls the MultiPlus charger settings. The values must match your battery manufacturer's specifications exactly:
The most common mistake: float voltage set too high, so the MultiPlus never enters bulk mode because it thinks the battery is already charged. Or absorption set too low, so the battery never reaches full charge.
Remote VEConfigure access requires a Cerbo GX with internet and VRM two-way communication enabled. Without this, a VE.Bus to USB adapter and physical access are needed.
Check the AC input current limit setting
The MultiPlus limits how much current it draws from AC input (grid or generator). If this is set too low, all available power goes to AC loads — leaving nothing for charging:
The AC input current limit can be set in VEConfigure, VictronConnect, or on the VRM remote console under the MultiPlus device settings.
Check DVCC settings and battery BMS communication
If your system has a Cerbo GX with DVCC (Distributed Voltage and Current Control) enabled, the BMS controls the MultiPlus charge behaviour dynamically. This is the most common hidden cause of charging failures:
Common BMS lockout triggers: low temperature (LiFePO4 batteries typically refuse charge below 0°C–5°C), cell overvoltage (one cell above safe limit), and communication timeout (BMS lost contact with GX device via CAN bus).
If BMS communication has dropped, check the CAN bus cable between battery and Cerbo GX. See our battery BMS disconnect guide for detailed CAN bus troubleshooting.
Check for VE.Bus error lockout or firmware mismatch
VE.Bus errors can lock the MultiPlus into a fault state where it refuses to charge until the error is manually cleared:
Firmware mismatch: If your system has multiple MultiPlus units (parallel or three-phase), all must run the same firmware version. A mismatch after a partial update is a common cause of VE.Bus communication errors. Update the GX device first, then all MultiPlus units together.
See our VE.Bus error codes guide for the full error code reference.
Why MultiPlus charging faults are almost always configuration
The Victron MultiPlus is an inverter-charger — it combines a mains inverter, a battery charger, and a transfer switch in one unit. Unlike simpler hybrid inverters that handle everything internally, the MultiPlus charger behaviour is controlled by a layered stack of settings: VEConfigure parameters, ESS assistant rules, DVCC limits from the BMS, and AC input current restrictions. When any one layer sends a conflicting signal — the charger stops. The hardware is almost always fine. The challenge is finding which layer is blocking the charge.
This is especially common in third-party battery integrations. Victron publishes compatibility lists and recommended settings for batteries like Pylontech, BYD, and Dyness, but installers frequently use slightly different parameters or forget to enable DVCC. Over time, firmware updates on either the Victron or battery side can change the BMS communication protocol, causing a previously-working system to stop charging. We see this pattern weekly — a system that worked fine for months suddenly stops after a firmware update or a seasonal temperature drop triggers the BMS low-temperature lockout.
MultiPlus charging faults — common questions
The most common causes are incorrect charge parameters in VEConfigure (wrong absorption or float voltage for your battery type), an AC input current limit set too low (leaving no headroom for charging after AC loads), a BMS lockout via DVCC where the battery management system has set the charge current limit to zero, or a VE.Bus error that has put the MultiPlus into a fault state.
For a standard 48V LiFePO4 bank, typical settings are absorption 53.2V–54.0V and float 52.0V–53.2V — but you must use the exact values from your battery manufacturer. Pylontech, BYD, and Dyness each have different recommended settings. Temperature compensation must be disabled for lithium. If DVCC is enabled, the BMS overrides these values dynamically.
If your system has a Cerbo GX with DVCC enabled, open VRM and check Settings then DVCC. Look at the CCL (Charge Current Limit) being sent by the BMS. If CCL is zero, the BMS is actively blocking charging — usually due to low temperature protection, cell overvoltage, or a CAN bus communication timeout. Also check the battery device page in VRM for alarm flags.
Sometimes. If paralleled units run different firmware versions, or if the GX device firmware is incompatible with the MultiPlus firmware, updating everything can resolve the fault. Update the GX device first, then all MultiPlus units. Never update during a fault condition. If the cause is incorrect parameters or a BMS lockout, firmware alone won't fix it.
Our remote diagnostic starts from £75 and covers the full VRM alarm history, VEConfigure parameter review, DVCC and BMS communication audit, and VE.Bus error analysis. Most MultiPlus charging faults are configuration issues that we resolve remotely. If physical work is needed, we provide a clear scope and quote before booking.
MultiPlus not charging your battery?
Tell us your MultiPlus model, battery brand, and what VRM or VictronConnect is showing. We'll review the VEConfigure parameters, DVCC status, and alarm history to identify the cause.