Schneider Electric EasyLogic EM6400NG+

Power and energy meter

The EasyLogic EM6400NG+ is a three-phase 96 × 96 mm panel meter with a three-line LED display, read through external 1 A or 5 A current transformers. Schneider sells it as the EM6400NG+, while the register list, ION Setup and the meter's own model register call it EM6400NG. Three references (class 1, 0.5S and 0.2) have an RS-485 port running Modbus RTU; two pulse-output references do not. The register list is the one Schneider shares with the PM2100 and PM2200, with its own EM6400 NG column. Start with the one-register product ID read below, then add FLOAT32 current, voltage, power and frequency and the INT64 energy counters.

Schneider Electric EasyLogic EM6400NG+ panel meter
  • Modbus RTU

Power and energy meter

Ask an engineer

Compatibility

Compatible with EpiSensor Edge over Modbus RTU

The EM6400NG+ RS-485 references are compatible with EpiSensor Edge over Modbus RTU, read through a ZMB-31 Modbus Interface or a Gateway serial port. Schneider documents RS-485 Modbus RTU on these references and publishes a register list with an EM6400 NG column, data types, units and a product ID register that identifies the meter.

RS-485 references only (METSEEM6400NGRSCL1, METSEEM6400NGRSCL5 and METSEEM6400NGRSCL2); the METSEEM6400NGPOCL1 and POCL5 have a pulse output instead of RS-485. Register numbers come from Schneider's EM6400 and PM2xxx register list v1050_6. Site check: confirm CoM is set to On, not RTFT (Retrofit), and that the product ID reads 15511 before adding points. Read-only monitoring: no writes to setup or reset registers.

Connect it with

Route into Edge

For a meter in a panel where a wireless link avoids running a data cable back to the Gateway

  • Modbus
  • Wireless
  • Edge
  • Platforms
Power and energy meter
Interface
Gateway
Edge
Output
EasyLogic EM6400NG+EM6400NG+ RS-485 terminals D1 (+) and D0 (-)
ZMB-31Modbus RTU to the EpiSensor wireless network
ZGW-20 GatewayHosts Edge locally
EpiSensor EdgeModbus client + register map
Customer platformMQTT · API · files
Modbus RTU · RS-485
EpiSensor wireless
Runs locally
Optional onward data
Wire the two-wire RS-485 pair from D1 (+) and D0 (-) to the ZMB-31, match the address, baud rate and parity shown on the meter's communication screen, and read the measurement registers with FC03. If another controller already polls the bus, agree the change with its owner first. The customer-platform output is optional; Edge remains the local system of record.

When the Gateway sits near the meter, or several meters share one wired RS-485 bus

  • Modbus
  • Edge
  • Platforms
Power and energy meter
Interface
Gateway
Edge
Output
EasyLogic EM6400NG+EM6400NG+ RS-485 terminals D1 (+) and D0 (-)
Isolated serial interfaceApproved RS-485-to-host adapter
ZGW-20 GatewayHosts Edge locally
EpiSensor EdgeEdge Modbus client
Customer platformMQTT · API · files
Modbus RTU · RS-485
Isolated serial
Runs locally
Optional onward data
Give each meter on the bus its own address, use the same baud rate and parity on every meter and in the Edge serial client, and stay within 32 devices on the segment. Schneider documents RS-485 Modbus RTU only; the EM6400NG+ has no Ethernet or Modbus TCP port. The customer-platform output is optional; Edge remains the local system of record.

Models

Download
ModelsInterfaceRoute into Edge
METSEEM6400NGRSCL1RS-485 Modbus RTU; class 1 active energy; real-time clock; odd harmonics to the 15thRead the EM6400 NG column of the register list with FC03. Product ID 15511.
METSEEM6400NGRSCL5RS-485 Modbus RTU; class 0.5S active energy; real-time clock; odd harmonics to the 15thSame register list, read path and product ID as the class 1 meter.
METSEEM6400NGRSCL2RS-485 Modbus RTU; class 0.2 active energy; real-time clock; odd harmonics to the 15thSame register list, read path and product ID as the class 1 meter.
METSEEM6400NGPOCL1 and METSEEM6400NGPOCL5Energy pulse output on D1 (+) and D0 (-), 40 V DC and 20 mA maximum; no RS-485No Modbus path. Only the energy pulse output is available.

Specifications

The EM6400NG+ is a compact 96 × 96 mm panel meter with a three-line LED display and three buttons, reading its currents through external CTs. Three of the five commercial references carry an RS-485 Modbus RTU port, so the first job on site is to read the commercial reference on the label or the meter model on the Diag screen.12

References with Modbus
METSEEM6400NGRSCL1 (class 1), METSEEM6400NGRSCL5 (class 0.5S) and METSEEM6400NGRSCL2 (class 0.2); METSEEM6400NGPOCL1 and POCL5 have a pulse output only12
Current inputs
1 A or 5 A CT secondary; CT primary 1 to 32767 A; starting current 5 mA; 12 A continuous withstand1
Voltage inputs
35 to 480 V L-L (277 V L-N) at CAT III, up to 600 V L-L (347 V L-N) at CAT II; use VTs above the direct-connect limit12
Meter accuracy
Active energy class 1, 0.5S or 0.2 by reference (IEC 62053-21 and IEC 62053-22) at 5 A nominal CTs. For reactive energy the manual's feature summary gives class 2.0 on the class 1 references and 1.0 on the class 0.5S references, while its specification tables give class 2 to IEC 62053-23 (±1%) for every reference. IEC 61557-12 PMD classes apply from firmware 1.3.0. The installed CTs and wiring add their own error.12
RS-485
Two-wire on D1 (+) and D0 (-); 4800, 9600, 19200 or 38400 baud; even, odd or no parity (two stop bits with none); address 1 to 247; up to 32 devices and 900 m; straight-line topology; 2.5 kV RMS isolation12
Serial defaults
The user manual gives Modbus RTU, address 1, 19200 baud and even parity. The shared register list shows 9600 baud as its default code, so read the installed values on the meter.13
Housing
96 × 96 × 73 mm maximum, about 600 g, panel up to 6 mm thick, vertical mounting1
Control power
44 to 277 V AC or DC ± 10%; 45 to 65 Hz on AC12
Environment
-10 to 60 °C operating; 5% to 95% RH non-condensing; front IP51 (IP54 or IP65 with an optional gasket kit), body IP30; indoor only, not for wet locations12
Unavailable values
FLOAT32 0xFFC00000; INT64 0x80000000000000003

Interface

Documented measurements and integration boundaries for EasyLogic EM6400NG+.

  • Product ID at register 90: INT16U, one register; 15511 on an EM6400NG with RS-485. The model register at 50 holds the text EM6400NG.
  • Current A, B and C at registers 3000, 3002 and 3004, neutral at 3006 and average at 3010: FLOAT32, two registers each, in A. The manual states that the meter calculates neutral current rather than measuring it.
  • Voltage A-B, B-C and C-A at 3020, 3022 and 3024 with the average at 3026; A-N, B-N and C-N at 3028, 3030 and 3032 with the average at 3036: FLOAT32 in V. Line-to-neutral values are reported only where the wiring connects them.
  • Active power A, B and C at 3054, 3056 and 3058, total at 3060: FLOAT32 in kW. Reactive power A to total at 3062 to 3068 in kVAR, apparent power A to total at 3070 to 3076 in kVA.
  • Power factor A, B, C and total at 3078 to 3084 in Schneider's four-quadrant encoding (range -2 to 2). Register 3192 holds the total as a plain FLOAT32 from -1 to 1, marked IEC standard in the register list; 3194 is the IEEE form.
  • Frequency at 3110: FLOAT32 in Hz, range 42 to 70.
  • Active energy delivered (into the load) at 3204 and received at 3208: INT64, four registers, in Wh. Reactive energy delivered at 3220 in VARh and apparent energy delivered at 3236 in VAh. FLOAT32 copies in kWh start at 2700 (delivered) and 2702 (received).
  • Present active power demand at 3766 and peak demand at 3770: FLOAT32 in kW. THD of current A, B and C at 21300, 21302 and 21304 and of voltage A-N, B-N and C-N at 21330, 21332 and 21334: FLOAT32 in %.
  • Unavailable data reads 0xFFC00000 for FLOAT32 and 0x8000000000000000 for INT64; record it as missing, not zero.
  • Communication settings sit at 6500 to 6503 and the power system, VT and CT setup at 2016 to 2031. The register list marks them RWC: they change only through Schneider's command interface. Keep them out of a monitoring poll.

Assessment

RS-485 references only (METSEEM6400NGRSCL1, METSEEM6400NGRSCL5 and METSEEM6400NGRSCL2); the METSEEM6400NGPOCL1 and POCL5 have a pulse output instead of RS-485. Register numbers come from Schneider's EM6400 and PM2xxx register list v1050_6. Site check: confirm CoM is set to On, not RTFT (Retrofit), and that the product ID reads 15511 before adding points. Read-only monitoring: no writes to setup or reset registers.

InteroperabilityWell supported
Schneider documents RS-485 Modbus RTU on the three RS-485 references and publishes a register list with an EM6400 NG column, data types, units, unavailable-value codes and a product ID register.13
AccuracySupported with conditions
Class 1, 0.5S or 0.2 active energy by reference with 1 A or 5 A CTs, four-quadrant energy, demand and odd harmonics to the 15th; system accuracy depends on the CTs, ratios and wiring, and neutral current is calculated.12
SecurityLimited
Modbus RTU carries no authentication. In the register list, Basic Meter Setup (command 2000, which sets the power system, VT and CT values) takes only a command semaphore as its first parameter, with no password, so any master on the segment can reconfigure the meter. The front-panel password (default 0000, to be changed) protects the keypad, and the RS-485 port can be switched off from the front panel. Keep the serial segment inside the panel and the poll read-only.13
ReliabilitySupported with conditions
The manual publishes control-power ride-through times, non-volatile energy storage, the IEC 61000-4 immunity tests and diagnostic and Modbus error codes on the display; communication loss still needs explicit stale-data handling.1
RuggednessSupported with conditions
Rated -10 to 60 °C with an IP51 front and IP30 body, for indoor panels only and not wet locations.12
ScalabilitySupported with conditions
Modbus addresses 1 to 247, up to 32 devices per segment, up to 38400 baud and 900 m; capacity depends on the cable run and poll schedule.1
LifecycleNot yet assessed
A May 2022 manual revision, a public register list, firmware upgrades over RS-485 with DLF3000 and a firmware version shown on the display. No support period is stated.13

Setup

Read the EM6400NG product ID, then frequency

The identity read needs no floating-point or word-order decision. Schneider's EM6400 and PM2xxx register list v1050_6 gives Product ID Number at register 90 as INT16U, with 15511 for the EM6400NG with communication, and Frequency at register 3110 as FLOAT32 in Hz. The list gives register numbers and states neither the address offset nor the word order. The frames below assume the register number minus one; if 15511 does not come back, send 0x005A for the product ID and 0x0C26 for frequency. These two reads settle both questions.

Function
FC03 Read Holding Registers
Address convention
Assumed, not stated in the register list: register 90 sent as zero-based PDU address 89 (0x0059). If that read does not return 15511, send 0x005A (90): request 01 03 00 5A 00 01 A4 19. A client that takes one-based register numbers subtracts one itself, so enter 90 there.
Product ID request
01 03 00 59 00 01 54 19: unit address 1, FC03, address 0x0059, one register, RTU CRC.
Product ID response
01 03 02 3C 97 E8 EA: two data bytes, 3C 97 = 15511, unsigned 16-bit, no multiplier.
Frequency request
01 03 0C 25 00 02 D6 90: register 3110 at address 3109 (0x0C25), two registers. With the 0x005A offset, send 01 03 0C 26 00 02 26 90.
Frequency decode
01 03 04 42 47 EB 85 D1 0D: data 42 47 EB 85 read high word first is IEEE 754 0x4247EB85 = 49.98 Hz. With the words swapped the same bytes read as 0xEB854247, about -3.2 × 10²⁶, an implausible value that means the client's word order is reversed.
Acceptance
15511 must agree with EM6400NG on the Diag meter model screen, and the frequency must match the frequency page of the display. If neither 0x0059 nor 0x005A returns 15511, check the unit address and the CoM setting before reading measurements.

Acceptance: 15511 confirms the meter and the address offset, and a frequency near 50 Hz (49.98 Hz here) confirms the FLOAT32 word order. These are expected responses worked from the register list, not captured meter transactions. Continue with current, voltage, power and energy, comparing each with the display.

  1. Identify the reference and firmware

    Read the commercial reference on the label: only METSEEM6400NGRSCL1, RSCL5 and RSCL2 have RS-485. Hold Down and OK for 2 seconds to open Diag and record the meter model, serial number and OS version. Confirm the power system, CT ratio and any VT ratio with the installer.

  2. Read the serial settings

    The Diag communication screen shows the unit ID, baud rate and parity. Check in Setup that CoM is On, not OFF or RTFT (Retrofit, which switches the port to a legacy data model). The manual gives address 1, 19200 baud and even parity as defaults; with no parity the meter uses two stop bits. Set the Edge serial client or the ZMB-31 to the installed values.

  3. Wire the RS-485 segment

    Connect D1 (+) and D0 (-) with shielded twisted pair in a straight line with no loop or ring, and ground the shield at one end only. Fit a 120 Ω, 0.5 W terminator at the ends of the segment where needed, and stay within 900 m and 32 devices.

  4. Read the product ID

    Send one FC03 read of register 90. The register list does not state the address offset, so start with zero-based PDU address 89 (0x0059), the register number minus one. Expect 15511; if that read does not return it, send 0x005A (90) instead and use the register numbers unchanged from then on.

  5. Add frequency, then the measurements

    Read frequency at register 3110 as two registers (0x0C25 if the product ID answered at 0x0059, 0x0C26 if it answered at 0x005A) and decode one FLOAT32. It must land near 50 or 60 Hz; use it to settle the word order, because the register list does not state one. Then add current at 3000, voltage at 3020 or 3028, total active power at 3060 in kW and energy at 3204 as INT64 Wh, with the same offset, comparing each with the display.

  6. Keep the poll read-only

    Communication, setup and reset values change through Schneider's command interface. Leave those registers out of the Edge poll, and change the default 0000 password, as the manual recommends, so the meter cannot be reconfigured from the front panel without it.

Common questions

Can every EM6400NG+ be read over Modbus?
No. Schneider lists five references. METSEEM6400NGRSCL1, RSCL5 and RSCL2 have RS-485 Modbus RTU; METSEEM6400NGPOCL1 and POCL5 use the same two terminals as a pulse output and have no Modbus port.12
Is the EM6400NG+ register list the same as the EM6400NG list?
Schneider publishes one register list for the EM6400, PM2100 and PM2200 with a column for the EM6400 NG, attached to an FAQ for the METSEEM6400NGRSCL2. The meter's model register reads EM6400NG and ION Setup calls it the EM6400NG series, so use that column for the RS-485 references named here.13
Is register 3110 the address sent on the bus?
The register list gives register numbers and does not state the offset. Start with 3109 (0x0C25), the register number minus one. The product ID read shows which convention your meter and client use: if 15511 comes back only at 0x005A rather than 0x0059, send 3110 (0x0C26) for frequency and use every register number unchanged.3
What does RTFT (Retrofit) change?
On the RS-485 references, the CoM setting has On, OFF and RTFT. Retrofit switches the port to a legacy communication data model. The register numbers on this page come from Schneider's current EM6400 and PM2xxx list, so CoM must be On.12
Which energy register should I log?
Active energy delivered at 3204 is a four-register INT64 in Wh; 2700 is a two-register FLOAT32 copy in kWh, which keeps only about seven significant digits. Use the INT64 for totals. The manual notes that every energy value resets when any of them overflows at 999999999.999 on the selected energy scale, so handle a sudden drop as a reset.13
Does the EM6400NG+ have Modbus TCP?
No. Schneider documents one RS-485 port running Modbus RTU. Edge reads it through a ZMB-31 Modbus Interface or a Gateway serial port.1
Does class 0.2 describe the whole installation?
It is the METSEEM6400NGRSCL2's stated active-energy class at 5 A nominal CTs. CT accuracy and ratio, wiring and the measurement boundary all affect the system result.1