Epever B-series charge controller

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
pv_array_input_voltage	12544	U16	0.01	V
pv_array_input_current	12545	U16	0.01	A
pv_array_input_power	12546	U32LE	0.01	W
load_voltage	12556	U16	0.01	V
load_current	12557	U16	0.01	A
load_power	12558	U32LE	0.01	W
battery_temperature	12560	I16	0.01	℃
device_temperature	12561	I16	0.01	℃
battery_soc	12570	U16	1	%
battery_real_rated_voltage	12573	U16	0.01	V
battery_status	12800	U16	1
charging_equipment_status	12801	U16	1
discharging_equipment_status	12802	U16	1
max_battery_voltage_today	13058	U16	0.01	V
min_battery_voltage_today	13059	U16	0.01	V
consumed_energy_today	13060	U32LE	0.01	kWh
consumed_energy_this_month	13062	U32LE	0.01	kWh
consumed_energy_this_year	13064	U32LE	0.01	kWh
total_consumed_energy	13066	U32LE	0.01	kWh
generated_energy_today	13068	U32LE	0.01	kWh
generated_energy_this_month	13070	U32LE	0.01	kWh
generated_energy_this_year	13072	U32LE	0.01	kWh
total_generated_energy	13074	U32LE	0.01	kWh
battery_voltage	13082	U16	0.01	V
battery_current	13083	U32LE	0.01	A
array_rated_voltage	12288	U16	0.01	V
array_rated_current	12289	U16	0.01	A
array_rated_power	12290	U32LE	0.01	W
battery_rated_voltage	12292	U16	0.01	V
battery_rated_current	12293	U16	0.01	A
battery_rated_power	12294	U32LE	0.01	W
rated_load_voltage	12301	U16	0.01	V
rated_load_current	12302	U16	0.01	A
rated_load_power	12303	U32LE	0.01	W

link settings as documented (unverified): RTU; default 115200 8?1; unit ID 1; FC 02,03,04,05,16; Serial communication parameters: baud rate 115200, data bits 8, stop bits 1, no data flow control.

bench facts as documented (unverified)

connector	RJ45
wiring notes	RJ45 interface pin define for RS485 port of LS-B, VS-B, Tracer-B, Tracer-A series. Interface pin definition for RS485 and RS232 port of iTracer, eTracer series.
protocol notes	All 32-bit-length data uses two 16-bit registers to represent (L and H register, respectively)

generated by gemini:gemini-3.5-flash · harvested from https://www.img4.cz/i4wifi/attach/StoItem/7069/MODBUS-Protocol-v25.pdf (Epever); 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.