Schneider Electric Schneider Electric EVlink Pro AC Modbus TCP template

Schneider Electric EVlink Pro AC

AC charging station with charging state, power, energy and a remote current setpoint.

The Schneider Electric EVlink Pro AC is an AC charging station that charges electric cars at offices, car parks and fleet sites. This Modbus TCP template reads charging state, OCPP status, power, current, energy and errors, and lets you set the charging current and send start and stop commands from ModbusCloud.

Protocol
Modbus TCP
Connection
Ethernet, Modbus TCP
Registers
50, read and write
Key readings
Charging state · OCPP status · Current per phase · Active power · Active energy · Session energy · Session charging time
Available commands
Current setpoint · Charge command · Lifebit
Compatible models
EVlink Pro AC · Schneider Electric EVlink Pro AC with T2S socket · Schneider Electric EVlink Pro AC with attached cable · Schneider Electric EVlink Pro AC with T2S and domestic socket
Last updated

Registers (50)

50 read, 3 write

NameUnitAccessAddress (Hidden until you enter your email)Function (hidden)Type (hidden)
Current Phase 1ARead2999FC03float32
Current Phase 2ARead3001FC03float32
Current Phase 3ARead3003FC03float32
Current AverageARead3009FC03float32
Voltage Phase 1VRead3027FC03float32
Voltage Phase 2VRead
Voltage Phase 3VRead
Voltage AverageVRead
Active Power Phase 1kWRead
Active Power Phase 2kWRead
Active Power Phase 3kWRead
Active Power TotalkWRead
Reactive Power TotalkvarRead
Apparent Power TotalkVARead
Power FactorRead
FrequencyHzRead
Active Energy TotalWhRead
Reactive Energy TotalkvarhRead
Session EnergyWhRead
EV StateRead
OCPP StatusRead
EV PresenceRead
Last Stop CauseRead
Error Group BitfieldRead
Error Code BitfieldRead
Last Event 0 CodeRead
Last Event 0 Start TimesRead
Last Event 0 End TimesRead
Last Event 1 CodeRead
Last Event 1 Start TimesRead
Last Event 1 End TimesRead
Last Event 2 CodeRead
Last Event 2 Start TimesRead
Last Event 2 End TimesRead
Last Event 3 CodeRead
Last Event 3 Start TimesRead
Last Event 3 End TimesRead
Contactor Charging TimesRead
Session Charging TimesRead
Set PointARead and write
Degraded Set Point Single PhaseARead
Degraded Set Point Three PhaseARead
LifebitRead and write
Set CommandRead and write
Command StatusRead
Firmware Major VersionRead
Firmware Minor VersionRead
Firmware Build VersionRead
EVSE ModelRead
EVSE Commercial ReferenceRead

Loading registers…

The ModbusCloud Gateway, front at an angle, with the RS485 terminal and the antenna connectors

Send your device list

If a device is not in the library yet, we build the template for free as soon as we have the register data.

Use cases

  • Show charging state, power and session energy of every charging station on a ModbusCloud dashboard.
  • Lower the current setpoint of a charging station from ModbusCloud when the building connection is near its limit.
  • Get an email when the OCPP status changes to Faulted or the error bitfield is not zero.
  • Keep a year of energy history per charging station to report consumption per car park or tenant.
  • Use an automation to switch a charging station unavailable outside office hours.

Installation

  1. Connect the Ethernet port of the charging station to the same network as the ModbusCloud Gateway and give it a fixed IP address.

  2. Enable the Modbus interface with eSetup and set the communication timeout and the degraded setpoints for single and three-phase charging.

  3. In ModbusCloud, add a Modbus TCP device on the Gateway with the IP address of the station, port 502 and unit ID 255, and choose the EVlink Pro AC template.

  4. Check that OCPP status and EV state show plausible values and that current and power rise when a car charges.

Things to watch for

Why does the charging station not answer Modbus requests?

Check that Modbus is enabled in eSetup, that the station and the Gateway are in the same network and that the unit ID is 255. Reading an address that is not in the register list returns an illegal data address exception, so use the template addresses unchanged.

Why does the station fall back to a low charging current?

When the lifebit is active and not refreshed within the communication timeout, the station treats Modbus as lost and applies the degraded setpoint from eSetup. Write the lifebit regularly, or write 2 to switch the lifebit off.

How do I set the charging current from ModbusCloud?

Write the current in amperes, 0 to 32, to the setpoint register. The station applies a change within 15 seconds. The value 99 means no setpoint was set by Modbus. Writing to a station needs remote control enabled for the gateway in ModbusCloud.

Why do some registers return 65535?

Some register ranges are reserved, and reading them returns 0xFFFF. Values that only change during a session, such as EV presence, are updated only when the station is not charging.

Want to see how it works?

Electrician working in an open distribution board