Atmoce MG100 M-gateway (pv)
The Atmoce MG100 is a microinverter gateway that aggregates production data from up to 90 Atmoce microinverters into a single Modbus TCP interface. This template reads two key registers from the MG100: current PV output power and cumulative PV energy yield. The MG100 communicates over Ethernet, making it straightforward to integrate into a LAN alongside a ModbusCloud Gateway. For installers monitoring residential or small commercial PV arrays, this template provides a reliable, low-configuration path to live generation data in the ModbusCloud portal.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 2, read only
- Brand
- Atmoce
- Last updated
Registers (2)
2 read, 0 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| power | W | Read | |||
| energy | Wh | Read |
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.
Use cases
- Monitor live PV output power from the Atmoce MG100 to verify generation against forecast irradiance.
- Track cumulative PV energy yield daily and monthly to confirm array performance over time.
- Alert on unexpected drops in reported power to detect failing microinverters or communication loss.
- Compare energy yield across multiple sites equipped with Atmoce MG100 gateways in a single portal view.
- Verify that commissioning is complete by spot-checking live power register values immediately after installation.
Installation
Enable Modbus TCP on the Atmoce MG100 by logging into the Atmozen app or the gateway web interface and activating the Modbus service under the communication or network settings section.
Connect the Atmoce MG100 to the same LAN as the ModbusCloud Gateway using a standard Ethernet cable; confirm the MG100 has a static or reserved DHCP IP address.
In your ModbusCloud portal, add the ModbusCloud Gateway, then import the Atmoce MG100 M-gateway (pv) template, entering the MG100 IP address, port 502, and the correct Modbus unit ID.
Verify the integration by checking the live value of the power register (address 60069) in the portal; a non-zero reading during daylight hours confirms successful communication.
Things to watch for
Why does the power register return zero even in daylight?
The MG100 aggregates data from its connected microinverters. If no microinverters are paired or all are offline, the gateway reports zero. Confirm microinverter pairing via the Atmozen app and check that the PV array is energised before re-polling the register.
The gateway connects but the portal shows no values. What now?
Check that Modbus TCP is explicitly enabled on the MG100, as it may be disabled by default. Also verify the unit ID configured in the portal matches the one set on the device. Mismatch between unit ID or IP address are the most common causes of empty readings.
The energy register value looks implausibly large. Is there a scaling factor?
The energy register (address 60160) is a uint64 type spanning four Modbus registers. Ensure your Modbus client is reading all four consecutive registers and assembling them correctly in big-endian byte order. Partial reads or wrong byte assembly produce grossly incorrect values.
Connection drops intermittently. How do I stabilise it?
The MG100 communicates over Ethernet and can lose its Modbus TCP connection if the device reboots or renews its DHCP lease. Assign a static IP or a DHCP reservation to the MG100 on your router, and set the poll interval in the ModbusCloud portal to no less than two seconds to avoid overwhelming the gateway.
Want to see how it works?
