SofarSolar SOFAR 80…136KTL (grid)

Installation

1. 1Enable 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.
2. 2Connect 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.
3. 3In 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.
4. 4Spot-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

01

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.

02

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.

03

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.

04

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.

Registers (8)

8 read / 0 write

More SofarSolar templates

SofarSolar Hybrid Inverter (battery)

SofarSolar

Modbus RTU

2 registers

SofarSolar HYD 3…6K-EP (pv)

SofarSolar

Modbus TCP

5 registers

SofarSolar Hybrid Inverter (pv)

SofarSolar

Modbus RTU

2 registers

SofarSolar HYD 3…6K-EP (grid)

SofarSolar

Modbus TCP

8 registers

SofarSolar Hybrid Inverter (grid)

SofarSolar

Modbus RTU

5 registers

SofarSolar HYD 3…6K-EP (battery)

SofarSolar

Modbus RTU

1 registers

More RTU templates

Alnor HRU-P

Alnor Systemy Wentylacji Sp. z o. o.

Modbus RTU

Controls Alnor HRU-P heat recovery ventilation units via Modbus RTU.

49 registers7

Alnor HRU

Alnor Systemy Wentylacji Sp. z o. o.

Modbus RTU

Controls and monitors Alnor heat recovery ventilation units via Modbus RTU.

29 registers13

Wattsonic - Schmachtl Sun Energy Box

Wattsonic

Modbus RTU

Monitors Schmachtl Wattsonic hybrid inverter via Modbus RTU

92 registers72

Heidelberg Wallbox Energy Control

AMPERFIED GmbH

Modbus RTU

Controls and monitors Heidelberg Wallbox Energy Control EV charger via Modbus RTU.

22 registers67

connecdoor.controller

connecdoor

Modbus RTU

Controls and monitors smart door access points via RS485

0 registers53

Belimo Air-Water Actuator Modbus RTU

Belimo

Modbus RTU

Controls communicative damper and valve actuators via Modbus RTU.

20 registers46