The id register returns a value other than 14. Why?

The SunSpec model map on your device may start at address 40000 or 50000 rather than 0. Adjust the base address offset in the ModbusCloud portal to match the actual SunSpec map start for your device. Scan the holding register space at offsets 0, 40000, and 50000 to locate the correct starting point.

Reads succeed but the addr string register shows garbage characters.

SunSpec string registers are packed as ASCII in consecutive 16-bit registers, big-endian byte order. If your gateway or polling tool applies a different byte swap, the string will appear garbled. Confirm your Modbus TCP client reads string registers without byte-swapping individual register pairs, as SunSpec mandates big-endian ordering.

The gateway connects but no values appear for any register.

Check that the unit ID assigned in the portal matches the device's configured Modbus unit ID. SunSpec devices often respond only on a specific unit ID. Also verify the TCP idle timeout: some devices close inactive connections after 60 to 120 seconds, causing silent poll failures. Reduce the polling interval or keep-alive settings in the portal.

Is it safe to write to nam, addr, port, user, or pw registers remotely?

Use caution. Writing proxy credentials or the target address remotely can redirect the device's outbound communication to an unintended endpoint, breaking monitoring or voiding support agreements. Always back up current register values before any write operation, test on one device first, and coordinate with the site owner before modifying authentication registers.

Free Modbus template: SunSpec Model 14 — Proxy Server

SunSpec Model 14 is a network-configuration model defined by the SunSpec Alliance that stores proxy server connection parameters on a compliant Modbus TCP device. The template reads the model identifier and length registers, and reads or writes the proxy name, capability flags, configuration word, connection type, target address, port, username, and password. It does not measure energy or power; its purpose is to let integrators inspect and configure the outbound proxy endpoint through which a DER device communicates with a monitoring back-end. Importing the SunSpec Model 14 Proxy Server template into ModbusCloud lets you track and audit these settings in one place.

Name	Address	Function	Type	Access
id SunSpec model identifier, fixed value 14 for Proxy Server.	0	FC03	uint16	R
l Model length in registers, excluding id and l.	1	FC03	uint16	R
nam Human-readable name assigned to this proxy server entry.	2	FC03	string	R/W
cap Capability flags indicating features supported by this proxy.	6	FC03	bool	R/W
cfg Configuration word encoding proxy operational settings.	7	FC03	uint16	R/W
typ Connection type flag: distinguishes proxy protocol variant.	8	FC03	bool	R/W
addr Target proxy server hostname or IP address string.	9	FC03	string	R/W
port TCP port number of the remote proxy server.	29	FC03	uint16	R/W
user Username for authenticating to the remote proxy server.	30	FC03	string	R/W
pw Password for authenticating to the remote proxy server.	42	FC03	string	R/W

SunSpec Model 14 — Proxy Server

Overview

Use cases

Installation

Things to watch for

Registers (10)

Working with Modbus in your projects?

Free: RS485 and Modbus RTU installation checklist (PDF)

More SunSpec templates

SunSpec Model 709 — DER Trip LF

SunSpec Model 139 — LVRTX

SunSpec Model 19 — PPP Link

SunSpec Model 601 — Tracker Controller DRAFT 2

SunSpec Model 64412 — DER Cyber Exploitation

SunSpec Model 135 — LFRT

More TCP templates

Algodue Energy meter UEM80-2D E

Sigenergy SigenStore EC (grid)

Fronius GEN24

HUAWEI SUN2000 Inverter & LUNA2000 battery

NIBE Nibe S-Series (SG Ready)

Fronius - Modbus TCP