SRNE PV inverter (RS485)

Register map(s) for this device, each at the trust rung it earned. Addresses are 0-based as on the wire; word order and scaling are only confirmed at the hardware-verified rung.

interop-verified

Read + decoded cleanly over a real network vs an independent third-party Modbus test server (transport and framing; reads are remapped into the server's register window, so the map's own addresses are NOT exercised). Does NOT prove word order/scaling against the actual device.

point	address (0-based)	type	scale	unit
user_password	4869	U16	1

link settings as documented (unverified): RTU; default 9600 8N1; FC 03,16; Supports a universal address of 0xF7 (247) for one-to-one communication without knowing the device address. Broadcast address is 0.

bench facts as documented (unverified)

wiring notes	Star connection. Physical layer limits the maximum number of slaves to 32.
max registers/read	12
broadcast	supported
protocol notes	CRC transmission order is low byte first, then high byte, which is different from standard Modbus. Although the protocol description mentions a limit of 20 registers, error code 0AH explicitly states that a length error is triggered if the number of registers exceeds 12.
doc revision	V1.00

generated by gemini:gemini-3.5-flash · harvested from https://www.midnitesolar.com/firmware/Solar_inverter_charger_communication_protocol.pdf (SRNE); manual-faithful — the document's claims, panel risk: LOW — panel concurs, no field disagreements; proved interop-verified on 2026-06-10 · recorded 2026-06-10

The trust ladder

Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.

generated — A prompt produced it. Unproven — anyone can regenerate this.
structure-verified — Decode path is structurally sound (addresses, widths, finite values). Does NOT prove word order or scaling.
interop-verified — Read + decoded cleanly over a real network vs an independent third-party Modbus test server (transport and framing; reads are remapped into the server's register window, so the map's own addresses are NOT exercised). Does NOT prove word order/scaling against the actual device.
simulator-verified — Decoded correctly against a protocol emulator seeded with known-true values — catches word-order/scaling errors vs the emulator, not the physical device.
hardware-verified x1 — Matched a real device with operator-attested readings as ground truth — the only rung that confirms word order + scaling on the wire.

Have a device that isn't here? Upload its register map — generation is free, and the connector earns its rung by being proven, not claimed.

Need it proven on your own device? Hardware verification — if it doesn't verify, you don't pay.

Building a platform? License the verified library — machine-readable maps, firmware matrix, API access.