Schneider Conext MPPT 60-150 charge controller

Register map(s) for this device, with a note of how far each has been checked. Addresses are 0-based, as on the wire. Scale and byte order are confirmed only at the hardware-verified rung.

coherence-checked

Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.

point	address (0-based)	type	scale	unit
device_state	64	U16	1
charger_enabled	65	U16	1
device_present	66	U16	1
charge_mode_status	67	U16	1
active_faults_flag	68	U16	1
active_warnings_flag	69	U16	1
fault_bitmap_0	70	U16	1
fault_bitmap_1	71	U16	1
warning_bitmap_0	72	U16	1
charger_status	73	U16	1
input_dc_voltage	76	U32BE	0.001	V
input_dc_current	78	U32BE	0.001	A
input_dc_power	80	U32BE	1	W
battery_temperature	86	U16	0.01	deg C
output_dc_voltage	88	U32BE	0.001	V
output_dc_current	90	U32BE	0.001	A
output_dc_power	92	U32BE	1	W
dc_power_output_percentage	94	U16	1	%
auxiliary_output_status	95	U16	1
auxiliary_output_voltage	96	U32BE	0.001	V
energy_from_pv_this_hour	102	U32BE	0.001	kWh
pv_input_active_this_hour	104	U32BE	1	s
energy_from_pv_today	106	U32BE	0.001	kWh
pv_input_active_today	108	U32BE	1	s
energy_from_pv_this_week	110	U32BE	0.001	kWh
pv_input_active_this_week	112	U32BE	1	s
energy_from_pv_this_month	114	U32BE	0.001	kWh
pv_input_active_this_month	116	U32BE	1	s
energy_from_pv_this_year	118	U32BE	0.001	kWh
pv_input_active_this_year	120	U32BE	1	s
energy_from_pv_lifetime	122	U32BE	0.001	kWh
pv_input_active_lifetime	124	U32BE	1	s
energy_to_battery_this_hour	126	U32BE	0.001	kWh
battery_charge_active_this_hour	128	U32BE	1	s
energy_to_battery_today	130	U32BE	0.001	kWh
battery_charge_active_today	132	U32BE	1	s
energy_to_battery_this_week	134	U32BE	0.001	kWh
battery_charge_active_this_week	136	U32BE	1	s
energy_to_battery_this_month	138	U32BE	0.001	kWh
battery_charge_active_this_month	140	U32BE	1	s
energy_to_battery_this_year	142	U32BE	0.001	kWh
battery_charge_active_this_year	144	U32BE	1	s
energy_to_battery_lifetime	146	U32BE	0.001	kWh
battery_charge_active_lifetime	148	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. 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. LOSS OF CONTROL: Do not assign the same address to two Modbus devices. The entire serial bus may behave unexpectedly if the master device cannot communicate with all the slave devices on the bus. — 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

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.
coherence-checked — Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.
hardware-verified (software-key) x1 — Matched a real device with operator-attested readings as ground truth — the only rung that confirms word order + scaling on the wire.

Device not here? Upload its manual and get a checked map back. It's free.

Want it confirmed against your own device? Order hardware verification. If it doesn't check out, you don't pay.

Building on a lot of devices? License the library — machine-readable maps, the firmware matrix, and API access.