Studer Xtender/VarioTrack/VarioString (needs Xcom-485 module)

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
xtender_battery_voltage	3000	F32LE	1
xtender_battery_temperature	3001	F32LE	1
xtender_battery_charge_current	3005	F32LE	1
xtender_state_of_charge	3007	F32LE	1
xtender_input_voltage	3011	F32LE	1
xtender_input_current	3012	F32LE	1
xtender_input_power	3013	F32LE	1
xtender_output_voltage	3021	F32LE	1
xtender_output_current	3022	F32LE	1
xtender_output_power	3023	F32LE	1
xtender_input_frequency	3084	F32LE	1
xtender_output_frequency	3085	F32LE	1
xtender_output_active_power	3087	F32LE	1
xtender_input_active_power	3088	F32LE	1
bsp_battery_voltage	7000	F32LE	1
bsp_battery_current	7001	F32LE	1
bsp_state_of_charge	7002	F32LE	1
bsp_power	7003	F32LE	1
bsp_temperature	7005	F32LE	1
variotrack_battery_voltage	11000	F32LE	1
variotrack_battery_current	11001	F32LE	1
variotrack_pv_voltage	11002	F32LE	1
variotrack_pv_current	11003	F32LE	1
variotrack_pv_power	11004	F32LE	1
variostring_battery_voltage	15000	F32LE	1
variostring_battery_current	15001	F32LE	1
variostring_pv_voltage	15004	F32LE	1
variostring_pv_current	15007	F32LE	1
variostring_pv_power	15010	F32LE	1

bench facts as documented (unverified)

doc revision

V1.6.40 (R700)

generated by gemini:gemini-3.5-flash · harvested from https://portal.studer-innotec.com/Content/docs/appendix.pdf (Studer Innotec); 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.