Atmoce MG100 M-gateway (battery)
The Atmoce MG100 is a microinverter M-Gateway that aggregates data from Atmoce solar and battery systems into a single Modbus TCP interface. This template targets the battery subsystem, reading instantaneous power, cumulative energy, and state of charge at addresses 60071, 60166, and 60095. Three write registers at addresses 60310 to 60312 allow remote battery mode control, covering charge, discharge, and automatic operating states. Connect this template in ModbusCloud to track battery behavior across time and trigger mode changes from your portal without on-site access.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 6, read and write
- Brand
- Atmoce
- Last updated
Registers (6)
3 read, 3 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| power | W | Read | |||
| energy | Wh | Read | |||
| soc | % | Read | |||
| batterymode_a | Write | ||||
| batterymode_c | Write | ||||
| batterymode_d | Write |
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 battery state of charge over time to detect capacity fade across seasons.
- Track instantaneous battery power to verify charge and discharge cycles match the expected schedule.
- Alert on unexpected drops in state of charge during off-peak hours to spot load anomalies.
- Report cumulative battery energy throughput monthly to support performance and warranty assessments.
- Verify that remote battery mode writes via the portal take effect within the expected response window.
Installation
Enable 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.
Connect 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.
In 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.
Spot-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
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.
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.
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.
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.
Want to see how it works?
