Bender CC613
Charge controller for AC wallboxes with charging state, meter values and a writable current limit.
The Bender CC613 is a charge controller that runs AC wallboxes and charging stations and measures charging power and energy through its meter. This Modbus TCP template reads charging state, meter values, session data and load management values and lets you set the charging current limit and availability from ModbusCloud.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 64, read and write
- Brand
- Bender
- Key readings
- Vehicle state · Charge point status · Charging power · Energy · Phase currents · Session energy
- Available commands
- Charging current limit · Charge point availability · Safe current · Load management limits
- Compatible models
- CC613 · CC612 · Wallboxes with a Bender CC612 or CC613 charge controller
- Last updated
Registers (64)
63 read, 9 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| Vehicle State | Read | ||||
| OCPP Charge Point Status | Read | ||||
| Total Active Power | W | Read | |||
| Total Energy | Wh | Read | |||
| Current L1 | A | Read | |||
| Current L2 | A | Read | |||
| Current L3 | A | Read | |||
| Voltage L1 | V | Read | |||
| Voltage L2 | V | Read | |||
| Voltage L3 | V | Read | |||
| Power L1 | W | Read | |||
| Power L2 | W | Read | |||
| Power L3 | W | Read | |||
| Energy L1 | Wh | Read | |||
| Energy L2 | Wh | Read | |||
| Energy L3 | Wh | Read | |||
| Signaled Current | Read | ||||
| Charged Energy Session | Wh | Read | |||
| Charge Duration Session | s | Read | |||
| Charged Energy Session 16-bit | Wh | Read | |||
| Charge Duration Session 16-bit | s | Read | |||
| Relay State | Read | ||||
| Plug Lock Status | Read | ||||
| Error Codes 1 | Read | ||||
| Error Codes 2 | Read | ||||
| Error Codes 3 | Read | ||||
| Error Codes 4 | Read | ||||
| Max Current EV | Read | ||||
| Minimum Current Limit | Read | ||||
| Operator Current Limit | A | Read | |||
| EV Battery State | % | Read | |||
| Smart Vehicle Detected | Read | ||||
| HEMS Current Limit | A | Read and write | |||
| Charge Point Availability | Read and write | ||||
| Safe Current | Read and write | ||||
| Communication Timeout | Read and write | ||||
| Modbus Address Offset | Read and write | ||||
| DLM Mode | Read | ||||
| DLM Sub-Distribution Limit L1 | A | Read | |||
| DLM Sub-Distribution Limit L2 | A | Read | |||
| DLM Sub-Distribution Limit L3 | A | Read | |||
| DLM Operator Limit L1 | A | Read and write | |||
| DLM Operator Limit L2 | A | Read and write | |||
| DLM Operator Limit L3 | A | Read and write | |||
| DLM External Meter Support | Read | ||||
| DLM Connected Slaves | Read | ||||
| DLM Current Applied L1 | A | Read | |||
| DLM Current Applied L2 | A | Read | |||
| DLM Current Applied L3 | A | Read | |||
| DLM Current Available L1 | A | Read | |||
| DLM Current Available L2 | A | Read | |||
| DLM Current Available L3 | A | Read | |||
| EV Required Energy 15118 | Read | ||||
| EV Required Energy 15118 32-bit | Read | ||||
| Scheduled Departure Time | Read | ||||
| Scheduled Departure Date | Read | ||||
| Session Start Time | Read | ||||
| Session End Time | Read | ||||
| Firmware Version | Read | ||||
| Protocol Version | Read | ||||
| Charge Point Model | Read | ||||
| ID Tag | Read | ||||
| EVCCID | Read | ||||
| Write ID Tag | Write |
Loading registers…
Send your device list
If a device is not in the library yet, we build the template for free as soon as we have the register data.
Use cases
- Show charging power, session energy and vehicle state of each charging point on a ModbusCloud dashboard.
- Get an email alert when the charge point reports a fault or the error codes are not zero.
- Keep a year of energy history per charging point to settle charging costs per month.
- Lower the charging current limit from ModbusCloud when the building connection is near its limit.
- Check the load management values of a charging park and see how much current each phase has left.
Installation
Connect the Ethernet port of the wallbox or charge controller to the same network as the ModbusCloud Gateway.
In the controller web interface, enable the Modbus TCP server and select the register set Ebee, Bender, MENNEKES.
Note the IP address of the controller; charging point 1 uses port 502, charging point 2 port 503.
In ModbusCloud, add a Modbus TCP device with that IP address and port and import this template.
Check that vehicle state and charge point status change when you plug in a vehicle.
Things to watch for
All meter values show 4294967295. What is wrong?
That is 0xFFFFFFFF, the value the controller sends when no meter is present or the value is not available. Check that a meter is built in and configured, and that your meter type supports per phase values. Voltages and total power need controller software 5.22 or later.
Why does the controller not answer on Modbus TCP?
The Modbus TCP server is off by default. Enable it in the controller settings and choose the register set Ebee, Bender, MENNEKES, not Phoenix or TQ-DM100. For the second charging point of a twin station use port 503.
Why does the car charge with less current than the limit I wrote?
The HEMS current limit is an upper limit. The signalled current can be lower because of the cable, the vehicle or dynamic load management. Writing 0 pauses the session. If the energy manager stops writing, the controller can fall back to the safe current after the communication timeout.
Is it safe to write the other settings?
Write with care. Changing Modbus Address Offset moves every register, so the template no longer matches. Charge Point Availability uses inverted values before software 5.22. Write ID Tag starts or stops a session like an RFID card and only works when the controller allows it.
Want to see how it works?
