Phoenix Contact: Electrical connections, industrial automation and networked energy measurement

Overview

Phoenix Contact supplies a broad range of electrical and automation equipment. Its EMpro products provide a specific energy-measurement layer within that portfolio: standalone instruments acquire electrical values and make them available to higher-level systems. This is distinct from selecting a general-purpose controller or a network gateway.

The DIN-rail product overview separates current-transformer and Rogowski-input models, with further variations for supply and communications. The virtual device catalogue also includes front-panel instruments. Those distinctions provide useful starting points for a specification: choose the measurement input, installation format and required interface before comparing the software functions available on the selected device.

Offering

The EMpro overview identifies EEM-MA370, order number 2907983, as a current-transformer model with display and Modbus TCP. EEM-MA371, order number 2908307, occupies the corresponding Rogowski-input position. The R variants add Modbus RTU, and separate 24 V DC variants are explicitly identified rather than implied by the base model name.

For a front-panel installation, the virtual device catalogue identifies EEM-MA770-PN, order number 2907946, with current-transformer input and PROFINET alongside Modbus TCP. This gives a different physical and automation arrangement from the DIN-rail meters. It is not a generic protocol option automatically present on every EMpro instrument.

Beyond metering, PLCnext Engineer supports controller engineering, Emalytics Collector handles building-data collection and processing, and ACRON provides process-data archiving and reporting. These software roles are separate from the electrical measurement hardware. Manufacturer documentation.

Technology

The EMpro device documentation describes web-based configuration, configuration export and import, and communication interfaces selected according to article and firmware. It also describes read-only options for interfaces that can otherwise change configuration. That is useful for separating a monitoring integration from an engineering connection that requires write access.

The DIN-rail model table makes the hardware distinctions visible, while the virtual web-management catalogue lets an engineer inspect a model's interface before installation. A practical monitoring setup should bind its register definitions to the selected article and firmware. This profile documents the available integration routes without claiming that a tested Edge template already exists for them.

Markets

Industrial sites may need energy readings at distribution boards, individual machines or process areas. EMpro's DIN-rail and panel choices allow the instrument format to follow the available enclosure space and operator access. The current-sensor choice is equally important: the product table separates conventional current-transformer inputs from Rogowski connections.

For a controls project, a named PROFINET variant can align with an existing automation network, while Modbus TCP provides another documented data path. The device description also exposes configuration and access-control functions. These should be considered alongside the readings required, rather than selecting an instrument solely because its family advertises several protocols.

Company

Phoenix Contact's group overview identifies its headquarters in Blomberg, Germany, and dates its founding to 1923 in Essen. The same source describes a family-owned group with electrical connection, industrial electronics and automation business fields. The location of the original business is therefore kept distinct from the current headquarters.

This profile focuses on the energy-measurement products relevant to connected energy systems, rather than attempting to summarize every product in the group. The manufacturer's EMpro documentation and virtual management catalogue provide direct technical entry points. They are particularly useful because model numbers, current-input types and interface variants can be checked before an integration is designed.