SofarSolar SOFAR 80…136KTL (grid)
The SofarSolar SOFAR 80…136KTL is a three-phase commercial and industrial string inverter covering the 80 kW to 136 kW power range. This template connects to the inverter as a grid-side meter over Modbus RTU via RS485 and reads total active grid power, per-phase currents and active power for phases A, B, and C, and a cumulative energy counter. With these values collected in your ModbusCloud portal you can track grid import and export continuously, balance per-phase loading, and maintain an auditable energy record across one or more sites.
- Protocol
- Modbus RTU
- Connection
- RS485
- Registers
- 8, read only
- Brand
- SofarSolar
- Compatible models
- HYD 5…20K-3PH · HYD 3…6K-EP · SOFAR 80…136KTL · SOFAR 5…24KTL-G3
- 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 | |||
| currents_a | A | Read | |||
| currents_b | A | Read | |||
| currents_c | A | Read | |||
| powers_a | W | Read | |||
| powers_b | W | Read | |||
| powers_c | W | Read | |||
| energy | 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 detect unexpected import or export events.
- Track cumulative grid energy to generate monthly billing reports for commercial tenants.
- Compare per-phase active power on phases A, B, and C to identify load imbalances over time.
- Alert on sustained grid import above a threshold during peak-tariff hours to trigger demand response.
- Verify per-phase current readings after panel reconfiguration to confirm balanced string distribution.
Installation
Enable Modbus RTU on the SOFAR 80…136KTL by navigating to the communication or Modbus settings menu on the inverter display, set the slave address (default 1) and baud rate to 9600, 8N1.
Connect the RS485 A+ and B- terminals of the inverter to the corresponding RS485 terminals of the ModbusCloud Gateway using a shielded twisted-pair cable; enable the termination resistor on the last device in the bus.
In the ModbusCloud portal, add the Gateway, import the SofarSolar SOFAR 80…136KTL (grid) template, and assign the unit ID that matches the slave address set on the inverter.
Spot-check register 1160 (total grid power) in the live data view and confirm the value matches a reference measurement from the inverter display or a calibrated clamp meter.
Things to watch for
All registers return zero or timeout. What is wrong?
Confirm the RS485 A+ and B- wires are not swapped at either end. SofarSolar inverters are polarity-sensitive. Also verify the baud rate is 9600 and the unit ID in the portal matches the slave address on the inverter, which defaults to 1 but is often changed in multi-inverter plants.
Per-phase current reads a large implausible number. How do I fix this?
The per-phase current registers (currents_a, currents_b, currents_c) are uint16 and include a manufacturer scaling factor. If the raw value looks implausible, check the SOFAR Modbus User Guide for the specific series scaling (commonly 0.01 A per count). The register unit field in this template is intentionally left blank; apply scaling at the portal or integration layer.
Register map varies and my firmware reads different values. Why?
SofarSolar has used different Modbus protocols across inverter series and firmware versions. This template targets the SOFAR 80…136KTL register layout. If the inverter firmware was recently updated, compare register 1160 output against the inverter display; mismatches indicate a protocol variant that may require a firmware-specific template.
Multiple Modbus clients lose connection intermittently. What helps?
RS485 supports only one master at a time. If another device, such as a data logger stick, is also polling the inverter, bus collisions will cause timeouts. Route all polling through the ModbusCloud Gateway as the sole master, or use a Modbus proxy to serialize requests from multiple clients.
Want to see how it works?
