Schneider EVlink Wallbox G4 Smart

Use cases

• Monitor real-time charging status, voltage, current, and power per phase on a live cloud dashboard.
• Set current limitations remotely to balance load across multiple EV chargers on a shared grid connection.
• Track cumulative energy consumption per wallbox for cost allocation and billing reports.
• Create alerts when the charging station reports an error status or cable disconnection.
• Start or stop charging sessions remotely using the remote control command register.
• Review historical session data to optimize charger utilization across a parking facility.

Installation

1. 1Connect the Schneider EVlink G4 Smart Wallbox to the same IP network as your ModbusCloud gateway (MCG or MLP series).
2. 2Ensure Modbus TCP is enabled on the wallbox and note its IP address and Modbus TCP port (default is 502).
3. 3Configure the Modbus unit ID on the wallbox if multiple devices share the same network segment.
4. 4In the ModbusCloud portal, add a new device and select the Schneider EVlink Wallbox G4 Smart template from the library.
5. 5Enter the wallbox IP address, port, and unit ID in the gateway configuration and verify the connection.
6. 6Confirm that live values for voltage, current, and charging status appear correctly on the ModbusCloud dashboard.

Things to watch for

01

Why does the energy reading seem extremely high or incorrect?

The energy register at address 356 is a uint32 value expressed in milliwatt-hours (mWh), not kilowatt-hours. Divide by 1,000,000 to convert to kWh. The template applies the correct scaling automatically.

02

Why do voltage and current readings show zero or unexpected values?

Voltage, current, and power registers are Float32 values that span two consecutive Modbus addresses. Ensure your gateway is configured to read both addresses as a single 32-bit float with the correct byte order (big-endian).

03

How do I read the error status correctly?

The error status is split across two registers: the most significant byte is at address 22 and the least significant byte is at address 23. Both registers must be read and combined to get the full error code.

04

The wallbox does not respond to Modbus TCP requests. What should I check?

Verify that Modbus TCP is enabled in the wallbox configuration menu. Confirm the IP address, TCP port (typically 502), and unit ID match the settings in your ModbusCloud gateway. Check that no firewall rules block traffic on the configured port.

Registers (18)

16 read / 2 write

More Schneider Electric GmbH templates

Schneider PowerTag flex-series (1-phase)

Schneider Electric GmbH

Modbus TCP

Reads single-phase energy data from Schneider PowerTag flex-series sensors via Modbus TCP.

4 registers36

Schneider Energy Meter (3-phase) via Modbus RTU

Schneider Electric GmbH

Modbus RTU

Reads 3-phase energy and power data from Schneider Electric meters via Modbus RTU.

24 registers94

Schneider Energy Meter iEM2000-series (1-phase)

Schneider Electric GmbH

Modbus TCP

Reads single-phase energy metering data from Schneider iEM2000-series meters.

13 registers65

Schneider Energy Meter (3-phase) via Modbus TCP

Schneider Electric GmbH

Modbus TCP

Reads 3-phase energy metering data from Schneider Electric meters via Modbus TCP.

24 registers59

Schneider PowerTag (3-phase)

Schneider Electric GmbH

Modbus TCP

Reads three-phase energy and power data from Schneider PowerTag sensors.

15 registers50

More TCP templates

Domekt R 400 V

Komfovent

Modbus TCP

Controls Komfovent Domekt recuperator ventilation via Modbus TCP

25 registers118

Fronius - Modbus TCP

Fronius

Modbus TCP

Monitors Fronius Symo and Primo inverters via Modbus TCP

15 registers597

NIBE Nibe S-Series (SG Ready)

NIBE

Modbus TCP

5 registers1

SunSpec Model 709 — DER Trip LF

SunSpec

Modbus TCP

9 registers

Victron Meter AcOut

Victron

Modbus TCP

16 registers

FoxESS Avocado (grid)

FoxESS

Modbus TCP

8 registers