- Home
- Modbus register maps
- Schneider Electric
- 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
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
Integration notes: Schneider Electric EVlink Pro AC charging station (Modbus TCP)
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.
| Register | Name | Type | Why | Access |
|---|---|---|---|---|
| HR 4004 | Set Point | UINT16 | Charging current setpoint | Read/write |
| HR 4000 | Lifebit | UINT16 | Lifebit heartbeat | Read/write |
| HR 1 | EV state | UINT16 | Pilot (EV) state | Read |
| HR 150 | OCPP status | UINT16 | OCPP status | Read |
| HR 4012 | Session energy | UINT32 ABCD | Session energy | Read |
| HR 4001 | Set command | UINT16 | Remote 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
- 4004 reads 99 until a Modbus master has written a setpoint since start-up.
- A setpoint change can take up to 15 s to take effect.
Network setup
- Use unit (server) ID 255.
- Addresses are 0-based (the table is on base 0).
Watch out for
- Firmware older than software 1.2.1 (guide revision 02) has addresses 1211-1213 and 4003-4011 one lower.
- The lifetime energy counters (3203/3219) are int64 with an unstated word layout, so they are not in this map.
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.
| Table | Address | Name | Description | Type | Order | Scale | Units | Access | Values / bits |
|---|---|---|---|---|---|---|---|---|---|
| HR | 1 | EV state | Control pilot state of the vehicle plus any detected pilot fault. | UINT16 | Read | 0 = 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 | |||
| HR | 150 | OCPP status | Charging station state as reported over OCPP. | UINT16 | Read | 0 = Init; 1 = Available; 2 = Preparing; 3 = Charging; 4 = SuspendedEV; 5 = SuspendedEVSE; 6 = Finishing; 7 = Reserved; 8 = Unavailable; 9 = Faulted | |||
| HR | 1150 | EV presence | Only refreshed while no charge is running. | UINT16 | Read | 0 = EV not present; 1 = EV present | |||
| HR | 1212 | Major version digit | First digit of the overall release version. | UINT16 | Read | ||||
| HR | 1213 | Minor version digit | Second digit of the overall release version. | UINT16 | Read | ||||
| HR | 1214 | Build version digit | Third digit of the overall release version. | UINT16 | Read | ||||
| HR | 4000 | Lifebit | Heartbeat: charger sets 1, master resets to 0; write 2 to switch it off. | UINT16 | Read/write | 0 = Reset by master; 1 = Set by charger; 2 = Deactivate lifebit | |||
| HR | 4001 | Set command | Remote command number to execute. | UINT16 | Read/write | 3 = STOP_CHARGE; 7 = SUSPEND_CHARGE; 8 = RESTART_CHARGE; 9 = REBOOT; 40 = SET_AVAILABLE; 41 = SET_UNAVAILABLE | |||
| HR | 4002 | Command status | Result of the previous remote command. | UINT32 | ABCD | Read | |||
| HR | 4004 | Set Point | Current limit from the energy manager, 0-32 A; 99 = never set since start-up. | UINT16 | A | Read/write | |||
| HR | 4005 | Degraded Set Point Mono | Single-phase fallback current used when Modbus is lost. | UINT16 | A | Read | |||
| HR | 4006 | Degraded Set Point Tri | Three-phase fallback current used when Modbus is lost. | UINT16 | A | Read | |||
| HR | 4007 | Contactor charging time | Time since the contactor closed. | UINT32 | ABCD | s | Read | ||
| HR | 4009 | Session charging time | Time since the transaction started. | UINT32 | ABCD | s | Read | ||
| HR | 4011 | Last stop cause | Why the last session ended or was refused. | UINT16 | Read | 0 = None; 1 = EmergencyStop; 2 = EVDisconnected; 3 = HardReset; 4 = Local; 5 = Other; 6 = PowerLoss; 7 = Reboot; 8 = Remote; 9 = SoftReset; 10 = UnlockCommand; 11 = DeAuthorized | |||
| HR | 4012 | Session energy | Energy delivered in the current session. | UINT32 | ABCD | Wh | Read | ||
| HR | 4020 | Error group bitfield | One bit per active error group. | UINT32 | ABCD | Read | |||
| HR | 4022 | Error code bitfield | One bit per active error code. | UINT32 | ABCD | Read | |||
| HR | 4024 | Last event n°0 - event code | UINT16 | Read | |||||
| HR | 4025 | Last event n°0 - event start time | The guide gives the range as seconds. | UINT16 | Read | ||||
| HR | 4026 | Last event n°0 - event end time | The guide gives the range as seconds. | UINT16 | Read | ||||
| HR | 4027 | Last event n°1 - event code | UINT16 | Read | |||||
| HR | 4028 | Last event n°1 - event start time | The guide gives the range as seconds. | UINT16 | Read | ||||
| HR | 4029 | Last event n°1 - event end time | The guide gives the range as seconds. | UINT16 | Read | ||||
| HR | 4030 | Last event n°2 - event code | UINT16 | Read | |||||
| HR | 4031 | Last event n°2 - event start time | The guide gives the range as seconds. | UINT16 | Read | ||||
| HR | 4032 | Last event n°2 - event end time | The guide gives the range as seconds. | UINT16 | Read | ||||
| HR | 4033 | Last event n°3 - event code | UINT16 | Read | |||||
| HR | 4034 | Last event n°3 - event start time | The guide gives the range as seconds. | UINT16 | Read | ||||
| HR | 4035 | Last event n°3 - event end time | The guide gives the range as seconds. | UINT16 | Read | ||||
| HR | 4040doc 4040 ... 4049 | EVSE Model | Model name, two ASCII characters per register. | STRING[20] | Read | ||||
| HR | 4060doc 4060 ... 4069 | EVSE Commercial Reference | Commercial reference, two ASCII characters per register. | STRING[20] | Read |
Notes on this map
- Word order: the guide's data-format table defines UINT32 as U32-4321 (high word in the first register), so the uint32 registers are mapped high word first (ABCD).
- Left out: the per-phase float32 measurements at 2999-3109 (currents, voltages, active/reactive/apparent power, power factor, frequency). The format table defines both IEEEFloat (F32-4321, high word first) and SwappedFloat (F32-2143) but never says which one the register table's float32 means, so the word order is not stated.
- Left out: Energy Active TOT (3203, Wh) and Energy Reactive TOT (3219, kVARh). They are typed int64, and the format table defines two 64-bit layouts (S64-87-21 and S64-21-87) without saying which one int64 means.
- The guide's text says the fallback currents are set by writing 4005 and 4006, but the register table marks both read-only and says they are configured in eSetup. They are kept read-only here.
- Revision 02 of the guide (March 2023, software 1.2.1) moved addresses 1211-1213 and 4003-4011 up by one; older firmware may still use the old numbers.
- The register page says reading an address not in the table returns Illegal data address, while the revision history (revision 04) says reads inside the reserved ranges 2999-3222 and 4000-4079 return 0xFFFF.
- Error codes 1.1 to 19.0 and their OCPP equivalents are listed on printed pp. 15-16; the bitfields at 4020/4022 flag the active ones (bit assignment not given).
- All values are refreshed once per second.
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
- Energy meter (pulse and status concentrator)
Schneider Electric Acti 9 Smartlink Modbus (A9XMSB11) 11-channel I/O and pulse concentrator
Acti 9 Smartlink Modbus RS-485 module A9XMSB11, per user manual DOCA0004EN-06 (04/2016).
Also known as: Acti 9 Smartlink, Smartlink Modbus, A9XMSB11, Acti9 Smartlink - Variable frequency drive (HVAC fans and pumps)
Schneider Electric Altivar 212 (embedded Modbus RTU)
ATV212H (IP21) and ATV212W (IP55) drives on the built-in Modbus RTU ports (RJ45 and open-style terminal), per Modbus manual S1A53844.
Also known as: ATV212, Altivar 212, ATV212H, ATV212W, ATV212HU15N4, ATV212WD11N4 - Variable frequency drive
Schneider Electric Altivar Machine ATV320 (embedded Modbus RTU)
ATV320 Book (ATV320...B) and Compact (ATV320...C) drives on the built-in RJ45 Modbus serial port; register map per Communication Parameters file NVE41316 V3.5.
Also known as: ATV320, Altivar 320, ATV320U, ATV320D, ATV320 Book, ATV320 Compact - Variable frequency drive
Schneider Electric Altivar Machine ATV340 (embedded Modbus serial / Modbus TCP)
ATV340 drives on the built-in Modbus serial port; Ethernet versions (ATV340...N4E) expose the same addresses on embedded Modbus TCP. Per Communication Parameters file NVE61728 V4.6.
Also known as: ATV340, Altivar 340, Altivar Machine ATV340, ATV340U, ATV340D, ATV340...N4E - Variable frequency drive
Schneider Electric Altivar Process ATV630 / ATV600 family (Modbus serial and Modbus TCP)
Altivar Process ATV600 drives (ATV630, ATV650 and other ATV6x0 models) on the embedded RJ45 Modbus serial port or the embedded Ethernet Modbus TCP server; register map per Communication Parameters file EAV64332 V4.6.
Also known as: ATV600, ATV630, ATV650, ATV660, ATV680, Altivar Process 600, ATV630U, ATV630D - Variable frequency drive
Schneider Electric Altivar Process ATV900 (ATV930/ATV950, embedded Modbus serial / Modbus TCP)
Altivar Process ATV900 drives (ATV930, ATV950) on the built-in Modbus serial port and the embedded Ethernet port (Modbus TCP). Per Communication Parameters file NHA80944 V4.6.
Also known as: ATV900, ATV930, ATV950, Altivar Process 900, Altivar 930, Altivar 950, ATV930U, ATV930D, ATV950U - Power meter (circuit breaker trip unit)
Schneider Electric ComPact NSX MicroLogic trip unit, standard dataset (IFM / IFE interface)
Standard dataset registers 32000-32341 served by the IFM (Modbus RTU) or IFE (Modbus TCP) interface for ComPact NSX; the same table lists availability for ComPact NS / MasterPact NT/NW and MasterPact MTZ. Per DOCA0091EN-09 (07/2022).
Also known as: ComPact NSX, Compact NSX, MicroLogic 5.2 E, MicroLogic 6.2 E, MicroLogic 7.2 E, MicroLogic 5.3 A, MicroLogic 6.3 E, IFM LV434000, IFE LV434001, IFE LV434002, ComPact NS, MasterPact NT, MasterPact NW, MasterPact MTZ - Solar inverter
Schneider Electric Conext CL three-phase PV inverter 18/20/25 kVA
Conext CL (IEC, PVSCL20E/25E) and Conext CL-NA (PVSCL18NA/25NA) three-phase string inverters, map revision 1.5.
Also known as: Conext CL-NA, Conext CL-E, PVSCL18NA, PVSCL20E, PVSCL25E, PVSCL25NA - Solar inverter
Schneider Electric Conext Core XC Series grid-tie PV inverter (0G-XC-BB)
Conext Core XC Series grid-tied PV inverters (540/630/680 kW ratings, 0G-XC-BB) with firmware v1.07 and later; some registers need newer firmware as noted.
Also known as: 0G-XC-BB, XC-AIC15P - Variable frequency drive
Schneider Electric Easy Altivar ATV610 (embedded Modbus serial)
Easy Altivar ATV610 drives on the built-in Modbus serial port, per Communication Parameters file EAV64394 V1.6.
Also known as: ATV610, Altivar 610, Easy Altivar 610, Altivar Easy 610, ATV610U, ATV610D - Energy meter (wireless sensors through an Ethernet gateway)
Schneider Electric PowerTag Energy wireless sensors via PowerTag Link gateway (Modbus TCP)
PowerTag Energy 63, M250/M630, F160 and Rope sensors read through a PowerTag Link or PowerTag Link HD gateway, per DOCA0157EN-09 (10/2025).
Also known as: PowerTag Link, PowerTag Link HD, A9XMWD20, A9XMWD100, PowerTag Energy 63, A9MEM1520, A9MEM1540, A9MEM1560, A9MEM1570, PowerTag M250, PowerTag M630, LV434020, PowerTag F160, A9MEM1580, PowerTag Rope, A9MEM1590 - Motor management and protection relay
Schneider Electric TeSys T LTMR motor management controller (Modbus RTU)
TeSys T LTMR Modbus controllers (LTMR..M..), with or without the LTMEV40 expansion module, per DOCA0130EN-03 (02/2024).
Also known as: TeSys T, LTMR, LTMR08MBD, LTMR27MBD, LTMR100MBD, LTMR08MFM, LTMR27MFM, LTMR100MFM, LTMR..M, LTMEV40 - Air handler (rack-mounted room cooling unit, split DX)
Schneider Electric Uniflair Rack Mounted Room Cooling ACRMD4K
Schneider Electric Uniflair Rack Mounted Room Cooling units ACRMD4Kxxx (indoor rack unit with matching outdoor unit), register map part number 990-91589.
Also known as: ACRMD4K, ACRMD4Kxxx, Uniflair rack mounted room cooling, 990-91589
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.