Heidelberg Energy Control Wallbox Modbus
Monitors and controls Heidelberg Energy Control Wallbox charging via Modbus RTU.
This template connects a Heidelberg Energy Control Wallbox to ModbusCloud via Modbus RTU. It reads voltage, current, power, energy, temperature, and charging state. It also allows control of maximum charging current, standby function, and remote lock.
- Protocol
- Modbus RTU
- Connection
- RS485, 19200 baud
- Registers
- 17, read and write
- Key readings
- L1 to L3 Current RMS · L1 to L3 Voltage · Power (L1+L2+L3) · Energy since PowerOn · Energy since Installation · Charging State
- Available commands
- Max Current (60-160) · Standby Function Control · Remote Lock
- Compatible models
- Heidelberg Energy Control
- Last updated
Registers (17)
14 read, 3 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| L1 Current RMS | A | Read | |||
| L2 Current RMS | A | Read | |||
| L3 Current RMS | A | Read | |||
| PCB-Temperatur in 0,1 °C | °C | Read | |||
| L1 Voltage | <v.1V> | Read | |||
| L2 Voltage | V | Read | |||
| L3 Voltage | V | Read | |||
| Extern Lock State | Read | ||||
| Power (L1+L2+L3) in VA | <v.1VA> | Read | |||
| Energy since PowerOn | <v.1VAh> | Read | |||
| Energy since Installation | <v.1VAh> | Read | |||
| Hardware configuration max current | <v.1A> | Read | |||
| Hardware configuration min current | <v.1A> | Read | |||
| Charging State | Read | ||||
| Max Current A 60-160 | A | Write | |||
| Standby Function Control | Write | ||||
| Remote Lock | 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
- Monitor real-time charging power and per-phase current on a live dashboard for each wallbox.
- Track total energy consumption since installation to generate usage reports for billing or energy audits.
- Set the maximum charging current remotely to implement simple load management across multiple wallboxes.
- Create an alert when the PCB temperature exceeds a safe threshold to prevent hardware damage.
- Use the remote lock feature to restrict wallbox access outside of scheduled charging hours.
- Monitor the charging state register to detect faults or idle periods and notify the end user automatically.
Installation
Connect the Modbus RTU wiring (A and B terminals) from the Heidelberg Energy Control Wallbox to the RS-485 port on your ModbusCloud Gateway.
Set the Modbus slave address on the wallbox using its DIP switches or configuration interface, and note the address for the next step.
Configure the gateway serial port to 19200 baud, even parity, and 1 stop bit to match the wallbox default settings.
Import the Heidelberg Energy Control Wallbox template from the ModbusCloud template library and assign the correct Modbus slave address.
Verify communication by checking that voltage, current, and charging state values appear on the ModbusCloud dashboard.
Things to watch for
The gateway cannot communicate with the wallbox. What should I check?
Verify that the baud rate is set to 19200 with even parity and 1 stop bit on both the gateway and the wallbox. Also confirm that the A and B RS-485 wires are not swapped and that the correct Modbus slave address is configured.
What do the Max Current register values 60 to 160 mean?
The values represent 6.0A to 16.0A in 0.1A increments. For example, writing 100 sets the maximum charging current to 10.0A.
Why does the PCB temperature value look too high?
The temperature register uses 0.1 degree Celsius resolution. Divide the raw value by 10 to get the actual temperature in degrees Celsius. The template should handle this scaling automatically.
Can I use this template with multiple Heidelberg wallboxes on the same RS-485 bus?
Yes. Assign a unique Modbus slave address to each wallbox and create a separate device instance in ModbusCloud for each one, all using this template.
Want to see how it works?
