Atmoce MG100 M-gateway (grid)
The Atmoce MG100 is a smart energy gateway designed for residential and light-commercial solar installations, connecting up to 90 Atmoce microinverters with batteries, loads, and the grid. This Modbus TCP template reads the grid connection point registers, covering total active power, cumulative energy, and per-phase voltages and currents for all three phases. Using the ModbusCloud Gateway, installers and building owners can continuously monitor grid import and export flows, detect phase imbalances, and build historical energy reports without additional metering hardware.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 8, read only
- Brand
- Atmoce
- Last updated
Registers (8)
8 read, 0 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| power | W | Read | |||
| energy | Read | ||||
| currents_a | A | Read | |||
| currents_b | A | Read | |||
| currents_c | A | Read | |||
| voltages_a | V | Read | |||
| voltages_b | V | Read | |||
| voltages_c | V | 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 total grid active power in real time to verify that solar self-consumption targets are being met.
- Track cumulative grid energy to generate monthly import and export reports for billing reconciliation.
- Compare per-phase currents on phases A, B, and C to detect load imbalances across the three-phase installation.
- Alert on unexpected grid power spikes to identify sudden load events or microinverter trip conditions.
- Verify per-phase voltages against grid tolerance limits to confirm compliance with local grid connection requirements.
Installation
Enable Modbus TCP on the MG100 gateway through the ATMOZEN app or the device web interface, under the communication or Modbus section, and note the assigned IP address.
Connect the MG100 to the same local area network as the ModbusCloud Gateway using an Ethernet cable (Cat 6 UTP recommended) or the device's Wi-Fi interface.
In the ModbusCloud portal, add a new device, select the Atmoce MG100 M-gateway (grid) template, enter the MG100 IP address, and set the Modbus unit ID to match the value configured on the device.
After saving, open the live register view and spot-check the power register (address 60073) and a phase voltage register (e.g., voltages_a at address 60089) to confirm non-zero values that match the physical installation.
Things to watch for
The gateway connects but all register values show zero or null. Why?
Modbus TCP is disabled by default on the MG100. Open the ATMOZEN app or the device's local web interface, navigate to the communication or Modbus section, and explicitly enable Modbus TCP. The device must also have an active grid connection before meter registers report live values.
Phase current values look incorrect or implausibly large. What should I check?
Current registers (addresses 60090, 60092, 60094) are int16 signed values. If your Modbus master is interpreting them as unsigned uint16, negative currents (grid export) will appear as very large positive numbers. Confirm your client treats these registers as signed 16-bit integers.
The energy register (address 60184) never increments. What is wrong?
The energy register is a uint64 spanning four consecutive 16-bit holding registers. Some Modbus clients default to reading only two registers for a 32-bit value. Verify your client is configured to read four registers starting at address 60184, and that byte and word order match the MG100 protocol specification (big-endian by default for TCP devices).
I get timeout errors even though the MG100 IP address is reachable. What now?
The MG100 supports multiple simultaneous communication channels (Wi-Fi, Ethernet, PLC, RS485). If the device is under heavy load from the ATMOZEN cloud connection or PLC traffic, Modbus TCP responses can be delayed. Increase the Modbus response timeout in the ModbusCloud portal to at least 2000 ms, and ensure no firewall rule is blocking TCP port 502 on the local network.
Want to see how it works?
