device library

Schneider EVlink Pro AC EV charger

Register map(s) for this device, with a note of how far each has been checked. Addresses are 0-based, as on the wire. Scale and byte order are confirmed only at the hardware-verified rung.

coherence-checked

Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.

pointaddress (0-based)typescaleunit
EV state1U161
OCPP status150U161
EV presence1150U161
Major version digit1212U161
Minor version digit1213U161
Build version digit1214U161
Current Phase 12999F32BE1A
Current Phase 23001F32BE1A
Current Phase 33003F32BE1A
Current Phase AVG3009F32BE1A
Voltage Phase 13027F32BE1V
Voltage Phase 23029F32BE1V
Voltage Phase 33031F32BE1V
Voltage Phase AVG3035F32BE1V
Power Active Phase 13053F32BE1kW
Power Active Phase 23055F32BE1kW
Power Active Phase 33057F32BE1kW
Power Active Phase TOT3059F32BE1kW
Power Reactive TOT3067F32BE1kVAR
Power Apparent TOT3075F32BE1kVA
Power factor3083F32BE1
Frequence3109F32BE1Hz
Energy Active TOT3203I64BE1Wh
Energy Reactive TOT3219I64BE1kVARh
Lifebit4000U161
Set command4001U161
Command status4002U32BE1
Set Point4004U161A
Degraded Set Point Mono4005U161A
Degraded Set Point Tri4006U161A
Contactor charging time4007U32BE1s
Session charging time4009U32BE1s
Last stop cause4011U161
Session energy4012U32BE1Wh
Error group bitfield4020U32BE1
Error code bitfield4022U32BE1
Last event n°0 - event code4024U161
Last event n°0 - event start time4025U161Seconds
Last event n°0 - event end time4026U161Seconds
Last event n°1 - event code4027U161
Last event n°1 - event start time4028U161Seconds
Last event n°1 - event end time4029U161Seconds
Last event n°2 - event code4030U161
Last event n°2 - event start time4031U161Seconds
Last event n°2 - event end time4032U161Seconds
Last event n°3 - event code4033U161
Last event n°3 - event start time4034U161Seconds
Last event n°3 - event end time4035U161Seconds
EVSE Model4040U161
EVSE Model4041U161
EVSE Model4042U161
EVSE Model4043U161
EVSE Model4044U161
EVSE Model4045U161
EVSE Model4046U161
EVSE Model4047U161
EVSE Model4048U161
EVSE Model4049U161
EVSE Commercial Reference4060U161
EVSE Commercial Reference4061U161
EVSE Commercial Reference4062U161
EVSE Commercial Reference4063U161
EVSE Commercial Reference4064U161
EVSE Commercial Reference4065U161
EVSE Commercial Reference4066U161
EVSE Commercial Reference4067U161
EVSE Commercial Reference4068U161
EVSE Commercial Reference4069U161

link settings as documented (unverified): TCP; unit ID 255; All exchanged data through Modbus interface is refreshed every second.

bench facts as documented (unverified)
protocol notesException code Illegal data address is returned when a read request is made to an invalid address. Registers between 2999 and 3222, and 4000 and 4079 are reserved; reading unmapped registers in these ranges returns 0xFFFF.
model register4040
identification notesEVSE Commercial Reference is at 4060-4069
doc revisionGEX1969300–06

⚠ disputed: doc_revision is GEX1969300–06 — disputed by Schneider Electric documentation where the latest verified revision is GEX1969300-04 [1.1.1]

⚠ disputed: power_reactive_tot @ 3067 — disputed by EVlink Pro AC Modbus Connectivity Guide GEX1969300-04 which does not map any register at address 3067

field reports — community-sourced, unverified (checked 2026-06-11)
  • In firmware versions prior to 1.2.1 (e.g., 1.1.6), Modbus registers from 1211 to 1213 and from 4003 to 4011 were shifted down by 1 (e.g., set_point was at 4003 instead of 4004, and major_version_digit was at 1211 instead of 1212). Upgrading to firmware 1.2.1 or later increments these addresses by 1. Attempting to write to 4004 on older firmware results in a Modbus exception 2 (Illegal Data Address). [source]
  • confirmed: default_unit_id is 255 — confirmed by EVlink Pro AC Modbus Connectivity Guide GEX1969300-04 [1.3.4]
  • confirmed: framing is TCP — confirmed by EVlink Pro AC Modbus Connectivity Guide GEX1969300-04
  • confirmed: All exchanged data through Modbus interface is refreshed every second — confirmed by EVlink Pro AC Modbus Connectivity Guide GEX1969300-04
  • confirmed: EVSE Model register is at 4040-4049 and EVSE Commercial Reference is at 4060-4069 — confirmed by EVlink Pro AC Modbus Connectivity Guide GEX1969300-04
  • confirmed: Exception code Illegal data address is returned when a read request is made to an invalid address — confirmed by EVlink Pro AC Modbus Connectivity Guide GEX1969300-04
  • confirmed: Registers between 2999 and 3222, and 4000 and 4079 are reserved; reading unmapped registers in these ranges returns 0xFFFF — confirmed by EVlink Pro AC Modbus Connectivity Guide GEX1969300-04
  • confirmed: ev_state @ 1, ocpp_status @ 150, ev_presence @ 1150, major_version_digit @ 1212, minor_version_digit @ 1213, build_version_digit @ 1214 — confirmed by EVlink Pro AC Modbus Connectivity Guide GEX1969300-04
  • confirmed: current_phase_1 @ 2999, current_phase_2 @ 3001, current_phase_3 @ 3003, current_phase_avg @ 3009 — confirmed by EVlink Pro AC Modbus Connectivity Guide GEX1969300-04

The trust ladder

Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.

Device not here? Upload its manual and get a checked map back. It's free.

Want it confirmed against your own device? Order hardware verification. If it doesn't check out, you don't pay.

Building on a lot of devices? License the library — machine-readable maps, the firmware matrix, and API access.