SolarLog Data Reading via Modbus TCP
Reads solar plant data from SolarLog data loggers via Modbus TCP.
This template reads production and consumption data from SolarLog PV data loggers via Modbus TCP. It provides AC/DC power, voltage, and yield values across daily, monthly, yearly, and total timeframes. No additional meters, interfaces, or licenses are required.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 17, read only
- Brand
- Solarlog
- Key readings
- AC Power (production and consumption) · DC Power · AC and DC Voltage · Daily and Yesterday Yield · Monthly, Yearly, and Total Yield · Total Power (Wh Peak)
- Compatible models
- SolarLog 200 · SolarLog 250 · SolarLog 300 · SolarLog 500 · SolarLog 1000 · SolarLog 1900 · SolarLog 2000 · SolarLog Base
- Last updated
Registers (17)
17 read, 0 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| LastUpdateTime (Sec) | Sec | Read | |||
| P-AC (W) | W | Read | |||
| P-DC (W) | W | Read | |||
| Uac (U) | U | Read | |||
| Udc (U) | U | Read | |||
| Daily yield (Wh) | Wh | Read | |||
| Yesterday yield (Wh) | Wh | Read | |||
| Monthly yield (Wh) | Wh | Read | |||
| Yearly yield (Wh) | Wh | Read | |||
| Total yield (Wh) | Wh | Read | |||
| P-AC (W) cons. | W | Read | |||
| Daily yield cons. (Wh) | Wh | Read | |||
| Yesterday yield cons. (Wh) | Wh | Read | |||
| Total yield cons. (Wh) | Wh | Read | |||
| Monthly yield cons. (Wh) | Wh | Read | |||
| Yearly yield cons. (Wh) | Wh | Read | |||
| TotalPower (Wh_Wp) | Wh Peak | 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 real-time AC and DC power production from a SolarLog data logger on a cloud dashboard.
- Track daily, monthly, yearly, and total yield to verify PV system performance over time.
- Create an alert when AC production power drops to zero during daylight hours to detect faults.
- Compare production and consumption data remotely to advise customers on self-consumption optimisation.
- Consolidate data from multiple SolarLog devices across different sites into one ModbusCloud account.
Installation
Verify that the SolarLog firmware is version 2.8.1 Build 49 or higher, and update via the SolarLog website if needed.
Enable the Modbus TCP server in the SolarLog configuration menu and note the device IP address.
Connect the ModbusCloud Gateway to the same local network as the SolarLog.
In the ModbusCloud platform, create a new Modbus TCP connection using the SolarLog IP address, port 502, and Slave ID 1.
Import the SolarLog Data Reading template from the ModbusCloud template library and assign it to the configured connection.
Confirm that register values such as AC Power and Daily Yield appear correctly on the ModbusCloud dashboard.
Things to watch for
No data appears after importing the template. What should I check?
Confirm that the SolarLog firmware is at least version 2.8.1 Build 49. Older firmware does not expose the Modbus TCP interface. Also verify that the gateway and the SolarLog are on the same subnet and that port 502 is not blocked by a firewall.
Do I need a Modbus license from SolarLog to use this template?
No. All registers used in this template are freely available without an additional Modbus license from SolarLog.
Which Slave ID should I use?
Use Slave ID 1. This is the default Modbus TCP slave address for SolarLog data loggers.
The yield values look too high or too low. What could be wrong?
Check that the register data types are set to uint16 or uint32 as specified in the template. Mismatched data types or incorrect byte order can cause scaling errors. The registers start at address 3500.
Want to see how it works?
