SRNE MPPT inverter-charger

Register map(s) for this device, with a note of how far each has been checked. Addresses are 0-based, as on the wire. Scale and byte order are confirmed only at the hardware-verified rung.

coherence-checked

Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.

point	address (0-based)	type	scale	unit
System information (max voltage / rated charging current)	10	U16	1
System information (rated discharging current / product type)	11	U16	1
Product model	12	U16	1
Software version	20	U32BE	1
Hardware version	22	U32BE	1
Product serial number	24	U32BE	1
Device address	26	U16	1
Battery capacity SOC	256	U16	1	%
Battery voltage	257	U16	0.1	V
Charging current	258	U16	0.01	A
Controller and Battery temperature	259	U16	1	℃
Load dc voltage	260	U16	0.1	V
Load dc current	261	U16	0.01	A
Load dc power	262	U16	1	W
Solar panel voltage	263	U16	0.1	V
Solar panel current	264	U16	0.01	A
Charging power	265	U16	1	W
Load On/Off command	266	U16	1
Battery's min. voltage of the current day	267	U16	0.1	V
Battery's max. voltage of the current day	268	U16	0.1	V
Max. charging current of the current day	269	U16	0.01	A
Max. discharging current of the current day	270	U16	0.01	A
Max. charging power of the current day	271	U16	1	W
Max. discharging power of the current day	272	U16	1	W
Charging amp-hrs of the current day	273	U16	1	AH
Discharging amp-hrs of the current day	274	U16	1	AH
Power generation of the current day	275	U16	1	W
Power consumption of the day	276	U16	1	W
Total number of operating days	277	U16	1	days
Total number of battery over-discharges	278	U16	1
Total number of battery full-charges	279	U16	1
Total charging amp-hrs of the battery	280	U32BE	1	AH
Total discharging amp-hrs of the battery	282	U32BE	1	AH
Cumulative power generation	284	U32BE	1	W
Cumulative power consumption	286	U32BE	1	W
Load status and Charging state	288	U16	1
Controller failure, alarm information 16 high bits	289	U16	1
Controller failure, alarm information 16 low bits	290	U16	1
Set charging current limit	57345	U16	0.01	A
Nominal battery capacity	57346	U16	1	AH
System voltage setting and recognized voltage	57347	U16	1
Battery type	57348	U16	1
Over-voltage threshold	57349	U16	0.1	V
Charging voltage limit	57350	U16	0.1	V
Equalizing charging voltage	57351	U16	0.1	V
Boost charging voltage/overcharge voltage	57352	U16	0.1	V
Floating charging voltage/overcharge recovery voltage	57353	U16	0.1	V
Boost charging recovery voltage	57354	U16	0.1	V
Over-discharge recovery voltage	57355	U16	0.1	V
Under-voltage warning level	57356	U16	0.1	V
Over-discharge voltage	57357	U16	0.1	V
Discharging limit voltage	57358	U16	0.1	V
end-of-charge SOC and end-of-discharge SOC	57359	U16	1
Over-discharge time delay	57360	U16	1	S
Equalizing charging time	57361	U16	1	Min
Boost charging time	57362	U16	1	Min
Equalizing charging interval	57363	U16	1	day
Temperature compensation factor	57364	U16	1	mV/℃/2V
Load working modes	57373	U16	1
Light control delay	57374	U16	1	Min
Light control voltage	57375	U16	1	V
Special power control	57377	U16	1
Historical data record (FLASH)	61440	U16	1

link settings as documented (unverified): RTU; default 9600 8N1; FC 03,06,16,120,121; Address FFH can be used to bypass the local device address with data return for stand-alone devices. Address 00H is a broadcast address.

bench facts as documented (unverified)

terminals	RJ12 (6-pin) for RS232, 4-pin terminal block for RS485-1, 8-pin terminal block for RS485-2, 4-pin terminal block for TTL
A/B polarity	RS485-1: D- (Yellow), D+ (Red); RS485-2: D+ (pin 2), D- (pin 3)
connector	RJ12, Terminal block
shield/ground	Power supply grounding/signal grounding
inter-frame delay	10 ms
broadcast	supported
protocol notes	PDU address segments (0000 to 0009)/(000A to 001A)/(0100 to 0122)/(E001 to E02D)/(F000 to F3FF) are not allowed to cross access and modification in the same command.
power	RS232: pins 5,6 positive, pins 3,4 ground. RS485-1: 12V pin 1, GND pin 2. RS485-2: Power positive pin 1, ground pin 4. TTL: GND pin 1, 12.8V pin 4.
doc revision	V3.9 (2020-4-21)

field reports — community-sourced, unverified (checked 2026-06-11)

Users report that changing settings (writing to registers) on SRNE hybrid inverters via Modbus requires writing a password (default '111111') to register E203 (or E202) first, which must be done once after every reboot of the inverter. Otherwise, write commands fail or are ignored. [source]
Modbus communication can be slow and unstable, with register writes taking up to 10 minutes or failing if multiple write registers are spammed without a delay (adding a delay between actions is recommended). [source]
confirmed: comms defaults (9600 baud, RTU, N, 8, 1) — confirmed by SRNE Inverter Modbus Protocol Guide and community integrations
confirmed: PDU address segments (0000 to 0009)/(000A to 001A)/(0100 to 0122)/(E001 to E02D)/(F000 to F3FF) are not allowed to cross access — confirmed by SRNE Modbus Protocol V3.8/V3.9 documentation
confirmed: Address FFH can be used to bypass local device address — confirmed by SRNE Modbus Protocol V3.8/V3.9 documentation
confirmed: Register battery_soc @ 256 (0x0100) and battery_voltage @ 257 (0x0101) — confirmed by SRNE Modbus Protocol V3.8/V3.9 documentation and community ESPHome integrations

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.
coherence-checked — Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.
hardware-verified (software-key) x1 — Matched a real device with operator-attested readings as ground truth — the only rung that confirms word order + scaling on the wire.

Device not here? Upload its manual and get a checked map back. It's free.

Want it confirmed against your own device? Order hardware verification. If it doesn't check out, you don't pay.

Building on a lot of devices? License the library — machine-readable maps, the firmware matrix, and API access.