Skip to content
07944 877 329 hello@solar-tech-support.co.uk
Alectrona Get a quote
Problem diagnosis · Victron Energy

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.
Free remote diagnostic £125 only if we fix it remotely
Start diagnosis
  • DVCC & CAN bus diagnosis
  • Pylontech, BYD & Dyness
  • Low-temp & cell imbalance
Battery BMS cutting power to your Victron system?

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 your free remote diagnosticBack to Victron hub

Independent — not affiliated with Victron Energy.

5.0
Rated 5.0 on Google Read all 151 reviews

I contacted Solar Tech Support because I had a problem with my legacy GiveEnergy installation. within 24 hours they had diagnosed the problem and offered advice on resolution. Because they were unable to fix the problem there was no charge! This despite numerous time consuming emails. I am currently trying to engage with the original installer but if that is unsuccessful I will go back to Solar Tech Support and ask them to repair the system with a retrofit. Very knowledgeable and responsive. I highly recommend them.

Tim Hatt · Aug 2026 Google

Very very helpfuland so quick. Made sure that a non expert like myself understood what the problem was and how to resolve it.

Declan S · Jun 2026 Trustpilot

My issue was assessed and resolved quickly once the engineer was able to look at the problem. This took a little longer than I had expected (3 days) and keeping the PC on all day/everyday with Sentinel open was a little cumbersome I thought. That said, with little support coming from GivEnergy nowadays it was good to find someone who knew the platform and could resolve my issue.

Terry Hanney · Oct 2026 Google

My 90-year-old father-in-law had a solar system installed nearly three years ago that never worked properly and kept tripping out. Neither the original installer nor GivEnergy could resolve the issues, and we were even pushed towards replacing the system entirely when GivEnergy went bust. I contacted Ron at Solar Tech Support via WhatsApp, and within a few hours he had diagnosed multiple faults — including incorrect wiring that posed a potential fire risk. He carried out a home visit in Nottingham for £295 (including parts), fixed everything, completed firmware updates, and ensured the system was fully operational. Since then, it has worked perfectly. Ron was knowledgeable, responsive, and took the time to explain everything clearly. Highly recommended — excellent value and complete peace of mind.

Julian Federici · Jun 2026 Google

Ron is a super star. Two months ago my GivEnergy battery failed a firmware upgrade leaving it a brick. My installer couldn't/wouldn't fix it. GivEnergy couldn't/wouldn't fix it. Then they went into administration and all hope was lost. A flurry of emails later and Ron had diagnosed the fault (failed USB flash drive, something I'd suspected) and talked me through resolving it. Two months of nothing resolved in about 3 hours. It's great to work with someone who pays attention to the details, knows that they're doing (not just following a script) and gets stuff sorted without a fuss or up-charging.

Christopher · Apr 2026 Trustpilot

I left an enquiry few days ago and got a call back today from Ron. I have FoxESS battery and inverter that seemed not doing the right job and after only few questions, Ron told me exactly what I need to do to restart my system, without even seeing it. After almost 2 weeks of not being able to use my FoxESS equipment, today is finally up and running. Very professional and knowledgeable. Thanks Ron

Micky Mihaela · Aug 2026 Google

Written by · Independent Solar Engineer Last updated

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.

Diagnostics

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.

1

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:

Key readings to check
DVCC status: Settings → DVCC — must be enabled. If disabled, the Victron system ignores the BMS entirely and uses fixed charge parameters.
Battery in device list: If the battery appears with voltage, SoC, and current readings, CAN communication is working. If missing, the cable or protocol selection has failed.
CVL / CCL / DCL values: Check these under the battery device page. If CCL = 0, the BMS is blocking charge. If DCL = 0, the BMS is blocking discharge. Both at zero means full protection lockout.

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.

2

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:

• Pylontech: Uses an RJ-45 to RJ-45 cable between the battery CAN/Console port and the Cerbo GX VE.Can port. The cable must be a straight-through type — crossover will not work. Pylontech supplies a specific cable; using a generic Ethernet cable may have different pinouts.
• BYD: Uses a dedicated CAN bus cable from the BMS (BMU) to the Cerbo GX VE.Can port. Check the BYD compatibility list — some older BMU hardware revisions require a specific cable adapter.
• Dyness: Typically uses an RJ-45 CAN cable similar to Pylontech. Verify the DIP switch settings on the Dyness master battery match the expected CAN protocol.
• Battery type setting: On the Cerbo GX, navigate to Settings → DVCC → Battery monitor and verify the correct battery brand and model is selected. Selecting the wrong type causes protocol mismatch even with a working cable.

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.

3

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:

Manufacturer charge temperature limits
Pylontech US3000C / US5000: Charge allowed down to 0°C. Below 0°C, CCL drops to zero.
BYD HVS / HVM: Charge allowed down to 0°C. Derates from 5°C.
Dyness Tower: Charge allowed down to 0°C. Derates from 5°C.
Generic LiFePO4: Most allow charge down to 0°C. Some budget cells specify 5°C minimum.

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.

4

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:

• What happens: One cell reaches its overvoltage threshold (typically 3.65V per cell) while the rest of the pack is still below full. The BMS triggers overvoltage protection and sets CVL/CCL to zero — stopping all charging.
• How to check: View individual cell voltages via the battery's own app (Pylontech Console, BYD BeConnect, Dyness Cloud) or via VRM if the BMS reports cell-level data. A difference of more than 50mV between highest and lowest cell confirms significant imbalance.
• How to fix: Reduce charge current to 0.2C or lower. Charge the pack fully — most BMS units only balance cells at the top of charge. Hold at absorption voltage for at least 2 hours. Repeat for 3-5 cycles until cell voltages converge within 20mV.
• SoC drift: If the displayed SoC doesn't match reality (e.g. shows 80% but the BMS trips on overvoltage), the SoC calibration has drifted. A full charge to 100% followed by a rest period allows the BMS to recalibrate.

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.

5

Verify DVCC charge parameters and firmware compatibility

Even with a healthy battery, incorrect DVCC settings or outdated firmware can cause charging to stop:

• CVL setting: On the Cerbo GX under DVCC, check whether a manual Charge Voltage Limit override is set. If it's lower than the battery's recommended full-charge voltage (typically 52.4–53.2V for 48V LiFePO4), the system stops charging prematurely.
• Firmware compatibility: Check the Victron compatibility list for your battery. Pylontech requires Cerbo GX firmware v2.60 or later. BYD requires v2.66 or later for HVS/HVM. Running older firmware causes incorrect DVCC behaviour.
• MultiPlus charge settings: In VEConfigure, the charge voltage and current settings should match or exceed the BMS values — DVCC overrides them downward, but if the VEConfigure values are too low, they become the bottleneck.
• Restart sequence: After any change, restart the battery BMS first, wait 30 seconds, then restart the Cerbo GX. This ensures clean CAN bus re-negotiation.

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.

Related Victron problems
Battery guides across brands
FAQ

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 free remote diagnostic 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.
Book

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.

  • No fix, no fee
  • Pylontech, BYD, Dyness & third-party lithium
  • DVCC configuration included

By submitting you agree to be contacted about your diagnostic request. We don't share your data with 3rd parties.

Call 07944 877 329 Book free diagnostic