Atmoce MG100 M-gateway (battery)

Installation

1. 1Enable Modbus TCP on the Atmoce MG100 through the Atmozen app or the device web interface under the communication or Modbus section, and note the assigned IP address and unit ID.
2. 2Connect the MG100 to the same LAN segment as the ModbusCloud Gateway using a Cat 6 Ethernet cable into the RJ45 port on the device or combiner.
3. 3In the ModbusCloud portal, add a new device, select the Atmoce MG100 M-gateway (battery) template, enter the MG100 IP address, port 502, and the configured Modbus unit ID.
4. 4Spot-check register 60095 (soc) in the live register view to confirm a plausible state-of-charge reading, then verify power at address 60071 matches any real-time load or generation visible on the inverter display.

Things to watch for

01

The gateway connects but soc and power registers return zero or no data.

Modbus TCP access may be disabled by default on the MG100. Confirm the Modbus server is enabled in the Atmozen app or device web interface. Also check that the configured unit ID in ModbusCloud matches the ID assigned on the device. A mismatch returns empty or zero responses without a Modbus exception.

02

Power readings appear as very large negative numbers. What is wrong?

The power register uses a signed int32 type. If your Modbus client reads it as unsigned, large negative values will appear as numbers above two billion. Confirm your polling tool or the ModbusCloud template is interpreting address 60071 as int32, not uint32. The template input already specifies int32, so no manual override is needed.

03

Writes to batterymode registers seem to have no effect. How do I diagnose this?

First confirm Modbus write access is enabled on the MG100 separately from read access, as some firmware versions gate writes independently. Use function code 16 as specified. Verify the unit ID is correct and that no firewall or router is blocking write transactions on port 502. Check the MG100 LED status for any fault indication after the write attempt.

04

Is it safe to write battery mode registers while the system is running?

Use caution with the write registers at addresses 60310, 60311, and 60312. Sending an incorrect mode value can override automatic battery management, force deep discharge, or prevent charging. Always test write commands during low-load periods, confirm the expected mode change in the portal before leaving the site, and review the Atmoce Modbus interface documentation for valid mode values before deploying automated setpoint logic.

Registers (6)

3 read / 3 write

More Atmoce templates

Atmoce MG100 M-gateway (grid)

Atmoce

Modbus TCP

8 registers

Atmoce MG100 M-gateway (pv)

Atmoce

Modbus TCP

2 registers

Atmoce AC Battery and Module-Inverter

Atmoce

Modbus RTU

Controls and monitors Atmoce module-inverters and AC coupled batteries via Modbus RTU.

38 registers9

More TCP templates

Algodue Energy meter UEM80-2D E

Algodue Elettronica S.r.l.

Modbus TCP

Measures single-phase energy consumption and production via Modbus TCP.

12 registers46

Sigenergy SigenStore EC (grid)

Sigenergy

Modbus TCP

5 registers1

Fronius GEN24

Fronius

Modbus TCP

Monitors and controls Fronius GEN24 inverters and PV batteries via SunSpec Modbus TCP

0 registers762

HUAWEI SUN2000 Inverter & LUNA2000 battery

Huawei

Modbus TCP

Monitors HUAWEI SUN2000 inverter, LUNA2000 battery, and Smart Power Sensor via Modbus TCP.

4 registers1248

NIBE Nibe S-Series (SG Ready)

NIBE

Modbus TCP

5 registers1

Fronius - Modbus TCP

Fronius

Modbus TCP

Monitors Fronius Symo and Primo inverters via Modbus TCP

15 registers597