Schneider EVlink Pro AC EV charger

Register map(s) for this device, each at the trust rung it earned. Addresses are 0-based as on the wire. Word order and scaling are confirmed at the hardware-verified rung and at no rung below it.

interop-verified

Read + decoded cleanly over a real network vs an independent third-party Modbus test server (transport and framing; reads are remapped into the server's register window, so the map's own addresses are NOT exercised). Does NOT prove word order/scaling against the actual device.

point	address (0-based)	type	scale	unit
ev_state	1	U16	1
ocpp_status	150	U16	1
ev_presence	1150	U16	1
major_version_digit	1212	U16	1
minor_version_digit	1213	U16	1
build_version_digit	1214	U16	1
current_phase_1	2999	F32BE	1	A
current_phase_2	3001	F32BE	1	A
current_phase_3	3003	F32BE	1	A
current_phase_avg	3009	F32BE	1	A
voltage_phase_1	3027	F32BE	1	V
voltage_phase_2	3029	F32BE	1	V
voltage_phase_3	3031	F32BE	1	V
voltage_phase_avg	3035	F32BE	1	V
power_active_phase_1	3053	F32BE	1	kW
power_active_phase_2	3055	F32BE	1	kW
power_active_phase_3	3057	F32BE	1	kW
power_active_phase_tot	3059	F32BE	1	kW
power_reactive_tot	3067	F32BE	1	kVAR
power_apparent_tot	3075	F32BE	1	kVA
power_factor	3083	F32BE	1
frequence	3109	F32BE	1	Hz
lifebit	4000	U16	1
set_command	4001	U16	1
command_status	4002	U32BE	1
set_point	4004	U16	1	A
degraded_set_point_mono	4005	U16	1	A
degraded_set_point_tri	4006	U16	1	A
contactor_charging_time	4007	U32BE	1	s
session_charging_time	4009	U32BE	1	s
last_stop_cause	4011	U16	1
session_energy	4012	U32BE	1	Wh
error_group_bitfield	4020	U32BE	1
error_code_bitfield	4022	U32BE	1

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 notes	Exception 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 register	4040
identification notes	EVSE Commercial Reference is at 4060-4069
doc revision	GEX1969300–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.

generated — A prompt produced it. Unproven — anyone can regenerate this.
structure-verified — Decode path is structurally sound (addresses, widths, finite values). Does NOT prove word order or scaling.
interop-verified — Read + decoded cleanly over a real network vs an independent third-party Modbus test server (transport and framing; reads are remapped into the server's register window, so the map's own addresses are NOT exercised). Does NOT prove word order/scaling against the actual device.
simulator-verified — Decoded correctly against a protocol emulator seeded with known-true values — catches word-order/scaling errors vs the emulator, not the physical device.
hardware-verified x1 — Matched a real device with operator-attested readings as ground truth — the only rung that confirms word order + scaling on the wire.

If your device isn't here, upload its register map. Generation is free, and the connector keeps the rung it earns under testing.

To prove a connector against your own device, order hardware verification. If it doesn't verify, you don't pay.

Platform builders can license the verified library: machine-readable maps, the firmware matrix, API access.