SAJ R5/R6/C6 inverter

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
device_type	36608	U16	1
subtype	36609	U16	1
comms_protocol_version	36610	U16	0.001
display_software_version	36631	U16	0.001
master_ctrl_software_version	36632	U16	0.001
slave_ctrl_software_version	36633	U16	0.001
display_board_hardware_version	36634	U16	0.001
ctrl_board_hardware_version	36635	U16	0.001
power_board_hardware_version	36636	U16	0.001
mpv_mode	256	U16	1
pv1_volt	263	U16	0.1	V
pv1_curr	264	U16	0.01	A
pv1_power	265	U16	1	W
pv2_volt	266	U16	0.1	V
pv2_curr	267	U16	0.01	A
pv2_power	268	U16	1	W
pv3_volt	269	U16	0.1	V
pv3_curr	270	U16	0.01	A
pv3_power	271	U16	1	W
bus_volt	272	U16	0.1	V
inv_temp_c	273	I16	0.1	°C
gfci	274	I16	1	mA
power	275	U16	1	W
q_power	276	I16	1	Var
pf	277	I16	0.001
l1_volt	278	U16	0.1	V
l1_curr	279	U16	0.01	A
l1_freq	280	U16	0.01	Hz
l1_dci	281	I16	1	mA
l1_power	282	U16	1	W
l1_pf	283	I16	0.001
l2_volt	284	U16	0.1	V
l2_curr	285	U16	0.01	A
l2_freq	286	U16	0.01	Hz
l2_dci	287	I16	1	mA
l2_power	288	U16	1	W
l2_pf	289	I16	0.001
l3_volt	290	U16	0.1	V
l3_curr	291	U16	0.01	A
l3_freq	292	U16	0.01	Hz
l3_dci	293	I16	1	mA
l3_power	294	U16	1	W
l3_pf	295	I16	0.001
iso1	296	U16	1	kΩ
iso2	297	U16	1	kΩ
iso3	298	U16	1	kΩ
iso4	299	U16	1	kΩ
today_energy	300	U16	0.01	kWh
month_energy	301	U32BE	0.01	kWh
year_energy	303	U32BE	0.01	kWh
total_energy	305	U32BE	0.01	kWh
today_hour	307	U16	0.1	H
total_hour	308	U32BE	0.1	H
error_count	310	U16	1
pv1_str_curr1	315	U16	0.01	A
pv1_str_curr2	316	U16	0.01	A
pv1_str_curr3	317	U16	0.01	A
pv1_str_curr4	318	U16	0.01	A
pv2_str_curr1	319	U16	0.01	A
pv2_str_curr2	320	U16	0.01	A
pv2_str_curr3	321	U16	0.01	A
pv2_str_curr4	322	U16	0.01	A
pv3_str_curr1	323	U16	0.01	A
pv3_str_curr2	324	U16	0.01	A
pv3_str_curr3	325	U16	0.01	A
pv3_str_curr4	326	U16	0.01	A
pv4_str_curr1	327	U16	0.01	A
pv4_str_curr2	328	U16	0.01	A
pv4_str_curr3	329	U16	0.01	A
pv4_str_curr4	330	U16	0.01	A

link settings as documented (unverified): RTU; default 9600 8N1; FC 03,16; UART communication: data bit 8, stop bit 1, no parity check, no flow control. Half duplex.

bench facts as documented (unverified)

terminals	RS232, RS485
wiring notes	Adopts UART half duplex communication mode.
broadcast	supported
model register	8F00H
serial register	8F03H
firmware register	8F17H
doc revision	A

generated by gemini:gemini-3.5-flash · harvested from https://api.library.loxone.com/downloader/file/100/SAJ%20Modbus%C2%A0Protocol_EN_R5.pdf (SAJ); manual-faithful — the document's claims, panel risk: ELEVATED — panel is not confident; 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.