ABB M4M 30 Modbus

Power and energy meter

M4M 30 Modbus is a panel network analyser for conventional 1 A or 5 A CTs, with RS-485, Bluetooth commissioning and four programmable I/O. Edge reads its scaled electrical values over Modbus RTU.

ABB M4M 30
  • Modbus RTU

Power and energy meter

Compatibility

Compatible through Modbus RTU

Edge reads the documented local Modbus interface through the connection path below. This is protocol compatibility, not a claim of a built-in device mapping.

M4M 30 MODBUS, order code 2CSG274761R4051 (M4M30RS485), using conventional CT inputs. Ethernet, Rogowski, I/O, BACnet, Profibus, MID and M4M32 variants are not interchangeable hardware.

Connect it with

For M4M30RS485 with a configured slave address

  • Modbus
  • Wireless
  • Edge
  • Platforms
Power and energy meter
Interface
Gateway
Edge
Output
M4M 30 ModbusM4M 30 Modbus RS-485 port
ZMB-31Modbus RTU to the EpiSensor wireless network
ZGW-20 GatewayHosts Edge locally
EpiSensor EdgeEdge Modbus client
Customer platformMQTT · API · files
Modbus RTU · RS-485
EpiSensor wireless
Runs locally
Optional onward data
Match the meter’s configured address, speed and parity. Use one master and the documented bus wiring and end termination. Bluetooth is a commissioning interface, not the Edge measurement transport used here. The customer-platform output is optional; Edge remains the local system of record.

Models

Download
ModelsInterfaceRoute into Edge
M4M 30 Modbus, 2CSG274761R4051Conventional CT inputs; Modbus RTU; four programmable I/OUse the manufacturer map’s M4M30 product applicability.
M4M 30 EthernetSeparate product with Modbus TCP and Ethernet portsUse its own network settings; do not infer Ethernet from the family manual.
M4M 30 Rogowski / M4M 30-M / M4M32Different sensor input, certification or metering specificationCheck the exact order code before choosing wiring, accuracy or register scope.

Specifications

The M4M map is deliberately explicit about engineering units and resolution. A voltage register contains an unsigned integer that must be scaled, whereas other values have different widths and signs. The standard Modbus variant also differs physically from the Ethernet and Rogowski models, even though one user manual covers them together.1

Order code
2CSG274761R4051 / M4M30RS4854
Current inputs
Conventional 1 A or 5 A CT secondary; Rogowski is a separate version1
Communications
Modbus RTU and Bluetooth; Bluetooth is not the polling path in this guide4
Serial parameters
Address 1–247; 9.6, 19.2, 38.4, 57.6 or 115.2 kbit/s; use the configured parity1
Accuracy
M4M30 active energy class 0.5S to IEC 62053-22 under the stated measurement conditions1
Installation envelope
Front IP54, terminals IP20; operating temperature −25 to +70 °C under manual conditions1

Interface

Documented measurements and integration boundaries for M4M 30 Modbus.

  • Phase voltage L1 at 0x5B02: two-register unsigned integer, resolution 0.1 V.
  • Phase and line voltages, currents and frequency with their individual workbook resolutions.
  • Signed and unsigned power quantities: use the declared data type rather than treating all measurements as FLOAT32.
  • Active energy import at 0x5000: four registers, unsigned quantity, 0.01 kWh resolution.
  • Demand, alarms and historical records have separate access procedures; historical selection can require writes.
  • Meter identity, firmware and configuration to preserve the exact product and scaling context.
  • Unavailable unsigned values are FFFF in every register; signed values use their maximum positive code. Keep these as unavailable, not as large real measurements.

Assessment

M4M 30 MODBUS, order code 2CSG274761R4051 (M4M30RS485), using conventional CT inputs. Ethernet, Rogowski, I/O, BACnet, Profibus, MID and M4M32 variants are not interchangeable hardware.

InteroperabilityWell supported
Manufacturer protocol manual plus typed, scaled register workbook establish a complete local read path.23
AccuracySupported with conditions
Conventional CT inputs and class 0.5S active-energy measurement have defined conditions; CT and wiring error remain separate.1
SecuritySupported with conditions
The user manual documents password-controlled configuration; protect the serial segment and omit writes from monitoring.1
ReliabilitySupported with conditions
The manual specifies supply, measurement and operating conditions; explicit stale-state handling is still required in the collector.1
RuggednessSupported with conditions
IP54 front, IP20 terminals and −25 to +70 °C operating range define a panel-mounted installation envelope.1
ScalabilitySupported with conditions
Unique addresses 1–247 and documented bus topology support multi-meter segments; poll complete values within a managed bus schedule.12
LifecycleSupported with conditions
ABB publishes revised user, protocol and mapping documents, including version-scoped quantities and firmware changes.13

Setup

Read and scale L1 phase voltage

ABB’s communications manual gives the FC03 request at 0x5B02, and its mapping workbook defines the two-register unsigned value with 0.1 V resolution.

Function
FC03 Read Holding Registers
Literal PDU address
0x5B02 = 23298 decimal; this is already the bus address
Quantity
2 registers, 4 data bytes
Request PDU
03 5B 02 00 02; the RTU client adds the configured slave address and CRC
Synthetic response data
00 00 08 FC, most significant byte first
Decode
Unsigned 32-bit 2300 × 0.1 V = 230.0 V
Acceptance
Confirm the configured wiring supports L1-N, then compare the scaled value with the simultaneous meter display

Acceptance: The 230 V response is an independently calculated example, not a physical device capture. Never apply the 0.1 multiplier to every register: current, power, energy and status entries have their own type, width and resolution.

  1. Match the order code and CT input

    Confirm 2CSG274761R4051 and record firmware. This is the conventional-CT Modbus version, not the Rogowski or Ethernet model. Have the authorised installer verify wiring, phase assignment and CT primary/secondary settings.

  2. Record the actual serial settings

    On the meter, open Configuration, Communication, Modbus RTU. Record address, baud rate and parity and enter those exact values in the Edge connection. Follow ABB’s bus topology and termination instructions and retain one master per segment.

  3. Use literal addresses and complete values

    ABB’s Start Reg Hex is the address sent on the bus. Convert hex to decimal if the client requires it; do not subtract one. Read both registers of L1 voltage at 0x5B02 in one FC03 request.

  4. Decode before expanding the point list

    Apply unsigned 32-bit decoding, most significant byte first, and the 0.1 V resolution for the voltage example. Compare the result with the meter display, then configure each further quantity from its own type, register count and resolution.

  5. Separate live reads from historical selection

    Read-only live metering does not require output or setup commands. ABB’s historical interface uses a header selection procedure with writes; treat that as a separate reviewed workflow. Preserve unavailable markers and compare an import-energy delta with the display over a known interval.

Common questions

Should 0x5B02 become 23297?
No. ABB states that the hexadecimal start register is expressed exactly as sent on the bus. 0x5B02 is decimal 23298; no one-based correction is applied.2
Why does a float decoder give nonsense?
L1 phase voltage is an unsigned integer across two registers, with 0.1 V resolution. Reinterpretation as IEEE-754 FLOAT32 changes the meaning of those bits. Use the workbook’s data type and multiplier.3
Can I read historical records without any writes?
The historical interface selects records through header registers and writes before reading data blocks. That is separate from straightforward FC03 live measurements; do not include those selection commands in a read-only polling template.2
Does Bluetooth replace the RS-485 connection?
The exact product offers Bluetooth and Modbus RTU, but this Edge integration uses the documented RS-485 Modbus interface. Bluetooth commissioning is not a claim of an Edge Bluetooth driver.14