Schneider Conext CL 20/25kVA PV inverter

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
kwh_energy_produced	2050	U32BE	0.1	kWHr/x10
energy_today	2052	U32BE	0.1	kWHr/x10
energy_today_minus_1	2054	U32BE	0.1
energy_today_minus_2	2056	U32BE	0.1
energy_today_minus_3	2058	U32BE	0.1
energy_today_minus_4	2060	U32BE	0.1
energy_today_minus_5	2062	U32BE	0.1
energy_today_na_e	2064	U32BE	0.1
unit_operation_hours	2078	U32BE	1	Hr/x1
operational_mode_state	5888	U16	1
temperature_control_board	5889	I16	0.1	C/X10
temperature_dc_module_12	5890	I16	0.1
temperature_dc_module_34	5891	I16	0.1
grid_current_sum	5893	U16	0.1	A/X10
temperature_inverter_module_a	5894	I16	0.1
temperature_inverter_module_b	5895	I16	0.1
temperature_inverter_module_c	5896	I16	0.1
phase_a_to_neutral_voltage	5897	I16	0.1	Vrms/X10
phase_b_to_neutral_voltage	5898	I16	0.1
phase_c_to_neutral_voltage	5899	I16	0.1
grid_apparent_power	6129	U16	0.1	KVA/X10
grid_reactive_power	6132	I16	0.1	KVAr/X10
grid_voltage_v12	6136	I16	0.1
grid_voltage_v23	6137	I16	0.1
grid_voltage_v31	6138	I16	0.1
grid_current_line_1	6139	I16	0.1
grid_current_line_2	6140	I16	0.1
grid_current_line_3	6141	I16	0.1
active_power	6142	I16	0.1	KW/X10
pv1_voltage	6143	I16	0.1
pv1_current	6144	I16	0.1
pv1_power	6145	I16	0.1
grid_frequency	6146	U16	0.1	Hz/X10
phase_a_frequency	6168	U16	0.1
phase_b_frequency	6169	U16	0.1
phase_c_frequency	6170	U16	0.1
phase_a_real_power	6171	I16	0.1
phase_b_real_power	6172	I16	0.1
phase_c_real_power	6173	I16	0.1
inverter_alarm_code	6184	U16	1
pv2_voltage	6185	I16	0.1
pv2_current	6186	I16	0.1
pv2_power	6191	I16	0.1

link settings as documented (unverified): RTU/TCP; default 9600 8N1; unit ID 10; FC 03,06,16,43; Addresses are 0 based ('on the wire' addressing) and not 1 based ('traditional' addressing).

bench facts as documented (unverified)

broadcast	supported
sentinel values	All unused address contains a value 0xFF and no exception occurs in Conext CL.
protocol notes	Broadcast is used only by Schneider Electric Monitoring Devices and not recommended for other Users.
model register	0x0028
serial register	0x0014
firmware register	0x0340
FC 43 device ID	supported
doc revision	1.5

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

confirmed: Baud rates [9600, 19200, 38400, 57600, 115200] and default baud rate 9600 — confirmed by Conext CL Modbus Registers Map Rev 1.5
confirmed: Default unit ID (slave address) is 10 — confirmed by Conext CL Modbus Registers Map Rev 1.5
confirmed: Framing RTU and TCP are supported — confirmed by Conext CL Modbus Registers Map Rev 1.5
confirmed: Function codes 3, 6, 16, and 43 are supported — confirmed by Conext CL Modbus Registers Map Rev 1.5
confirmed: Addresses are 0-based ('on the wire' addressing) — confirmed by Conext CL Modbus Registers Map Rev 1.5
confirmed: Default parity is None (N) and stop bits is 1 — confirmed by Conext CL Modbus Registers Map Rev 1.5
confirmed: Document revision is 1.5 — confirmed by Conext CL Modbus Registers Map Rev 1.5
confirmed: Identification registers (firmware_register: 0x0340, model_register: 0x0028, serial_register: 0x0014) — confirmed by Conext CL Modbus Registers Map Rev 1.5

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.