verified connector library

Schneider Conext MPPT 60-150 charge controller

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.

pointaddress (0-based)typescaleunit
device_state64U161
charger_enabled65U161
device_present66U161
charge_mode_status67U161
active_faults_flag68U161
active_warnings_flag69U161
fault_bitmap_070U161
fault_bitmap_171U161
warning_bitmap_072U161
charger_status73U161
input_dc_voltage76U32BE0.001V
input_dc_current78U32BE0.001A
input_dc_power80U32BE1W
battery_temperature86U160.01deg C
output_dc_voltage88U32BE0.001V
output_dc_current90U32BE0.001A
output_dc_power92U32BE1W
dc_power_output_percentage94U161%
auxiliary_output_status95U161
auxiliary_output_voltage96U32BE0.001V
energy_from_pv_this_hour102U32BE0.001kWh
pv_input_active_this_hour104U32BE1s
energy_from_pv_today106U32BE0.001kWh
pv_input_active_today108U32BE1s
energy_from_pv_this_week110U32BE0.001kWh
pv_input_active_this_week112U32BE1s
energy_from_pv_this_month114U32BE0.001kWh
pv_input_active_this_month116U32BE1s
energy_from_pv_this_year118U32BE0.001kWh
pv_input_active_this_year120U32BE1s
energy_from_pv_lifetime122U32BE0.001kWh
pv_input_active_lifetime124U32BE1s
energy_to_battery_this_hour126U32BE0.001kWh
battery_charge_active_this_hour128U32BE1s
energy_to_battery_today130U32BE0.001kWh
battery_charge_active_today132U32BE1s
energy_to_battery_this_week134U32BE0.001kWh
battery_charge_active_this_week136U32BE1s
energy_to_battery_this_month138U32BE0.001kWh
battery_charge_active_this_month140U32BE1s
energy_to_battery_this_year142U32BE0.001kWh
battery_charge_active_this_year144U32BE1s
energy_to_battery_lifetime146U32BE0.001kWh
battery_charge_active_lifetime148U32BE1s

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 notesModbus does not provide an error response when data written to a Modbus Register is out of range or invalid.
model register0x0000
serial register0x002B
firmware register0x001E
doc revisionRevision A.4

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: LOW — panel concurs, no field disagreements; 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.

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.