Renogy Rover 20A/40A MPPT charge controller

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 voltage and rated charging current	10	U16	1
Rated discharging current and 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
Controller, device address	26	U16	1
Battery capacity SOC	256	U16	1	%
Battery voltage	257	U16	0.1	V
Charging current (to battery)	258	U16	0.01	A
Controller and Battery temperature	259	U16	1	°C
Street light (load) voltage	260	U16	0.1	V
Street light (load) current	261	U16	0.01	A
Street light (load) power	262	U16	1	W
Solar panel voltage	263	U16	0.1	V
Solar panel current (to controller)	264	U16	0.01	A
Charging power	265	U16	1	W
Light 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	0.0001	kWh
Power consumption of the day	276	U16	0.0001	kWh
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	0.0001	kWh
Cumulative power consumption	286	U32BE	0.0001	kWh
Street light status and Charging state	288	U16	1
Controller fault and warning information	289	U32BE	1
Dimming command	57345	U16	1	%
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/ °C/ 2V
1st-stage operating duration	57365	U16	1	H
1st-stage operating power	57366	U16	1	%
2nd-stage operating duration	57367	U16	1	H
2nd-stage operating power	57368	U16	1	%
3rd-stage operating duration	57369	U16	1	H
3rd-stage operating power	57370	U16	1	%
Morning on operating duration	57371	U16	1	H
Morning on operating power	57372	U16	1	%
Load working modes	57373	U16	1
Light control delay	57374	U16	1	Min
Light control voltage	57375	U16	1	V
LED load current setting	57376	U16	10	mA
Special power control	57377	U16	1
Working hours determined by automatic sensing 1	57378	U16	1	H
Power with people sensed 1	57379	U16	1	%
Power with no people sensed 1	57380	U16	1	%
Working hours determined by automatic sensing 2	57381	U16	1	H
Power with people sensed 2	57382	U16	1	%
Power with no people sensed 2	57383	U16	1	%
Working hours determined by automatic sensing 3	57384	U16	1	H
Power with people sensed 3	57385	U16	1	%
Power with no people sensed 3	57386	U16	1	%
Sensing time delay	57387	U16	1	S
LED load current	57388	U16	10	mA
Special power control	57389	U16	1
Historical data of the current day	61440	U16	1
Data before the current day	61441	U16	1

link settings as documented (unverified): RTU; FC 03,06,16,120,121; Start character: >10ms, End character: >10ms. 00H is a broadcast address to which all slaves respond but do not return commands.

bench facts as documented (unverified)

max registers/read	125
inter-frame delay	10 ms
broadcast	supported
model register	0x000C
serial register	0x0018
firmware register	0x0014
FC 43 device ID	not supported

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

The official MODBUS Protocol document contains a typo in its temperature parsing example, stating that a register value of 800AH (0x800A) indicates a battery temperature of -10 °C. In reality, the battery temperature is stored in the low byte of register 0x0103, where the highest bit (bit 7) is the sign bit. A battery temperature of -10 °C is represented by 0x8A in the low byte (e.g., 0x008A), whereas 0x800A represents a controller temperature of -0 °C and a battery temperature of +10 °C. [source]
Writing 0 to the load control register 0x010A to turn off the load does not work on some firmware versions. Once the load is turned on by writing 1 to 0x010A, writing 0 back to it does nothing. To turn the load off, users must work around this by changing the load working mode (register 0xE01D) to 14 and then back to 15. [source]
The default Modbus slave address for some Renogy controllers (especially when communicating via the BT-1 Bluetooth module) is undocumented as 255 (0xFF) instead of the standard Modbus default of 1. [source]
confirmed: RTU framing and function codes 3, 6, 16, 120, 121 — confirmed by official Renogy Rover MODBUS Protocol document [1.1.2]
confirmed: Start/End character delay >10ms — confirmed by official Renogy Rover MODBUS Protocol document
confirmed: 00H broadcast address behavior — confirmed by official Renogy Rover MODBUS Protocol document
confirmed: Identification registers (firmware @ 0x0014, model @ 0x000C, serial @ 0x0018) — confirmed by floreno/renogy-rover-modbus GitHub repository
confirmed: Register map addresses (battery SOC @ 0x0100, battery voltage @ 0x0101, charging current @ 0x0102, temperatures @ 0x0103) — confirmed by sophienyaa/NodeRenogy GitHub repository
confirmed: Max read/write registers limit of 125 (0x007D) — confirmed by official Renogy Rover MODBUS Protocol document

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.