Victron Battery BMS Disconnect — DVCC, CAN Bus & Third-Party Lithium Diagnosis
Your Victron system has stopped charging or discharging the battery — the BMS has disconnected or triggered a protection. In systems using third-party lithium batteries (Pylontech, BYD, Dyness), the BMS communicates with Victron via DVCC and CAN bus. When that communication breaks down, or the BMS triggers a protection, the entire system goes into a safe-but-idle state.
We review VRM alarm history, check DVCC charge and discharge limits, analyse CAN bus communication status, and identify whether the disconnect is a cable fault, temperature protection, or cell imbalance.
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.
How Victron talks to third-party batteries. Victron uses DVCC (Distributed Voltage and Current Control) to let the battery BMS control charge and discharge limits. The BMS sends three values over CAN bus: CVL (Charge Voltage Limit), CCL (Charge Current Limit), and DCL (Discharge Current Limit). The MultiPlus, Quattro, and MPPT controllers all obey these limits. When the BMS sets CCL and DCL to zero, the system stops all charging and discharging — this is what a "BMS disconnect" looks like in practice.
5-step BMS disconnect diagnosis
A BMS disconnect on a Victron system usually means the battery is protecting itself — or the communication link between the BMS and the GX device has failed. Either way, the system goes idle. Work through these steps to find the cause.
Check DVCC status and battery communication on the Cerbo GX
Start at the GX device — this is where you can see what the BMS is telling the Victron system:
If the battery is missing from the device list, skip to step 2. If it appears but shows zero limits, skip to step 3 or 4 depending on whether temperature or SoC is the suspected cause.
Inspect the CAN bus or serial cable between the BMS and GX device
The CAN bus cable is the sole communication link between the battery BMS and the Victron system. A loose or damaged cable causes a complete communication failure:
After checking the cable, restart both the battery BMS (typically by toggling the breaker or button on the master battery) and the Cerbo GX. CAN bus re-negotiation requires both devices to restart.
Check for low-temperature charge protection on the BMS
LiFePO4 batteries must not be charged below a minimum temperature — the BMS enforces this by setting CCL to zero via DVCC:
Check the battery temperature on the Cerbo GX battery device page. If it's at or near the threshold, this is the cause. The system resumes charging automatically when the cells warm up. Discharge usually continues at reduced rates — most LiFePO4 batteries can discharge down to -10°C or -20°C.
UK garages, lofts, and outbuildings regularly hit sub-zero temperatures in winter. Battery heating mats or relocating the battery to a heated space are the permanent solutions.
Investigate cell imbalance and SoC calibration drift
If the BMS disconnects at a specific charge level rather than due to temperature, cell imbalance is the likely cause:
Cell imbalance builds up over months. It's more common in systems that rarely reach 100% SoC — the BMS doesn't get the chance to balance.
Verify DVCC charge parameters and firmware compatibility
Even with a healthy battery, incorrect DVCC settings or outdated firmware can cause charging to stop:
See our MultiPlus charging guide for related charge parameter diagnosis including AC input limits and PowerAssist interaction.
Why third-party batteries cause more disconnects than Victron's own
Victron's own lithium batteries (Smart Lithium range) use VE.Bus BMS, which is deeply integrated into the Victron ecosystem. When a Victron battery triggers a protection, the system handles it natively — the MultiPlus transitions to a reduced-power mode rather than shutting down completely. Third-party batteries communicate via CAN bus, which is inherently a looser integration. The BMS sends limit values (CVL, CCL, DCL) and the Victron system obeys them, but there's no graceful degradation — when the BMS says stop, everything stops.
This is not a design flaw — it's a deliberate safety choice. Third-party BMS manufacturers have different protection philosophies, different cell chemistries, and different threshold settings. Victron cannot predict every scenario, so DVCC takes the conservative approach: if the BMS says zero, the system does zero. The practical result is that Victron systems with third-party batteries are more sensitive to cable issues, temperature, and cell imbalance than equivalent systems from manufacturers who control the entire stack. The trade-off is that Victron's open architecture gives you the freedom to choose your battery — you just need to ensure the communication layer is reliable.
Battery BMS disconnect — common questions
The battery BMS sets the DVCC Charge Current Limit to zero when cell temperature drops below the safe charging threshold — typically 0–5°C for LiFePO4. This prevents lithium plating damage. The system resumes automatically once the cells warm up. Discharge usually continues at reduced rates. If your battery is in an unheated space, UK winters will trigger this regularly. Battery heating mats or relocating to a warmer room are the permanent fixes.
DVCC — Distributed Voltage and Current Control — lets the battery BMS control the Victron inverter-charger and MPPT controllers. When enabled on the Cerbo GX, the BMS sends three values via CAN bus: Charge Voltage Limit (CVL), Charge Current Limit (CCL), and Discharge Current Limit (DCL). The Victron equipment adjusts to stay within these limits. Without DVCC, the system uses fixed charge settings that may not match the battery's requirements.
Reduce the charge current to 0.2C or lower via VEConfigure or DVCC settings. Charge the pack fully — Pylontech only balances at the top of charge, so the pack must reach near 100% SoC. Hold at absorption voltage for at least 2 hours, then repeat for 3–5 cycles. Monitor individual cell voltages via the Pylontech console port — balanced cells should be within 20mV of each other.
Yes — the CAN bus cable is the sole communication link. If it's loose, damaged, or the wrong type, the GX device loses contact with the BMS and DVCC defaults to zero charge and zero discharge current. This is the most common cause of sudden BMS disconnects where the battery itself shows no faults on its own display. Replace with the manufacturer-specified cable and verify connections at both ends.
Our remote diagnostic starts from £75 and covers VRM data review, DVCC configuration audit, CAN bus communication status, charge and discharge limit history, cell voltage analysis where available, and firmware compatibility check. Most BMS disconnect faults are caused by cable issues, low-temperature protection, or incorrect DVCC settings that we can identify remotely.
Still getting BMS disconnects?
We check your DVCC settings, CAN bus communication, battery temperature, and cell balance data to identify whether it's a cable, firmware, temperature, or cell fault.
Request received
We'll review your system details and get back to you within one working day.