Schneider Conext XW/XW+ inverter-charger

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 confirmed at the hardware-verified rung and at no rung below it.

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
fault_bitmap_0	66	U16	1
fault_bitmap_1	67	U16	1
fault_bitmap_2	68	U16	1
fault_bitmap_3	69	U16	1
warning_bitmap_0	70	U16	1
inverter_enabled	71	U16	1
charger_enabled	72	U16	1
sell_enabled	73	U16	1
active_faults_flag	75	U16	1
active_warnings_flag	76	U16	1
charge_mode_status	77	U16	1
battery_voltage	80	U32BE	0.001	V
battery_current	82	U32BE	0.001	A
battery_power	84	U32BE	1	W
battery_temperature	86	U16	0.01	deg C
invert_dc_current	88	U32BE	0.001	A
invert_dc_power	90	U32BE	1	W
charge_dc_current	92	U32BE	0.001	A
charge_dc_power	94	U32BE	1	W
charge_dc_power_percentage	96	U16	1	%
grid_ac_frequency	97	U16	0.01	Hz
grid_ac_voltage	98	U32BE	0.001	V
grid_ac_current	100	U32BE	0.001	A
grid_ac_power	102	U32BE	1	W
grid_ac_input_power_apparent	104	U32BE	1	VA
grid_ac_input_current	106	U32BE	0.001	A
grid_ac_input_power	108	U32BE	1	W
grid_ac_l1_voltage	110	U32BE	0.001	V
grid_ac_l2_current	112	U32BE	0.001	A
grid_ac_l2_voltage	114	U32BE	0.001	V
grid_ac_l1_current	116	U32BE	0.001	A
grid_ac_voltage_qualified	118	U16	1
grid_ac_frequency_qualified	119	U16	1
grid_ac_qualified_duration	120	U32BE	1	s
inverter_status	122	U16	1
charger_status	123	U16	1
grid_output_voltage	126	U32BE	0.001	V
grid_output_current	128	U32BE	0.001	A
grid_output_frequency	130	U16	0.01	Hz
grid_output_power	132	U32BE	1	W
grid_output_power_apparent	138	U32BE	1	VA
load_ac_voltage	140	U32BE	0.001	V
load_ac_l1_voltage	142	U32BE	0.001	V
load_ac_l2_voltage	144	U32BE	0.001	V
load_ac_l1_current	146	U32BE	0.001	A
load_ac_l2_current	148	U32BE	0.001	A
load_ac_current	150	U32BE	0.001	A
load_ac_frequency	152	U16	0.01	Hz
load_ac_power	154	U32BE	1	W
load_ac_power_apparent	160	U32BE	1	VA
generator_ac_voltage	162	U32BE	0.001	V
generator_ac_current	164	U32BE	0.001	A
generator_ac_frequency	166	U16	0.01	Hz
generator_ac_voltage_qualified	167	U16	1
generator_ac_frequency_qualified	168	U16	1
generator_ac_qualified_duration	170	U32BE	1	s
generator_ac_power	172	U32BE	1	W
generator_ac_l1_voltage	178	U32BE	0.001	V
generator_ac_l1_current	180	U32BE	0.001	A
generator_ac_l2_voltage	182	U32BE	0.001	V
generator_ac_l2_current	184	U32BE	0.001	A
generator_ac_power_apparent	186	U32BE	1	VA
auxiliary_output_status	188	U16	1

link settings as documented (unverified): 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.

⚠ UNINTENDED OPERATION: The use of this product with Modbus communications requires expertise in the design, operation, and programming of the device. Only qualified persons should program, install, alter, and commission this product. When writing values to the device, you must ensure other persons are not working with the device. Failure to follow these instructions can result in death or serious injury, and/or equipment damage. — Starkest reads only; we never write a control register.

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.
model register	0x0000
serial register	0x002B
firmware register	0x001E
doc revision	Revision A.4
firmware applicability	Conext XW/XW+ Device Modbus map applies to products: 865-1000, 865-1000-01, 865-1005, 865-1010, 865-1035, 865-1035-61, 865-1040, 865-1040-61, 865-1045, 865-1045-61, 865-6848-01, 865-5548-01, 865-8548-61, 865-7048-61

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

Off-by-one addressing confusion: The Modbus map addresses are documented starting at 1 (1-based indexing) in some vendor contexts, requiring users to subtract 1 to align with standard 0-based Modbus master tools (e.g., Node-RED, Home Assistant). For example, battery_voltage is at address 80 (0x0050) but may need to be queried at 81 depending on the client's offset configuration. [source]
Writing an illegal or out-of-range value to a register can cause the inverter to stop functioning correctly (e.g., failing to sell to the grid), requiring a firmware re-upload to recover. [source]
confirmed: Modbus does not provide an error response when data written to a Modbus Register is out of range or invalid — confirmed by the official 'Modbus Map: Conext™ XW Device' document overview section
confirmed: Conext XW/XW+ Device Modbus map applies to products: 865-1000, 865-1000-01, 865-1005, 865-1010, 865-1035, 865-1035-61, 865-1040, 865-1040-61, 865-1045, 865-1045-61 — confirmed by Table 1 (Applicable Products) in the official Modbus Map document
confirmed: UNINTENDED OPERATION warning text — confirmed by the safety warning section on page 1 of the official Modbus Map document
confirmed: Register addresses (e.g., device_state @ 64 (0x0040), battery_voltage @ 80 (0x0050), battery_temperature @ 86 (0x0056)) — confirmed by the register tables in the official Modbus Map 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.
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.

If your device isn't here, upload its register map. Generation is free, and the connector keeps the rung it earns under testing.

To prove a connector against your own device, order hardware verification. If it doesn't verify, you don't pay.

Platform builders can license the verified library: machine-readable maps, the firmware matrix, API access.