All devices

Bender · EV charger

CC612 / CC613 charge controller Modbus register map

Default configuration

Protocol
Modbus TCP
Port
502
Unit ID
255
Addressing
0-based
Byte order
Big endian
Word order
High word first

Register map

AddressCountNameTypeUnitScaleAccess
1002
Firmware / application version number
Ascii-1R
1041
OCPP charge point status
Charge point status according to the OCPP enumeration.
UInt16-1R
1202
Modbus protocol version
Version of the 'Ebee/Bender/MENNEKES' register set served by the charge controller.
Ascii-1R
1221
Vehicle (control pilot) state
1 = A, 2 = B, 3 = C, 4 = C. The charge controller reports the IEC 61851 state; the values 3 and 4 both mean charging.
UInt16-1R
1401
Relay state
0 = off, 1 = 3 phases active, 5 = 1 phase active.
UInt16-1R
14210
Charge point model
Model string, 20 bytes. Also tells the OEM variant apart (e.g. 'AMTRON 4You').
Ascii-1R
2002
Phase 1 energy from primary meter
Legacy register set only: phase energy in Wh.
UInt32kWh0.001R
2022
Phase 2 energy from primary meter
Legacy register set only: phase energy in Wh.
UInt32kWh0.001R
2042
Phase 3 energy from primary meter
Legacy register set only: phase energy in Wh.
UInt32kWh0.001R
2122
Current L1 from primary meter
Raw value in mA.
UInt32A0.001R
2142
Current L2 from primary meter
Raw value in mA.
UInt32A0.001R
2162
Current L3 from primary meter
Raw value in mA.
UInt32A0.001R
2182
Total energy from primary meter
Lifetime meter reading in Wh.
UInt32kWh0.001R
2202
Active power from primary meter
UInt32W1R
2222
Voltage L1 of the OCPP meter
UInt32V1R
2242
Voltage L2 of the OCPP meter
UInt32V1R
2262
Voltage L3 of the OCPP meter
UInt32V1R
72010
User ID (OCPP IdTag) of the current session
Bytes 0 to 19.
Ascii-1R
7301
EV battery state
State of charge reported by a smart vehicle, 0 to 100.
UInt16%1R
7401
Smart vehicle detected
1 = the connected EV is a smart vehicle and reports its battery state, 0 = no EV or not a smart vehicle.
UInt16-1R
7416
EVCCID of the connected vehicle
ASCII representation of the hex EVCCID, bytes 0 to 11.
Ascii-1R
10001
HEMS current limit
Current limit written by the energy management system. Writing 0 disables charging.
UInt16A1RW
10011
HEMS current limit, 1/10 A
Same limit with 0.1 A resolution; only present on controllers that support it (evcc probes this register).
UInt16A0.1RW
10021
HEMS power limit
Power limit in W. Only available on the MENNEKES AMTRON 4You / 4Business firmware; 0xFFFF means 3-phase full power.
UInt16W1RW
22001
Present state of charge
MENNEKES AMTRON 4You / 4Business protocol 1.6 and newer: 0 to 100, -101 = not available.
Int16%1R

Read this device live with Modbus Connect, free for Windows, macOS and Linux

Related guides

Notes

Source: evcc's charger implementation for the Bender CC612/CC613 register set (charger/bender.go, register constants with their units and the 0xFFFFFFFF/unavailable handling), used as a secondary source -- it records the register numbers and scales of the vendor's "Modbus TCP server for energy management systems" register set, which Bender does not publish on the open web (the public document is the CC612/CC613 installation and operating manual D00325, linked as the supplier URL; it describes the charge controller and how to enable the Modbus TCP server, but not the register list). The charge controller serves holding registers only, on port 502, unit ID 255; function codes 03/06/16. Two settings on the controller are required before this map answers: 'Modbus TCP Server for energy management systems' enabled, and 'Register Address Set' set to the Ebee/Bender/MENNEKES selection (not Phoenix, TQ-DM100 or ISE/IGT Kassel); 'Allow UID Disclose' must be on for the EVCCID and IdTag rows. Rows 200-204 only exist on charge controllers with the older (legacy) register set; on the current set the meter values are the 32-bit rows 212-227. A 32-bit value of 0xFFFFFFFF (or any value with the top bit set) means 'not available' and appears briefly while the controller restarts. This one controller is the OEM heart of a long list of wallboxes: MENNEKES AMTRON Professional / Twincharge / AMEDIO, Garo GLB and LS4, Ensto Chago Wallbox, Juice Charger Me, SMA EV Charger Business, Webasto Live, Spelsberg Wallbox Smart Pro, CUBOS C11E/C22E, ubitricity Heinz, TechniSat Technivolt, Ebee, Optec Mobility One and others -- they are all covered by this seed instead of a separate file each. MENNEKES' own HCC3 controllers (AMTRON Xtra / Premium) have a different map and a separate seed. For two-outlet stations each charging point is a separate Modbus server (port 502 for point 1, 503 for point 2).