Schneider Conext Grid-Tie 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 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
inverter_enabled	65	U16	1
device_present	66	U16	1
active_faults_flag	67	U16	1
active_fault_count	68	U16	1
fault_bitmap_0	69	U16	1
configuration_errors	70	U32BE	1
pv_input_voltage	72	U32BE	0.001	V
pv_input_current	74	U32BE	0.001	A
pv_input_power	76	U32BE	1	W
grid_ac_voltage	78	U32BE	0.001	V
grid_ac_current	80	U32BE	0.001	A
grid_ac_frequency	82	U16	0.01	Hz
inverter_status	83	U16	1
grid_ac_power	84	U32BE	1	W
ac_power_to_load	86	U32BE	1	W
ac_power_to_grid	88	U32BE	1	W
energy_from_pv_this_hour	96	U32BE	0.001	kWh
pv_input_active_this_hour	98	U32BE	1	s
energy_from_pv_today	100	U32BE	0.001	kWh
pv_input_active_today	102	U32BE	1	s
energy_from_pv_this_week	104	U32BE	0.001	kWh
pv_input_active_week	106	U32BE	1	s
energy_from_pv_this_month	108	U32BE	0.001	kWh
pv_input_active_month	110	U32BE	1	s
energy_from_pv_this_year	112	U32BE	0.001	kWh
pv_input_active_year	114	U32BE	1	s
energy_from_pv_lifetime	116	U32BE	0.001	kWh
pv_input_active_lifetime	118	U32BE	1	s
grid_output_energy_this_hour	120	U32BE	0.001	kWh
grid_output_active_this_hour	122	U32BE	1	s
grid_output_energy_today	124	U32BE	0.001	kWh
grid_output_active_today	126	U32BE	1	s
grid_output_energy_this_week	128	U32BE	0.001	kWh
grid_output_active_this_week	130	U32BE	1	s
grid_output_energy_this_month	132	U32BE	0.001	kWh
grid_output_active_this_month	134	U32BE	1	s
grid_output_energy_this_year	136	U32BE	0.001	kWh
grid_output_active_this_year	138	U32BE	1	s
grid_output_energy_lifetime	140	U32BE	0.001	kWh
grid_output_active_lifetime	142	U32BE	1	s
ac_to_load_energy_this_hour	144	U32BE	0.001	kWh
ac_to_load_active_this_hour	146	U32BE	1	s
ac_to_load_energy_today	148	U32BE	0.001	kWh
ac_to_load_active_today	150	U32BE	1	s
ac_to_load_energy_this_week	152	U32BE	0.001	kWh
ac_to_load_active_this_week	154	U32BE	1	s
ac_to_load_energy_this_month	156	U32BE	0.001	kWh
ac_to_load_active_this_month	158	U32BE	1	s
ac_to_load_energy_this_year	160	U32BE	0.001	kWh
ac_to_load_active_this_year	162	U32BE	1	s
ac_to_load_energy_lifetime	164	U32BE	0.001	kWh
ac_to_load_active_lifetime	166	U32BE	1	s
ac_to_grid_energy_this_hour	168	U32BE	0.001	kWh
ac_to_grid_active_this_hour	170	U32BE	1	s
ac_to_grid_energy_today	172	U32BE	0.001	kWh
ac_to_grid_active_today	174	U32BE	1	s
ac_to_grid_energy_this_week	176	U32BE	0.001	kWh
ac_to_grid_active_this_week	178	U32BE	1	s
ac_to_grid_energy_this_month	180	U32BE	0.001	kWh
ac_to_grid_active_this_month	182	U32BE	1	s
ac_to_grid_energy_this_year	184	U32BE	0.001	kWh
ac_to_grid_active_this_year	186	U32BE	1	s
ac_to_grid_energy_lifetime	188	U32BE	0.001	kWh
ac_to_grid_active_lifetime	190	U32BE	1	s

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. LOSS OF CONTROL: Do not assign the same address to two Modbus devices. — 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
identification notes	Unique ID Number is located at register 0x0014
doc revision	Revision A.4

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.