SofarSolar SOFAR 5…24KTL-G3 (battery)

Installation

1. 1Ensure the inverter has an LSE-3 or compatible LAN logger installed and connected to your local network; confirm it responds on port 8899, which the SOFAR G3 series uses for Modbus TCP.
2. 2In the ModbusCloud portal, add a new device, select Modbus TCP, enter the logger's IP address and port 8899, and set the unit ID to match the Modbus address configured on the inverter (default 1).
3. 3Import this template into the portal and assign it to the device; the batterymode register will appear in the control panel ready for write commands.
4. 4Send a test write to register 4368 with a known valid mode value, then confirm the inverter display or portal response reflects the change before enabling any automated rules.

Things to watch for

01

Why does my write command return no response or time out?

The SOFAR G3 series uses function code 16 (write multiple registers) for control registers. Ensure your gateway is not sending function code 6 (single register write). Also confirm the logger is reachable on port 8899 and that the unit ID matches the inverter's configured Modbus address.

02

The batterymode register accepts the write but the inverter ignores it. Why?

G3 control registers use volatile memory, meaning the inverter may reject commands outside the valid mode enumeration or when the inverter is in a fault or firmware-update state. Verify the inverter's operating status is normal before writing, and consult the SOFAR G3 Modbus protocol document for the list of valid mode values.

03

Register values differ across firmware versions. Which version is required?

SofarSolar has revised the G3 Modbus register map across firmware releases. The remote control section starting at 0x1100 is present from protocol version V1.22 onwards. Download the Modbus protocol document matching your firmware from the SOFAR download centre and cross-check the batterymode address before deploying.

04

Is it safe to write the batterymode register repeatedly from automated rules?

Write registers on the SOFAR G3 use volatile memory specifically to limit write wear, but frequent or incorrect mode writes can cause the inverter to cycle between modes, disrupt protection logic, or potentially invalidate warranty terms. Test automation rules carefully in manual mode first, and add rate-limiting to prevent runaway writes.

Registers (1)

0 read / 1 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 TCP templates

Domekt R 400 V

Komfovent

Modbus TCP

Controls Komfovent Domekt recuperator ventilation via Modbus TCP

25 registers118

Fronius - Modbus TCP

Fronius

Modbus TCP

Monitors Fronius Symo and Primo inverters via Modbus TCP

15 registers597

NIBE Nibe S-Series (SG Ready)

NIBE

Modbus TCP

5 registers1

SunSpec Model 709 — DER Trip LF

SunSpec

Modbus TCP

9 registers

Victron Meter AcOut

Victron

Modbus TCP

16 registers

FoxESS Avocado (grid)

FoxESS

Modbus TCP

8 registers