Schneider Conext Battery Monitor

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_state	64	U16	1
device_present	65	U16	1
configuration_errors	66	U32BE	1
dc_source_id	68	U32BE	1
battery_voltage	70	U32BE	0.001	V
battery_current	72	U32BE	0.001	A
battery_temperature	74	U32BE	0.01	deg C
battery_state_of_charge	76	U32BE	1	%
battery_state_of_health	78	U32BE	1	%
battery_percent_over_charge	80	U32BE	1	%
battery_midpoint_1_voltage	82	U32BE	0.001	V
battery_midpoint_2_voltage	84	U32BE	0.001	V
battery_midpoint_3_voltage	86	U32BE	0.001	V
battery_capacity_remaining	88	U32BE	1	Ah
battery_capacity_removed	90	U32BE	1	Ah
battery_bts_present	92	U32BE	1
battery_time_to_full	94	U32BE	1	Min
battery_time_to_discharge	96	U32BE	1	Min
battery_hours_in_float	98	U32BE	0.1	Hr
battery_last_equalize	100	U32BE	1	Days
battery_average_discharge	102	I16	1	Ah
battery_average_discharge_percent	103	I16	0.01	%
battery_deepest_discharge	104	I16	1	Ah
battery_deepest_discharge_percent	105	I16	0.01	%
battery_capacity_removed_alt	106	U32BE	1	Ah
battery_capacity_returned	108	U32BE	1	Ah
battery_number_of_charge_cycles	110	U16	1
battery_number_of_synchronizations	111	U16	1
battery_number_of_discharges	112	U16	1

link settings as documented (unverified): baud 9600/19200/38400/57600/115200; RS485 settings (Address, Baud Rate, Parity, Stop Bits, Byte Order) are available via registers 0x00A0-0x00A4.

bench facts as documented (unverified)

protocol notes	Modbus does not provide an error response when data written to a Modbus Register is out of range or invalid. To confirm that a Modbus Register is correctly written, you should read it back and compare it with the expected value.
model register	0x0000
serial register	0x002B
firmware register	0x001E
doc revision	Revision A.4
firmware applicability	Conext Battery Monitor (Product ID: 865-1080-01)

generated by gemini:gemini-3.5-flash · harvested from https://web.archive.org/web/20170704034313/http://solar.schneider-electric.com/wp-content/uploads/2016/08/Conext-Modbus-Maps-V4.zip (Schneider Electric); manual-faithful — the document's claims, panel risk: ELEVATED — panel is not confident; proved interop-verified on 2026-06-11 · recorded 2026-06-11

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.