Powerdog Powerdog (grid)
The Powerdog is an energy management and PV monitoring system developed by ecodata solutions GmbH, deployed at grid connection points on solar installations. This template reads two signed 32-bit active power values over Modbus TCP: power_a (register 40026) and power_b (register 40002), representing the two active power channels at the grid meter interface. Both registers use function code 3 and carry no unit scaling in the register definition, so raw integer values correspond directly to watts. Connecting the Powerdog to ModbusCloud gives installers live and historical visibility into grid power flows without additional hardware.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 2, read only
- Brand
- Powerdog
- Last updated
Registers (2)
2 read, 0 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| power_a | W | Read | |||
| power_b | W | 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 grid power import and export across both channels to verify net-metering accuracy.
- Track long-term trends in power_a and power_b to detect drift or calibration issues over time.
- Alert on sustained positive power readings indicating unexpected grid draw during peak solar hours.
- Compare channel A and channel B values to spot asymmetric load distribution at the grid connection.
- Report historical grid power data per site to support billing reconciliation or yield analysis.
Installation
Enable Modbus TCP on the Powerdog device through its web interface or configuration portal, noting the assigned IP address and port (default 502).
Connect the Powerdog to the same LAN segment as the ModbusCloud Gateway, ensuring no firewall rules block port 502 between the two devices.
In your ModbusCloud portal, add the Gateway, import the Powerdog (grid) template, and enter the device IP address, port, and Modbus unit ID matching the Powerdog configuration.
Verify the integration by reading register 40002 and register 40026 live in the portal and confirming the values change in line with actual grid power flow.
Things to watch for
Both registers return zero even though the system is live. Why?
The Powerdog may not have Modbus TCP enabled. Check the device configuration interface and confirm that the Modbus server is active. Also verify that the unit ID configured in the ModbusCloud portal matches the slave ID set on the Powerdog, as a mismatch silently returns zeros on many devices.
Register values look unexpectedly large or wrong. What is the cause?
Both power_a and power_b are int32 types spanning two consecutive 16-bit registers. If your polling tool or gateway reads only a single 16-bit word instead of two consecutive registers (four bytes), the result will be incorrect. Confirm that the template is configured to read two registers per channel and that byte order is big-endian, which is standard for Modbus.
The gateway connects but register 40026 always times out. Register 40002 is fine.
Some Powerdog firmware versions may not populate register 40026 unless a specific operational mode or metering option is active. Check that the hardware configuration includes a second power channel and that the firmware version in use supports reading at address 40026. Consult the ecodata documentation for your specific device revision.
How do I tell whether a power reading represents import or export?
The registers are typed as int32, meaning values are signed. A positive value typically indicates power drawn from the grid (import), and a negative value indicates power fed into the grid (export). Confirm the sign convention with the ecodata documentation for your specific Powerdog firmware, as conventions can vary between device generations.
More Powerdog templates
Want to see how it works?
