Every device. One tool. Pay once. Modbus · BACnet · Siemens S7 · one-time licence · also from us: BACManager ↗

Victron Cerbo GX Modbus TCP: Unit-IDs, Registers and Scale Factors

A Victron GX device — Cerbo GX, Color Control GX, Venus GX or the GX built into a MultiPlus-II — is a Modbus TCP gateway to everything connected to it: inverter/chargers, solar chargers, batteries, meters. The Unit-ID picks the device, the register picks the value, and nearly every first attempt fails on the Unit-ID. This page covers enabling the server, the Unit-IDs, the system registers, the scale factors and the error codes, from Victron's own manual and register list.

ModbusManager Pro dashboard for a Victron Cerbo GX energy storage system: energy flow with 3.2 kW solar, battery at 68 % charging with 1.4 kW, 1.2 kW house load and 0.6 kW export to the grid; battery voltage, current and state; active input grid; VE.Bus state bulk; AC in and out voltages; input current limit; VE.Bus error none; switch on; and a trend of PV, battery and grid power
The free workspace below on a simulated Cerbo GX — system values on Unit-ID 100, the MultiPlus on 227.

Enable the Modbus TCP Server

Modbus TCP is disabled by default. On the GX go to Settings → Integrations → Modbus TCP server (on older firmware Settings → Services → Modbus-TCP) and enable it. The server listens on TCP port 502. The same menu lists Available services — every connected device with its Unit-ID — and shows the last error, which is the fastest way to see why a request failed.

Unit-ID Selects the Device

The GX answers for every device behind it; the Unit-ID in the request says which one. Victron's preferred IDs:

Unit-IDDevice
100com.victronenergy.system — the whole-system values (0 maps to the same; use 100)
227Cerbo GX VE.Bus port: MultiPlus / Quattro
228MultiPlus-II GX / EasySolar-II GX VE.Bus port
242Venus GX VE.Bus port
246Color Control GX VE.Bus port
223 / 224 / 226Cerbo GX VE.Direct ports (solar chargers, battery monitors)
225CAN-bus BMS

Since Venus OS 2.60 Unit-IDs are assigned dynamically: the table gives the preferred ones, but the Available services list on your GX is the truth. They do not change after a reboot. Units in a parallel or three-phase system are not addressed one by one — read the totals.

System Registers (Unit-ID 100)

Function code 3 or 4 — Victron says there is no difference. Addresses go on the wire as listed. Scale is Victron's scale factor: divide the raw value by it.

RegisterValueTypeScale
808–810PV AC-coupled on output L1–L3uint161 (W)
817–819AC consumption L1–L3uint161 (W)
820–822Grid L1–L3 (+ import, − export)int161 (W)
826Active input: 0 unknown, 1 grid, 2 generator, 3 shore, 240 noneuint16—
840Battery voltageuint1610 (V)
841Battery currentint1610 (A)
842Battery power (+ charging)int161 (W)
843State of chargeuint161 (%)
844Battery state: 0 idle, 1 charging, 2 discharginguint16—
850 / 851PV DC-coupled power / currentuint16 / int161 (W) / 10 (A)
860DC system powerint161 (W)
884…906PV and consumption again as 32-bituint32 / int321 (W)

The 16-bit power registers stop at 65 535 W (32 767 W signed). For a larger system use the 32-bit copies from 868 and 884 onwards.

Inverter/Charger (VE.Bus, e.g. Unit-ID 227)

RegisterValueScale
3–5AC input voltage L1–L310 (V)
9AC input frequency100 (Hz)
12–14AC input power L1–L30.1 → raw × 10 W
15–17 / 23–25AC output voltage / power10 (V) / 0.1
22Active input current limit (writable)10 (A)
26 / 27Battery voltage / current100 (V) / 10 (A)
31VE.Bus state: 3 bulk, 4 absorption, 5 float, 8 passthru, 9 inverting…—
32VE.Bus error (0 = none)—
33Switch: 1 charger only, 2 inverter only, 3 on, 4 off—
37ESS power setpoint phase 1 (writable)1 (W)

Victron's own example: Unit-ID 246, register 3, the reply 2302 ÷ 10 = 230.2 V AC. Watch the power registers with scale 0.1 — dividing by 0.1 multiplies by 10.

Error Codes

CodeMeaning on a GX
0x01Function not supported (only 3, 4, 6, 16 are)
0x02Unit-ID fine, but a requested register does not exist for that device — including a gap inside a block
0x03Invalid quantity of registers
0x0AUnit-ID in the mapping list, but no device on that port
0x0BUnit-ID not in the mapping list at all

Reading 1–100 in one go fails because registers 1 and 2 do not exist; reading 840–850 fails because 847–849 are reserved. Read gap-free blocks, as the workspace does.

Common Mistakes

Step-by-Step: Reading a Cerbo GX with ModbusManager

  1. Enable the Modbus TCP server on the GX and note the Unit-IDs under Available services.
  2. In ModbusManager choose TCP, the GX's IP address, port 502.
  3. Read FC03, Unit-ID 100, address 840, quantity 7: battery voltage, current, power, SOC and state.
  4. Open the workspace below; change 227 to your VE.Bus Unit-ID if it differs.

Download a Ready-Made Workspace

Read-only. Nothing is written — no ESS setpoint, no current limit. Set the IP address of your GX in the connection. Tags, script and dashboard are ModbusManager Pro features; Standard opens the poll windows only.

Victron_CerboGX.json

Victron Cerbo GX workspace (Unit-ID 100 + 227). Open via Workspace › Open in ModbusManager Pro.

Download Workspace

Try it with ModbusManager Pro

Energy-flow element, historian, alarms on SOC, and MQTT to Home Assistant. Free 14-day trial. No credit card. Windows 10/11.

Download Pro Trial

The grid meter on a Victron system is often a Carlo Gavazzi EM24 or EM340. Other solar systems: Deye / Sunsynk, Huawei SUN2000, Modbus to MQTT.

Frequently Asked Questions

Which Unit-ID does a Victron Cerbo GX use for system data?

Unit-ID 100 for com.victronenergy.system: battery 840–846, PV 850, grid 820–822, consumption 817–819. Unit-ID 0 maps to the same data, but Victron recommends 100.

How do I enable Modbus TCP on a Victron GX?

It is disabled by default. Enable the Modbus TCP server under Settings → Integrations (older firmware: Settings → Services). The same menu lists the Unit-ID of every connected device.

What does exception 0x0B mean from a Victron GX?

The Unit-ID is not in the GX's mapping list. 0x0A means it is mapped but no device answers on that port, and 0x02 means the Unit-ID is right but a requested register does not exist.

How are Victron Modbus values scaled?

Divide by the scale factor in Victron's register list: battery voltage 840 has factor 10 (526 = 52.6 V); VE.Bus power has factor 0.1, so the raw value is multiplied by 10.

What is the Unit-ID of the MultiPlus on a Cerbo GX?

Victron's preferred ID for the Cerbo GX VE.Bus port is 227 (CCGX 246, Venus GX 242, MultiPlus-II GX 228). Since Venus OS 2.60 IDs are assigned dynamically; check Available services on your GX.

Sources

Victron Energy, GX Modbus-TCP Manual (victronenergy.com), and CCGX-Modbus-TCP-register-list-3.60.xlsx (field list, Unit ID mapping and document versions). Tested against a simulator built from these documents, not a physical GX.

// beyond the GX

Victron plus the rest of the site

ModbusManager Pro reads the GX next to meters, PLCs and BACnet controllers, and republishes the values as one Modbus TCP map or as MQTT topics with Home Assistant discovery.

Modbus gateway software →