Phoenix Contact EEM-MA370-R

Three-phase energy meter

The EEM-MA370-R (order number 2907980) is the EMpro display meter for external 1 A or 5 A current transformers with an RS-485 port beside the Ethernet port. Phoenix Contact documents Modbus RTU on four RS-485 terminals, factory settings of address 1, 9600 bit/s and even parity, FC03 and FC04 reads, and 32-bit floats sent low word first. Start with the frequency read below, compare it with the display, then add the voltage, current and power registers Phoenix publishes.

Phoenix Contact EMpro EEM-MA370-R DIN-rail energy meter with display, order number 2907980
  • Modbus RTU
  • Modbus TCP
  • HTTP
  • MQTT

Three-phase energy meter

Ask an engineer

Compatibility

Compatible with EpiSensor Edge over Modbus TCP or Modbus RTU

The EEM-MA370-R is compatible with EpiSensor Edge over Modbus RTU, read through a ZMB-31 Modbus Interface or a Gateway serial port, and over Modbus TCP on its Ethernet port. Phoenix Contact documents the RS-485 terminals and factory serial settings, FC03 and FC04 reads, the 32-bit float word order and the process-data addresses used in this guide.

EEM-MA370-R, order number 2907980, using the EMpro online documentation English revision 004 (10 July 2026) as the starting map. Site check: read frequency first and compare it with the display before adding points. Read-only monitoring: no PIN, configuration, mapping-allocation or reset writes.

Connect it with

Route into Edge

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

  • Modbus
  • Wireless
  • Edge
  • Platforms
Three-phase energy meter
Interface
Gateway
Edge
Output
EEM-MA370-REEM-MA370-R RS-485 terminals A+, B- and GND
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 A+, B- and the shield (GND) to the ZMB-31, match the meter's address, baud rate and parity, and read with FC03. Bridge the meter's Ω and A+ terminals to switch in its 120 Ω resistor when it ends the line. If another controller already polls the bus, agree the change with its owner first: Phoenix allows one client per RS-485 network. The customer-platform output is optional; Edge remains the local system of record.

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

  • Modbus
  • Edge
  • Platforms
Three-phase energy meter
Interface
Gateway
Edge
Output
EEM-MA370-REEM-MA370-R RS-485 terminals A+, B- and GND
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
Run a shielded twisted pair in a line topology, give each meter its own address from 1 to 247 and use the same baud rate, parity and stop bits on every meter and in the Edge serial client. Phoenix gives 32 devices (one client and 31 servers) as the typical limit of a line. The customer-platform output is optional; Edge remains the local system of record.

When the meter's Ethernet port X1 is on the local monitoring network

  • Modbus
  • Edge
  • Platforms
Three-phase energy meter
Interface
Gateway
Edge
Output
EEM-MA370-REEM-MA370-R Ethernet port X1
Protected EthernetSegmented LAN
ZGW-20 GatewayHosts Edge locally
EpiSensor EdgeModbus client + register map
Customer platformMQTT · API · files
Modbus TCP
Protected Ethernet
Runs locally
Optional onward data
Add the meter's IP address to the Edge Modbus TCP configuration and read the same registers with FC03; the register map and word order do not change between RTU and TCP. The customer-platform output is optional; Edge remains the local system of record.

Models

Download
ModelsInterfaceRoute into Edge
EEM-MA370-R, order number 2907980Display model for external 1 A or 5 A current transformers; Modbus TCP over RJ45 (X1) and Modbus RTU over RS-485; REST from firmware 1.1.0 and MQTT from firmware 1.7.0RS-485 through a ZMB-31 or the Gateway serial port, or Ethernet Modbus TCP. Start with the frequency read below.
EEM-MA370, order number 2907983Same display meter with Modbus TCP only, no RS-485 portUse the EEM-MA370 guide for the Ethernet route.
EEM-MA371-R, order number 2907985Modbus TCP and Modbus RTU, with Rogowski coil current inputs instead of CT inputsSame communication settings, but do not reuse the EEM-MA370-R current-input assumptions.
EEM-MA390-R, order number 1576552Adds BACnet IP and BACnet MS/TP to Modbus TCP and Modbus RTUTreat as a separate model and confirm which protocol its RS-485 port is set to before reading Modbus RTU.

Specifications

The RS-485 port has four terminals: GND for the shield, B- and A+ for the signal pair, and Ω for the built-in 120 Ω resistor, which is switched in by bridging Ω and A+. It leaves the factory at address 1, 9600 bit/s and even parity with one stop bit, and Modbus RTU is active by default.34

Exact model
EEM-MA370-R, order number 29079801
Voltage
Nominal 100 to 575 V AC phase-phase (57.7 to 333 V AC phase-neutral); measuring range 18 to 690 V AC phase-phase, 11 to 400 V AC phase-neutral; 45 to 65 Hz2
Current
External CT with 1 A or 5 A secondary and a primary from 1 A to 20,000 A; measuring range 0.05% to 120% of In2
Accuracy
Active energy class 0.5 S (IEC 62053-22); reactive energy class 2 (EN 62053-23); active power 0.5% to DIN EN 61557-122
RS-485
Modbus RTU, 2.4 to 115.2 kbit/s; address 1 to 247 (default 1); default 9600 bit/s, even parity, 1 stop bit; terminals GND, B-, A+ and Ω234
Ethernet
100Base-TX RJ45 (X1) with Modbus TCP, REST API and MQTT12
Supply
80 to 276 V AC or 120 to 300 V DC, under 4 W2
Housing and environment
90 × 80 × 64 mm DIN-rail housing; -25 to +70 °C operating; IP20 housing, IP40 display; up to 2,000 m; up to 95% humidity, non-condensing2

Interface

Documented measurements and integration boundaries for EEM-MA370-R.

  • Addresses are the decimal register numbers Phoenix prints, sent as the zero-based PDU address: 32780 is 0x800C. Read with FC03; FC04 returns the same registers.
  • Frequency at 32780 (0x800C): two registers, 32-bit IEEE 754 float, Hz.
  • Total active power at 32790 (0x8016): two registers, 32-bit float.
  • System current at 32825 (0x8039) and system conductor voltage at 32829 (0x803D): two registers each, 32-bit float.
  • Word order: Phoenix calls it little-endian byte swap. The low word is in the first register, each word high byte first (CDAB on the wire): 123.456 (0x42F6E979) arrives as 0xE979 then 0x42F6.
  • Optional mapped block: 125 read-only registers from 57600 (0xE100), filled through allocation registers from 57344 (0xE000) or the web server. Its content depends on that configuration.
  • The complete register table, with units and dividers for every point, is in the product's download area under Application notes, and in the meter's web server register search.
  • Keep writes out of the client: persistent changes need the PIN at 16403 and a 1 written to 16387, which a monitoring client should never send.

Assessment

EEM-MA370-R, order number 2907980, over Modbus RTU or Modbus TCP, using the addresses in the EMpro online documentation English revision 004 and display checks.

InteroperabilitySupported with conditions
Phoenix documents the RS-485 terminals and defaults, FC03 and FC04, the float word order and the main process addresses. Further points come from the full register table in the product download area.3456
AccuracySupported with conditions
Class 0.5 S active energy, 0.2% voltage and current accuracy and continuous gapless measurement are published. The CT ratio set in the meter decides every current, power and energy value.2
SecurityLimited
The RS-485 port allows configuration writes and Modbus has no authentication or encryption. A PIN register guards persistent changes; keep the client read-only and the line physically protected.35
ReliabilitySupported with conditions
Wide AC and DC supply ranges, continuous acquisition and a real-time clock with a power reserve are published. Treat failed or non-finite reads as missing data.2
RuggednessSupported with conditions
Rated -25 to +70 °C, IP20 housing and IP40 display, 1 g vibration and 30 g shock, for installation in a suitable enclosure.2
ScalabilitySupported with conditions
Addresses 1 to 247, a typical 32 devices per RS-485 line and a 125-register mapped block for single-request polling, subject to one client and a bounded poll plan.36
LifecycleSupported with conditions
Phoenix keeps revisioned, dated online documentation and names the firmware versions that add REST and MQTT. Record the installed firmware with the point configuration.12

Setup

Read supply frequency from 32780 over Modbus RTU

The EMpro Modbus mapping page (English revision 004) gives frequency at register 32780 as a 32-bit float, and the register-table page sets the word order. Use it as the starting point and compare the result with the display.

Request
01 03 80 0C 00 02 2D C8: address 1, FC03, start 0x800C, two registers, RTU CRC.
Address convention
32780 is the register number Phoenix prints and is sent as the zero-based PDU address 0x800C. A client that numbers registers from one shows it as 32781; do not add 40001.
Synthetic response
01 03 04 00 00 42 48 CA A5: four data bytes, 00 00 42 48.
Decode
Low word first: 0x0000 then 0x4248 reconstruct 0x42480000, which is 50.0 Hz as an IEEE 754 float. No divider applies.
Acceptance
Keep the point when it agrees with the frequency on the display. If it reads as a tiny or huge number, swap the word order; if the meter does not answer, check the address, parity and termination.

Acceptance: The response bytes are a synthetic decoder check, not a captured meter reply. A real reply must agree with the display before voltage, current and power points are enabled.

  1. Confirm the exact article

    Read EEM-MA370-R and order number 2907980 from the front of the meter. Record the firmware version, serial number and the CT primary and secondary set in the meter.

  2. Read the serial settings without changing them

    Check the Modbus address, baud rate, parity and stop bits on the display or in the web server. The factory settings are address 1, 9600 bit/s, even parity and 1 stop bit. Enter the same values in the Edge serial client or the ZMB-31.

  3. Wire the RS-485 pair

    Connect A+ and B- to the twisted pair and GND to the shield. Bridge Ω and A+ only on the meter at the end of the line. Keep a single Modbus client on the line.

  4. Read frequency first

    Send FC03 to 32780 (0x800C) for two registers and decode the float low word first, as in the worked read below. Compare the result with the frequency on the display.

  5. Add the points you need

    Add system voltage, system current and total active power from the published addresses, then any further points from the full register table, checking each unit and divider. Keep FC06 and FC16 out of the polling configuration.

Common questions

Can Edge read the EEM-MA370-R over Modbus RTU?
Yes. Wire the RS-485 port to a ZMB-31 Modbus Interface or a Gateway serial port, match the serial settings and read with FC03. The same registers are also available over Modbus TCP on the Ethernet port.345
What are the factory serial settings?
Address 1, 9600 bit/s, even parity and 1 stop bit, with Modbus RTU active. The address can be set from 1 to 247 and the speed up to 115,200 bit/s on the display, in the web server or over Modbus.234
Where is the full EEM-MA370-R register table?
Phoenix Contact publishes it in the product's download area under Application notes, and the meter's web server has a register search once it is in service. This guide uses only the addresses Phoenix prints in its online documentation.56
Which word order do the float registers use?
Low word first, with each word high byte first. Phoenix calls this little-endian byte swap; many clients call it CDAB or word-swapped float.5
Can Edge read several values in one request?
Yes. The meter can copy up to 125 registers from different addresses into a read-only block starting at 57600 (0xE100). Set the allocation once in the web server, record it, then poll the block from Edge; keep the individual addresses for troubleshooting.6