Schneider Electric · EV charger
EVlink Pro AC / Charge Pro 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
| Address | Count | Name | Type | Unit | Scale | Access |
|---|---|---|---|---|---|---|
| 1 | 1 | EV state 0 = state E (0 V), 1 = state F, not available (-12 V), 2 = A1 available, not ready (12 V), 3 = B1 EV connected, not ready (9 V), 4 = C1 charging, stop requested by EVSE (6 V), 5 = D1 charging with ventilation required, stop requested by EVSE (3 V), 6 = A2 available, ready (12 V PWM), 7 = B2 EV connected, ready (9 V PWM), 8 = C2 charging (6 V PWM), 9 = D2 charging with ventilation required (3 V PWM), 10 = control pilot wire invalid, 11 = control pilot wire symmetric, fault on the control circuit. | UInt16 | - | 1 | R |
| 150 | 1 | OCPP status 0 = init, 1 = available, 2 = preparing, 3 = charging, 4 = suspended EV, 5 = suspended EVSE, 6 = finishing, 7 = reserved, 8 = unavailable, 9 = faulted. | UInt16 | - | 1 | R |
| 1150 | 1 | EV presence 0 = EV not present, 1 = EV present. Updated only when not charging. | UInt16 | - | 1 | R |
| 1212 | 1 | Global release version, major | UInt16 | - | 1 | R |
| 1213 | 1 | Global release version, minor | UInt16 | - | 1 | R |
| 1214 | 1 | Global release version, build | UInt16 | - | 1 | R |
| 2999 | 2 | Current phase 1 | Float32 | A | 1 | R |
| 3001 | 2 | Current phase 2 | Float32 | A | 1 | R |
| 3003 | 2 | Current phase 3 | Float32 | A | 1 | R |
| 3009 | 2 | Current phase, average | Float32 | A | 1 | R |
| 3027 | 2 | Voltage phase 1 | Float32 | V | 1 | R |
| 3029 | 2 | Voltage phase 2 | Float32 | V | 1 | R |
| 3031 | 2 | Voltage phase 3 | Float32 | V | 1 | R |
| 3035 | 2 | Voltage phase, average | Float32 | V | 1 | R |
| 3053 | 2 | Active power phase 1 | Float32 | kW | 1 | R |
| 3055 | 2 | Active power phase 2 | Float32 | kW | 1 | R |
| 3057 | 2 | Active power phase 3 | Float32 | kW | 1 | R |
| 3059 | 2 | Active power, total | Float32 | kW | 1 | R |
| 3075 | 2 | Apparent power, total | Float32 | kVA | 1 | R |
| 3083 | 2 | Power factor | Float32 | - | 1 | R |
| 3109 | 2 | Frequency | Float32 | Hz | 1 | R |
| 4000 | 1 | Lifebit Communication watchdog. The charging station sets it to 1, the client resets it to 0; writing 2 deactivates the lifebit. When activated, communication counts as lost if the lifebit is not refreshed within the configured timeout. | UInt16 | - | 1 | RW |
| 4001 | 1 | Set command 3 = stop charge, 7 = suspend charge, 8 = restart charge, 9 = reboot, 40 = set available, 41 = set unavailable. The station resets the register to 0 afterwards and reports errors in 4002. | UInt16 | - | 1 | RW |
| 4002 | 2 | Command status Status of the previous remote command. | UInt32 | - | 1 | R |
| 4004 | 1 | Set point Remote energy management setpoint in amps, 0 to 32 A; 99 means no charge in progress. A setpoint change is applied within 15 s. | UInt16 | A | 1 | RW |
| 4005 | 1 | Degraded set point, single phase Setpoint applied when the Modbus communication is lost, configured via eSetup. The guide's table marks 4005/4006 read-only, while its text says they are written by the external system; access is RW here to match the text. | UInt16 | A | 1 | RW |
| 4006 | 1 | Degraded set point, three phase Setpoint applied when the Modbus communication is lost, configured via eSetup; see the note on 4005. | UInt16 | A | 1 | RW |
| 4007 | 2 | Contactor charging time Duration since the contactor closed. | UInt32 | s | 1 | R |
| 4009 | 2 | Session charging time Duration since the transaction started. | UInt32 | s | 1 | R |
| 4011 | 1 | Last stop cause 0 = none, 1 = emergency stop, 2 = EV disconnected, 3 = hard reset, 4 = local, 5 = other, 6 = power loss, 7 = reboot, 8 = remote, 9 = soft reset, 10 = unlock command, 11 = de-authorized. | UInt16 | - | 1 | R |
| 4012 | 2 | Session energy Consumed energy during the charging session in Wh. | UInt32 | kWh | 0.001 | R |
| 4020 | 2 | Error group bitfield Currently raised error groups, one bit per group. | UInt32 | - | 1 | R |
| 4022 | 2 | Error code bitfield Currently raised error codes, one bit per error. | UInt32 | - | 1 | R |
| 4024 | 1 | Last event 0: event code | UInt16 | - | 1 | R |
| 4025 | 1 | Last event 0: start time | UInt16 | s | 1 | R |
| 4026 | 1 | Last event 0: end time | UInt16 | s | 1 | R |
| 4027 | 1 | Last event 1: event code | UInt16 | - | 1 | R |
| 4028 | 1 | Last event 1: start time | UInt16 | s | 1 | R |
| 4029 | 1 | Last event 1: end time | UInt16 | s | 1 | R |
| 4030 | 1 | Last event 2: event code | UInt16 | - | 1 | R |
| 4031 | 1 | Last event 2: start time | UInt16 | s | 1 | R |
| 4032 | 1 | Last event 2: end time | UInt16 | s | 1 | R |
| 4033 | 1 | Last event 3: event code | UInt16 | - | 1 | R |
| 4034 | 1 | Last event 3: start time | UInt16 | s | 1 | R |
| 4035 | 1 | Last event 3: end time | UInt16 | s | 1 | R |
| 4040 | 10 | EVSE model Two characters per register. | Ascii | - | 1 | R |
| 4060 | 10 | EVSE commercial reference Two characters per register. | Ascii | - | 1 | R |
Read this device live with Modbus Connect, free for Windows, macOS and Linux
Related guides
Notes
Source: Schneider Electric, "EVlink Pro AC - Modbus Connectivity Guide", GEX1969300-04 (06/2023), chapter "Registers" plus the chapters "Supported Commands", "Lifebit" and "EVlink Pro AC Modbus Interface". The guide states that the table lists the registers accessible to the client "on base 0" and that the server ID is 255; its data-format chapter defines SINT32/UINT32 as high word first, so this file uses zero-based addressing with high word first. The PDF was read from a mirror of the vendor document (devicelib.my-gekko.com); the reference and revision are the vendor's own. The guide's section on the Modbus interface says the external system writes the degraded setpoints 4005/4006, so those two rows are RW here even though the register table marks the whole block read-only -- the seed follows the descriptive text and says so in the row descriptions. Left out: "Energy Active TOT" (3203) and "Energy Reactive TOT" (3219), both int64 in the guide, because the app has no 64-bit integer type; session energy (4012, uint32) carries the same value for a charging session. evcc's charger/schneider-v3.go drives the same addresses with function codes 03/06, which is how the table is to be read.