Easy Modbus
  1. Home
  2. Modbus register maps
  3. Schneider Electric
  4. EVlink Pro AC charging station (Modbus TCP)

EV charger · Modbus register map

Schneider Electric EVlink Pro AC charging station (Modbus TCP) Modbus register map

Updated 19 November 2026

Short answer

The EVlink Pro AC runs a Modbus TCP server so a building or energy management system can limit its charging current and monitor it. This map covers the pilot and OCPP states, firmware version, the lifebit heartbeat, remote commands, the current setpoint and fallback setpoints, session data, error bitfields, the last four events and the model strings.

This page lists 32 Modbus registers for the Schneider Electric EVlink Pro AC charging station (Modbus TCP) — 3 writable — with the table, 0-based wire address, data type, word order, scale, units and access of each, re-typed from Schneider Electric’s own free documentation (linked below) and checked against it.

Manufacturer
Schneider Electric
Model
EVlink Pro AC charging station (Modbus TCP)
Equipment type
EV charger
Registers
32 (3 writable)
Transport
Modbus TCP
Default unit ID
255
Documented addressing
0-based (the number printed is the address on the wire)
32-bit word order
ABCD high word first (big-endian)
Firmware
Software 1.1.6 to 1.4.0 (per the revision history)
Also known as
EVlink Pro AC
Source document
EVlink Pro AC Modbus Connectivity Guide · GEX1969300-06 · rev. 2026-03 (cover date; the revision history lists January 2026)
Download CSV all columns JSON Manufacturer PDF ↗

Integration notes: Schneider Electric EVlink Pro AC charging station (Modbus TCP)

Integration in brief

Connect over Modbus TCP to unit ID 255. Write the current limit in amps to 4004 and keep the lifebit at 4000 cycling so the charger knows the master is alive; read 1 and 150 for state and 4012 for session energy.

Minimum registers to map

Addresses are 0-based wire addresses. Enough to monitor and run the unit; map more as the job needs.

RegisterNameTypeWhyAccess
HR 4004Set PointUINT16Charging current setpointRead/write
HR 4000LifebitUINT16Lifebit heartbeatRead/write
HR 1EV stateUINT16Pilot (EV) stateRead
HR 150OCPP statusUINT16OCPP statusRead
HR 4012Session energyUINT32 ABCDSession energyRead
HR 4001Set commandUINT16Remote commands (stop, suspend, restart)Read/write

Enable Modbus control & writes

The degraded (fallback) setpoints are configured with the eSetup tool. The guide does not say how Modbus is switched on or where the communication timeout is set.

Communication loss & watchdog

With the lifebit active (charger writes 1, master resets it to 0), Modbus counts as lost if the master does not refresh it within the configured communication timeout; the charger then limits to the fallback current in 4005 (single-phase) or 4006 (three-phase). Writing 2 to 4000 deactivates the lifebit.

Byte order & addressing

Network setup

Watch out for

Schneider Electric EVlink Pro AC charging station (Modbus TCP) Modbus registers

Address = 0-based wire address (the documented number is shown under it when it differs) · Order: ABCD = high word first, CDAB = low word first · Scale: engineering value = raw × scale.

32 of 32 shown
Schneider Electric EVlink Pro AC charging station (Modbus TCP) Modbus register map
TableAddressNameDescriptionTypeOrderScaleUnitsAccessValues / bits
HR1EV stateControl pilot state of the vehicle plus any detected pilot fault.UINT16Read0 = State E: 0 V; 1 = State F: not available (-12 V); 2 = State A1: available, not ready (12 V); 3 = State B1: EV connected, not ready (9 V); 4 = State C1: charging, stop requested by EVSE (6 V); 5 = State D1: charging with ventilation, stop requested by EVSE (3 V); 6 = State A2: available, ready (12 V PWM); 7 = State B2: EV connected, ready (9 V PWM); 8 = State C2: charging (6 V PWM); 9 = State D2: charging with ventilation (3 V PWM); 10 = Control pilot invalid; 11 = Control pilot symmetric: control circuit fault
HR150OCPP statusCharging station state as reported over OCPP.UINT16Read0 = Init; 1 = Available; 2 = Preparing; 3 = Charging; 4 = SuspendedEV; 5 = SuspendedEVSE; 6 = Finishing; 7 = Reserved; 8 = Unavailable; 9 = Faulted
HR1150EV presenceOnly refreshed while no charge is running.UINT16Read0 = EV not present; 1 = EV present
HR1212Major version digitFirst digit of the overall release version.UINT16Read
HR1213Minor version digitSecond digit of the overall release version.UINT16Read
HR1214Build version digitThird digit of the overall release version.UINT16Read
HR4000LifebitHeartbeat: charger sets 1, master resets to 0; write 2 to switch it off.UINT16Read/write0 = Reset by master; 1 = Set by charger; 2 = Deactivate lifebit
HR4001Set commandRemote command number to execute.UINT16Read/write3 = STOP_CHARGE; 7 = SUSPEND_CHARGE; 8 = RESTART_CHARGE; 9 = REBOOT; 40 = SET_AVAILABLE; 41 = SET_UNAVAILABLE
HR4002Command statusResult of the previous remote command.UINT32ABCDRead
HR4004Set PointCurrent limit from the energy manager, 0-32 A; 99 = never set since start-up.UINT16ARead/write
HR4005Degraded Set Point MonoSingle-phase fallback current used when Modbus is lost.UINT16ARead
HR4006Degraded Set Point TriThree-phase fallback current used when Modbus is lost.UINT16ARead
HR4007Contactor charging timeTime since the contactor closed.UINT32ABCDsRead
HR4009Session charging timeTime since the transaction started.UINT32ABCDsRead
HR4011Last stop causeWhy the last session ended or was refused.UINT16Read0 = None; 1 = EmergencyStop; 2 = EVDisconnected; 3 = HardReset; 4 = Local; 5 = Other; 6 = PowerLoss; 7 = Reboot; 8 = Remote; 9 = SoftReset; 10 = UnlockCommand; 11 = DeAuthorized
HR4012Session energyEnergy delivered in the current session.UINT32ABCDWhRead
HR4020Error group bitfieldOne bit per active error group.UINT32ABCDRead
HR4022Error code bitfieldOne bit per active error code.UINT32ABCDRead
HR4024Last event n°0 - event codeUINT16Read
HR4025Last event n°0 - event start timeThe guide gives the range as seconds.UINT16Read
HR4026Last event n°0 - event end timeThe guide gives the range as seconds.UINT16Read
HR4027Last event n°1 - event codeUINT16Read
HR4028Last event n°1 - event start timeThe guide gives the range as seconds.UINT16Read
HR4029Last event n°1 - event end timeThe guide gives the range as seconds.UINT16Read
HR4030Last event n°2 - event codeUINT16Read
HR4031Last event n°2 - event start timeThe guide gives the range as seconds.UINT16Read
HR4032Last event n°2 - event end timeThe guide gives the range as seconds.UINT16Read
HR4033Last event n°3 - event codeUINT16Read
HR4034Last event n°3 - event start timeThe guide gives the range as seconds.UINT16Read
HR4035Last event n°3 - event end timeThe guide gives the range as seconds.UINT16Read
HR4040doc 4040 ... 4049EVSE ModelModel name, two ASCII characters per register.STRING[20]Read
HR4060doc 4060 ... 4069EVSE Commercial ReferenceCommercial reference, two ASCII characters per register.STRING[20]Read

Notes on this map

Check it against the live device. A register map tells you what the controller can expose; the unit in front of you may differ by firmware or options. Read a few registers and compare them with the unit’s own display; for a 32-bit value the float and byte-order decoder shows all four word orders at once, so a wrong word order or scale is obvious. New to this? Read what a register map is and why addresses are off by one.

Questions about the Schneider Electric EVlink Pro AC charging station (Modbus TCP)

What Modbus registers does the Schneider Electric EVlink Pro AC charging station (Modbus TCP) have?

This map lists 32 registers: 32 holding registers. 3 of them can be written. Registers vary with firmware, options and configuration, so confirm against the device.

Are the Schneider Electric EVlink Pro AC charging station (Modbus TCP) Modbus addresses 0-based or 1-based?

The manufacturer's document numbers registers 0-based (the number printed is the address on the wire). Every address on this page is the 0-based wire address you put in the request; the documented number is shown under it where it differs. The guide says the register table is on base 0, so the printed address goes on the wire unchanged: the current setpoint at 4004 is requested at address 4004.

What byte order does the Schneider Electric EVlink Pro AC charging station (Modbus TCP) use for 32-bit values?

Multi-register values in this map use ABCD (high word first (big-endian)). Set your client to this order for every 32/64-bit value in the table.

What are the minimum Modbus registers to integrate the Schneider Electric EVlink Pro AC charging station (Modbus TCP)?

Start with HR 4004 Set Point (Charging current setpoint); HR 4000 Lifebit (Lifebit heartbeat); HR 1 EV state (Pilot (EV) state); HR 150 OCPP status (OCPP status); HR 4012 Session energy (Session energy); HR 4001 Set command (Remote commands (stop, suspend, restart)).

How do I enable Modbus control of the Schneider Electric EVlink Pro AC charging station (Modbus TCP)?

The degraded (fallback) setpoints are configured with the eSetup tool. The guide does not say how Modbus is switched on or where the communication timeout is set.

What happens when the Schneider Electric EVlink Pro AC charging station (Modbus TCP) loses Modbus communication?

With the lifebit active (charger writes 1, master resets it to 0), Modbus counts as lost if the master does not refresh it within the configured communication timeout; the charger then limits to the fallback current in 4005 (single-phase) or 4006 (three-phase). Writing 2 to 4000 deactivates the lifebit.

Where is the official Schneider Electric EVlink Pro AC charging station (Modbus TCP) Modbus documentation?

The source is EVlink Pro AC Modbus Connectivity Guide (GEX1969300-06), revision 2026-03 (cover date; the revision history lists January 2026), published free by Schneider Electric at https://download.schneider-electric.com/files?p_Doc_Ref=GEX1969300.

More Schneider Electric Modbus register maps

Source: EVlink Pro AC Modbus Connectivity Guide · GEX1969300-06 · rev. 2026-03 (cover date; the revision history lists January 2026). Register numbers, types, scaling and units are reproduced as published; descriptions are our own.