Guide
|
Victron Energy
September 07, 2026

Victron DVCC Explained, and When Not to Use It

What DVCC actually changes in a Victron system, what each sub-setting does, when it is required, and the charge limit that catches most RV installs.

Victron Cerbo GX MK2 system monitoring hub

DVCC stands for Distributed Voltage and Current Control. Victron's own manual gives the clearest one-line description of what it does: enabling it "changes the GX device from a passive monitor into an active system controller."

That is the whole idea. Without DVCC, every charging device in your system runs its own charge algorithm and none of them know about each other. With DVCC, the GX device coordinates them.

Whether you need it depends almost entirely on what battery you have.

Where the setting lives

On a current GX device: Settings → System Setup → Charge Control.

Older firmware and older documentation show this as Settings → DVCC, so if you are following an out-of-date guide that is the same thing in a different place.

The short answer, by system type

Victron publishes a table of which device runs the charge algorithm in each combination. For an RV, which is an off-grid system rather than a grid-tied one, the useful rows reduce to this:

Your battery DVCC on? What happens
Managed lithium with a CAN-bus BMS Yes The battery instructs every charger. Victron's table labels turning DVCC off here "Don't do this; better enable DVCC."
Ordinary battery, lead-acid or lithium without a CAN-bus BMS Optional The charge algorithm is identical either way. DVCC adds coordination features but does not change who runs the charge curve.

That second row surprises people. With a normal battery in an off-grid system, DVCC on and DVCC off produce exactly the same charge algorithm. Every device stays on its internal curve. What you gain from DVCC is the system-wide current limit and the three sharing features below, not a different charging behaviour.

So if someone tells you to "just turn on DVCC" to fix a charging problem on a standard lithium drop-in battery, that advice is unlikely to do what they think.

What happens with a managed battery

When a battery with a CAN-bus BMS is connected, it sends the GX device three values:

  • Charge Voltage Limit (CVL) — the maximum voltage the battery will currently accept
  • Charge Current Limit (CCL) — the maximum charge current it is asking for
  • Discharge Current Limit (DCL) — the maximum discharge current it will allow

Those are passed to the inverter/chargers, solar chargers and Orion XS DC-DC chargers, which then disable their own charging algorithms and follow the battery's instructions directly.

Two consequences worth knowing:

Your configured charge voltages stop mattering. Victron states it plainly: configuring charge voltages or charge profiles in VEConfigure or VictronConnect is unnecessary and has no effect, because the devices charge using the voltage received over CAN-bus from the battery. People spend hours adjusting settings that are being ignored.

Devices report "Ext. control" instead of a charge stage. That is normal, not a fault. Victron notes that in battery-controlled mode the LEDs continue to show bulk and absorption but never float.

Some batteries send dynamic values that change with cell voltage, state of charge or temperature. Others send fixed values. With either, you generally do not need to wire allow-to-charge and allow-to-discharge connections into a Multi or Quattro's AUX inputs.

One safety behaviour to be aware of: when inverting off-grid, Multis and Quattros shut down if the maximum discharge current is set to zero, and restart automatically when conditions allow.

The sub-settings, one by one

Limit charge current

A user-set ceiling on total system charge current.

This is the setting most often misunderstood, and the detail that matters is what it does not control. Victron is explicit: only Victron inverter/chargers, MPPT solar chargers and Orion XS DC-DC chargers are governed. Anything else is invisible to it. That includes a Skylla-i charger, and it includes your alternator, because the alternator is not connected to the GX device at all.

So on an RV with a DC-DC charger fed by the alternator and a shore charger and solar, the limit governs some of those sources and not others. Whatever is unaccounted for is extra current on top of your limit.

There is a second subtlety about DC loads. Without a DC load monitor, a 50 A limit with 20 A of DC loads running means the battery only receives 30 A. Configure a SmartShunt or BMV-712 as a DC meter and the system compensates: with 25 A of DC load reported, the chargers are set to 75 A so the battery still receives its 50 A.

If a CAN-bus BMS asks for a different current than you configured, the lower of the two applies.

Charge sources are prioritised in this order: MPPT solar chargers first, then Orion XS DC-DC chargers, then inverter/chargers. Solar gets used before shore power, which is what you want.

Limit managed battery charge voltage

Narrow purpose, and Victron cautions against using it for anything else.

It exists because some managed batteries need a reduced charge voltage during initial commissioning to let cells balance in the first weeks. Victron's warning is direct: improper use may prevent cell balancing and lead to severe long-term imbalance.

Leave it alone unless your battery manufacturer specifically tells you to use it.

Shared Voltage Sense (SVS)

The GX device picks the best available battery voltage measurement and shares it, preferring the BMS or a battery monitor, falling back to the VE.Bus system's own reading.

This matters because a charger measures voltage at its own terminals, which after cable voltage drop is not the voltage at the battery. Sharing an accurate measurement makes every charger aim at the right number.

Enabled by default with DVCC. It is force-enabled and unchangeable with a Lynx Smart BMS, and force-disabled for some batteries — check your battery's compatibility page.

Shared Temperature Sense (STS)

Forwards measured battery temperature to all connected chargers, so temperature compensation works from the battery's actual temperature rather than each device's guess.

Sources can be a BMV-702 or 712, a SmartShunt, a Lynx Shunt VE.Can, the GX device's own temperature input, a Multi or Quattro, or an MPPT with a sensor fitted.

Force-disabled for the Lynx Smart BMS and some managed batteries.

Shared Current Sense (SCS)

Shares measured battery current with MPPT solar chargers and Orion XS chargers so they can use tail current to decide when absorption ends, rather than relying on a timer.

Only applies to systems without ESS and without a managed battery, since in those cases charge control is external anyway. Needs MPPT firmware v1.47 or later.

Controlling BMS

For systems with more than one BMS, selects which one DVCC follows.

It also lets you use a BMV or SmartShunt as the battery monitor for state-of-charge tracking while the BMS stays in charge of DVCC, which is often the combination you want.

The multi-inverter trap

If you have more than one Multi or Quattro, read this before assuming the system is coordinated.

Units on the GX device's built-in VE.Bus port are controlled by DVCC, whether single, parallel, split-phase or three-phase. But a second Multi or Quattro connected through an MK3-USB interface is not controlled by DVCC by default and just runs its own configuration.

There is a setting for it, "Managed battery controls all Multis and Quattros," which only appears when an extra unit is connected that way, and it is disabled by default.

Even then, there is a real limitation: the charge current limit is not divided between units. The full value is applied to each one. Two units with a 100 A CCL can therefore attempt 200 A. Victron states it is the installer's responsibility to make sure the limit is not exceeded.

When to leave DVCC off

  • You have an ordinary battery and no reason to coordinate. The charge algorithm is the same either way, so if the system works, turning DVCC on is not a fix.
  • Your battery's compatibility page says a feature must be disabled. Follow the battery documentation over any general advice.

And when to definitely turn it on: any managed battery with a CAN-bus BMS. Victron's own table tells you not to run those without it.

What you need

DVCC lives on the GX device, so a Cerbo GX is the starting point. A SmartShunt adds accurate state of charge, voltage sensing and the DC load metering that makes the charge current limit behave correctly. A Lynx Smart BMS turns a lithium bank into a managed battery, which is the configuration DVCC is really built for.

If you tell us what is in your system and what it is doing now, we will tell you whether DVCC will change anything. Everything ships from Upland, California.

Guide
|
Victron Energy
Updated: September 09, 2026