PhoenixContact PhoenixContact PhoenixContact Modbus TCP template

PhoenixContact PhoenixContact

The PhoenixContact EMpro is a multifunctional energy measuring device for low-voltage installations, used in control cabinets and industrial or commercial buildings to meter three-phase electrical parameters. This Modbus TCP template reads per-phase voltages (L1, L2, L3), per-phase and total currents, per-phase and total active power, grid frequency, and cumulative consumption and production energy totals. With all 15 registers flowing into the ModbusCloud portal, operators can trend load profiles, spot phase imbalances, and verify energy balances across sites from a single dashboard.

Protocol
Modbus TCP
Connection
Ethernet, Modbus TCP
Registers
15, read only
Last updated

Registers (15)

15 read, 0 write

NameUnitAccessAddress (Hidden until you enter your email)Function (hidden)Type (hidden)
voltage_l1VRead
voltage_l2VRead
voltage_l3VRead
frequencyHzRead
current_l1ARead
current_l2ARead
current_l3ARead
currentARead
active_powerWRead
active_power_l1WRead
active_power_l2WRead
active_power_l3WRead
voltageVRead
active_consumption_energyWhRead
active_production_energyWhRead

Loading registers…

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.

Number of installations (optional)

Use cases

  • Monitor total active power and per-phase power to detect load imbalances across L1, L2, and L3.
  • Track cumulative consumption energy over time to validate utility bills and identify unexpected usage spikes.
  • Alert on grid frequency deviations to flag grid instability events at a site in near real time.
  • Compare active production energy against consumption energy to verify net metering accuracy on PV installations.
  • Report per-phase voltage readings daily to confirm supply quality stays within contractual limits.

Installation

  1. Enable Modbus TCP on the PhoenixContact device via its integrated web server: navigate to the communication or Modbus section and confirm TCP is active on port 502.

  2. Connect the device to the same LAN segment as the ModbusCloud Gateway using a standard RJ45 Ethernet cable, and note the device's assigned IP address.

  3. In the ModbusCloud portal, add the Gateway, create a new device, import the PhoenixContact template, and enter the device IP address and Modbus unit ID (default 255 on many EMpro models).

  4. Spot-check live values: verify that voltage_l1 (address 32774) returns a plausible line voltage and that active_consumption_energy (address 33024) is non-zero and incrementing.

Things to watch for

All registers return zero or NaN. What is wrong?

The EMpro family returns float32 values spanning two consecutive 16-bit registers. Confirm your gateway is configured to read 2 holding registers per point (count 2) using function code 3. A count of 1 will yield an incomplete float and produce garbage or zero readings.

The gateway connects but no data appears in the portal.

Check that the Modbus unit ID in the portal matches the slave address configured on the device. Many PhoenixContact EMpro units ship with unit ID 255. Also confirm port 502 is reachable: firewall rules on managed switches can silently block Modbus TCP traffic.

Phase voltage values look correct but active power reads near zero.

Active power registers (32790, 32798, 32800, 32802) report signed float32 values. If current transformer polarity is reversed on one or more phases, positive and negative contributions cancel out. Verify CT orientation matches the documented wiring direction in the device manual.

Cumulative energy counters reset unexpectedly after a power cycle.

Some firmware versions of the EMpro series store energy totals in volatile memory until a configurable save interval elapses. Check the device web interface for an energy counter persistence or auto-save setting and ensure the device is not being hard-reset during commissioning.

More TCP templates

Want to see how it works?

Electrician working in an open distribution board