Phoenix Contact EEM-MA370

Compatibility

Direct Edge integration not yet verified

Phoenix Contact's exact-model documentation identifies Modbus/TCP and publishes an example of the configurable process-data map. The retained pages do not contain the complete register table, supported function-code contract or unavailable-value rules required for a released Edge point set.

EEM-MA370 order number 2907983 only. Obtain and retain the complete firmware-matched register table, confirm the server role and read semantics, and validate the installed CT and voltage configuration before proposing an Edge route. Do not apply this guide to EEM-MA370-R, EEM-MA371 or EEM-MA390 variants.

Models

Specifications

Phoenix Contact identifies order number 2907983 as the EEM-MA370 display model with current-transformer inputs and Modbus/TCP. The -R and 24 V DC variants have different interface or supply contracts and must be identified separately.¹

Measurement

Three-phase voltage and external 1 A or 5 A CT current inputs; continuous simultaneous acquisition²

Voltage range

18 to 690 V AC phase-phase and 11 to 400 V AC phase-neutral²

Current range

External CT primary from 1 A to 20,000 A with 1 A or 5 A secondary²

Energy accuracy

Active energy class 0.5 S under IEC 62053-22; reactive energy class 2 under IEC 62053-23²

Ethernet

100Base-TX RJ45 with Modbus/TCP, REST API and firmware-dependent MQTT^1, 2

Environment

-25 to +70 degrees Celsius; IP20 housing and IP40 display; up to 2,000 m altitude²

Interface

Documented measurements and integration boundaries for EEM-MA370.

• Potential voltage, current, frequency, active-power and energy points require the complete firmware-matched register table before publication.
• Keep raw meter values, CT configuration, derived intervals and any upstream settlement totals as separate records.
• The configurable 125-register process-data area is a device mapping feature, not proof that every source register is safe or available on the installed firmware.
• No relay output, MQTT command, configuration register or reset operation is approved by this guide.

Setup

1. Confirm the exact article

   Record EEM-MA370 and order number 2907983 from the device. Capture firmware, serial number, supply variant and Ethernet configuration.

2. Record the measurement circuit

   Document voltage wiring, CT primary and secondary ratings, CT polarity and phase assignment. Verify the configured values against the installation drawings.

3. Obtain the complete interface contract

   Retain the firmware-matched Phoenix Contact register table with supported function codes, addresses, data types, units and invalid-value behavior.

4. Keep the allocation area outside monitoring

   The configurable process map uses a writable allocation block. Do not let the monitoring client alter mapping, network, meter or output configuration.

5. Prove a bounded read path

   Validate identity and one electrical value against the simultaneous display before expanding the point set. Reconcile power and energy under a known load.

Common questions

Can Edge read the EEM-MA370 over Modbus TCP?

The exact model publishes Modbus/TCP and a configurable process-data map, but this guide does not release a direct Edge path. The complete firmware-matched register table and read contract still need to be retained and commissioned.^1, 3

Is the EEM-MA370-R the same integration?

No. The -R variant adds Modbus RTU, while order number 2907983 covered here is the Modbus/TCP display model. Identify the exact order number before designing the network.¹

Does class 0.5 S make the Edge record suitable for billing?

No. The meter specification describes the instrument. A copied or calculated Edge series does not inherit an approved revenue or settlement role.²

Can Edge configure the 125-register mapped area?

This guide excludes all writes. Phoenix Contact separates the read-only mapped area from its writable allocation area. Any mapping change belongs to a controlled commissioning process outside the monitoring client.³