Etrel · EV charger
INCH / INCH Duo Modbus register map
Default configuration
- Protocol
- Modbus TCP
- Port
- 502
- Unit ID
- 1
- Addressing
- 0-based
- Byte order
- Big endian
- Word order
- High word first
Register map
| Address | Count | Name | Type | Unit | Scale | Access |
|---|---|---|---|---|---|---|
| 0 | 1 | Connector 1 status 0 = unknown, 1 = available, 2 = preparing (unauthorized/disconnected), 3 = preparing (waiting for EV), 4 = charging, 5 = charging paused by EV, 6 = charging paused by EVSE, 7 = finishing, 8 = faulted, 9 = unpausing charging, 10 = unavailable, 11 = reserved. | Int16 | - | 1 | R |
| 1 | 1 | Connector 1 measured vehicle number of phases 0 = three phases, 1 = single phase (L1), 2 = single phase (L2), 3 = single phase (L3), 4 = unknown, 5 = two phases. | Int16 | - | 1 | R |
| 2 | 2 | Connector 1 EV max phase current | Float32 | A | 1 | R |
| 4 | 2 | Connector 1 target current from power management or Modbus | Float32 | A | 1 | R |
| 6 | 2 | Connector 1 frequency | Float32 | Hz | 1 | R |
| 8 | 2 | Connector 1 voltage L1-N | Float32 | V | 1 | R |
| 10 | 2 | Connector 1 voltage L2-N | Float32 | V | 1 | R |
| 12 | 2 | Connector 1 voltage L3-N | Float32 | V | 1 | R |
| 14 | 2 | Connector 1 current L1 | Float32 | A | 1 | R |
| 16 | 2 | Connector 1 current L2 | Float32 | A | 1 | R |
| 18 | 2 | Connector 1 current L3 | Float32 | A | 1 | R |
| 20 | 2 | Connector 1 active power L1 | Float32 | kW | 1 | R |
| 22 | 2 | Connector 1 active power L2 | Float32 | kW | 1 | R |
| 24 | 2 | Connector 1 active power L3 | Float32 | kW | 1 | R |
| 26 | 2 | Connector 1 active power, total | Float32 | kW | 1 | R |
| 28 | 2 | Connector 1 power factor | Float32 | - | 1 | R |
| 30 | 2 | Connector 1 energy of running session Total imported active energy in the running charging session. | Float32 | kWh | 1 | R |
| 44 | 2 | Connector 1 EV max power Maximum power detected in the running charging session. | Float32 | kW | 1 | R |
| 46 | 2 | Connector 1 EV planned energy Energy planned to be delivered in the running charging session. | Float32 | kWh | 1 | R |
| 53 | 1 | Connector 1 selected charging mode 1 = fast mode, 2 = smart mode. | Int16 | - | 1 | R |
| 54 | 10 | Connector 1 RFID UID of last session | Ascii | - | 1 | R |
| 100 | 1 | Connector 2 status INCH Duo only. Same enumeration as connector 1. | Int16 | - | 1 | R |
| 101 | 1 | Connector 2 measured vehicle number of phases INCH Duo only. Same enumeration as connector 1. | Int16 | - | 1 | R |
| 102 | 2 | Connector 2 EV max phase current | Float32 | A | 1 | R |
| 104 | 2 | Connector 2 target current from power management or Modbus | Float32 | A | 1 | R |
| 106 | 2 | Connector 2 frequency | Float32 | Hz | 1 | R |
| 108 | 2 | Connector 2 voltage L1-N | Float32 | V | 1 | R |
| 110 | 2 | Connector 2 voltage L2-N | Float32 | V | 1 | R |
| 112 | 2 | Connector 2 voltage L3-N | Float32 | V | 1 | R |
| 114 | 2 | Connector 2 current L1 | Float32 | A | 1 | R |
| 116 | 2 | Connector 2 current L2 | Float32 | A | 1 | R |
| 118 | 2 | Connector 2 current L3 | Float32 | A | 1 | R |
| 120 | 2 | Connector 2 active power L1 | Float32 | kW | 1 | R |
| 122 | 2 | Connector 2 active power L2 | Float32 | kW | 1 | R |
| 124 | 2 | Connector 2 active power L3 | Float32 | kW | 1 | R |
| 126 | 2 | Connector 2 active power, total | Float32 | kW | 1 | R |
| 128 | 2 | Connector 2 power factor | Float32 | - | 1 | R |
| 130 | 2 | Connector 2 energy of running session | Float32 | kWh | 1 | R |
| 144 | 2 | Connector 2 EV max power | Float32 | kW | 1 | R |
| 146 | 2 | Connector 2 EV planned energy | Float32 | kWh | 1 | R |
| 153 | 1 | Connector 2 selected charging mode 1 = fast mode, 2 = smart mode. | Int16 | - | 1 | R |
| 154 | 10 | Connector 2 RFID UID of last session | Ascii | - | 1 | R |
| 990 | 10 | Charger serial number | Ascii | - | 1 | R |
| 1000 | 10 | Charger model | Ascii | - | 1 | R |
| 1010 | 5 | Charger hardware version | Ascii | - | 1 | R |
| 1015 | 5 | Charger software version | Ascii | - | 1 | R |
| 1020 | 2 | Charger number of connectors | Int32 | - | 1 | R |
| 1022 | 1 | Connector 1 connector type 1 = socket type 2, 2 = cable type 2, 3 = socket household, 4 = unknown. | Int16 | - | 1 | R |
| 1023 | 1 | Connector 1 number of phases 0 = three phases, 1 = single phase (L1), 2 = single phase (L2), 3 = single phase (L3), 4 = unknown, 5 = two phases. | Int16 | - | 1 | R |
| 1024 | 1 | Connector 1 L1 connected to phase 1 = L1, 2 = L2, 3 = L3. | Int16 | - | 1 | R |
| 1025 | 1 | Connector 1 L2 connected to phase 1 = L1, 2 = L2, 3 = L3. | Int16 | - | 1 | R |
| 1026 | 1 | Connector 1 L3 connected to phase 1 = L1, 2 = L2, 3 = L3. | Int16 | - | 1 | R |
| 1028 | 2 | Connector 1 custom max current | Float32 | A | 1 | R |
| 1122 | 1 | Connector 2 connector type INCH Duo only. 1 = socket type 2, 2 = cable type 2, 3 = socket household, 4 = unknown. | Int16 | - | 1 | R |
| 1123 | 1 | Connector 2 number of phases INCH Duo only. | Int16 | - | 1 | R |
| 1124 | 1 | Connector 2 L1 connected to phase INCH Duo only. 1 = L1, 2 = L2, 3 = L3. | Int16 | - | 1 | R |
| 1125 | 1 | Connector 2 L2 connected to phase INCH Duo only. 1 = L1, 2 = L2, 3 = L3. | Int16 | - | 1 | R |
| 1126 | 1 | Connector 2 L3 connected to phase INCH Duo only. 1 = L1, 2 = L2, 3 = L3. | Int16 | - | 1 | R |
| 1128 | 2 | Connector 2 custom max current | Float32 | A | 1 | R |
Read this device live with Modbus Connect, free for Windows, macOS and Linux
Related guides
Notes
Source: Etrel, "INCH and DUO SmartHome Modbus TCP Registers master SPECIFICATIONS - V6.0 - 072025_02.xlsx" (sheets 'ReadRegisters', 'Write registers' and 'Enumerations'), the vendor register list attached to "Modbus Communication with INCH products" in the Etrel Knowledge Centre (etrel.atlassian.net, page 3485665834) and downloadable without a login. The document states that the register numbers are the actual address values placed in the messages (not Modicon names) and that all values are big-endian, so this file uses zero-based addressing with high word first. Reading uses function code 04 on port 502, writing uses function code 16 (the write table is a separate list, so those entries are marked W); the vendor lists the unit identifier as free (the charger answers on the configured one, evcc uses 1). Connector 2 registers exist on the INCH Duo; on a single-connector INCH they are simply absent. Left out on purpose: the 64-bit rows the document defines -- running session duration (32), running session departure time (36), running session ID (40) and the lifetime meter value (48, int64 mWh) -- because the app has no 64-bit integer type, and the same rows' 32-bit counterparts do not exist. The building-load-guard and power-cluster blocks at 2000+ live on the second Modbus socket (port 503) and are not part of this device map.