SunSpec Model 402 — String Combiner (Advanced)

Installation

1. 1Verify that the SunSpec Model 402 block is active on the target device by confirming the DID register returns 402; consult the combiner manufacturer's documentation under the communication or Modbus section to enable Modbus TCP if not already active.
2. 2Connect the combiner to the same Ethernet network as the ModbusCloud Gateway, ensuring TCP port 502 is reachable and no firewall blocks the connection.
3. 3In the ModbusCloud portal, add the Gateway, import the SunSpec Model 402 template, and assign the correct Modbus unit ID matching the combiner's configured slave address.
4. 4Spot-check the live dca and dcv readings in the portal against the combiner's local display or data logger to confirm scaling factors (dca_sf, dcv_sf) are being applied correctly.

Things to watch for

01

Current and power readings look ten times too large or too small. Why?

SunSpec uses signed 16-bit scale factors (dca_sf, dcw_sf, dcwh_sf) as exponents of ten. If your Modbus master applies the raw integer without multiplying by 10 raised to the scale-factor value, readings will be off by an order of magnitude. Confirm the portal is reading the scale-factor registers at addresses 2 through 6 and applying them to each corresponding measurement.

02

The gateway connects but all registers return 0x8000 or 0xFFFF. What now?

These are SunSpec not-implemented sentinel values. The target device may not support every register in Model 402, or the model block was not discovered correctly. Verify the DID at address 0 returns exactly 402 and that the block length register (l) matches the expected size. Some combiners require a Modbus TCP discovery scan starting at register 40001 or 50001 before the model block becomes accessible.

03

The evt register shows a non-zero value. What does each bit mean?

The evt field is a 32-bit SunSpec standard bitmask where each bit position maps to a defined combiner fault condition such as low-string current, overcurrent, or ground fault. Consult the SunSpec String Combiner Models specification for the full bit definition table. The evtvnd register holds additional manufacturer-specific flags; check the combiner device manual for those bit definitions.

04

I cannot reach the combiner over TCP even though it is on the same LAN.

Confirm that the combiner's Modbus TCP server is enabled (some devices ship with it disabled by default) and that it is listening on port 502. Check that the unit ID configured in the ModbusCloud portal matches the slave address set on the device. Also verify no VLAN separation or firewall rule is blocking port 502 between the Gateway and the combiner.

Registers (18)

18 read / 0 write

More SunSpec templates

SunSpec Model 709 — DER Trip LF

SunSpec

Modbus TCP

9 registers

SunSpec Model 139 — LVRTX

SunSpec

Modbus TCP

12 registers

SunSpec Model 19 — PPP Link

SunSpec

Modbus TCP

11 registers

SunSpec Model 601 — Tracker Controller DRAFT 2

SunSpec

Modbus TCP

13 registers

SunSpec Model 64412 — DER Cyber Exploitation

SunSpec

Modbus TCP

45 registers

SunSpec Model 135 — LFRT

SunSpec

Modbus TCP

11 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

Victron Meter AcOut

Victron

Modbus TCP

16 registers

SMA StpSe Battery

SMA

Modbus TCP

16 registers

GoodWe EmergencyPowerMeter

GoodWe

Modbus TCP

12 registers