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.
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 |
|---|---|---|---|---|
| cc_did | 0 | U16 | 1 | |
| cc_length | 1 | U16 | 1 | |
| cc_port_number | 2 | U16 | 1 | |
| cc_voltage_sf | 3 | I16 | 1 | |
| cc_current_sf | 4 | I16 | 1 | |
| cc_power_sf | 5 | I16 | 1 | |
| cc_ah_sf | 6 | I16 | 1 | |
| cc_kwh_sf | 7 | I16 | 1 | |
| cc_batt_voltage | 8 | U16 | 0.1 | |
| cc_array_voltage | 9 | U16 | 0.1 | |
| cc_batt_current | 10 | U16 | 0.1 | |
| cc_array_current | 11 | U16 | 1 | |
| cc_charger_state | 12 | U16 | 1 | |
| cc_watts | 13 | U16 | 1 | |
| cc_todays_min_battery_volts | 14 | U16 | 0.1 | |
| cc_todays_max_battery_volts | 15 | U16 | 0.1 | |
| cc_voc | 16 | U16 | 0.1 | |
| cc_todays_peak_voc | 17 | U16 | 1 | |
| cc_todays_kwh | 18 | U16 | 0.1 | |
| cc_todays_ah | 19 | U16 | 1 | |
| cc_lifetime_kwh_hours | 20 | U16 | 1 | |
| cc_lifetime_kamp_hours | 21 | U16 | 0.1 | |
| cc_lifetime_max_watts | 22 | U16 | 1 | |
| cc_lifetime_max_battery_volts | 23 | U16 | 0.1 | |
| cc_lifetime_max_voc | 24 | U16 | 0.1 | |
| cc_temp_sf | 25 | U16 | 1 | |
| cc_temp_output_fets | 26 | I16 | 1 | |
| cc_temp_enclosure | 27 | I16 | 1 |
| connector | RJ45 |
| model register | 18 |
| serial register | 50 |
| firmware register | 42 |
| identification notes | Addresses are 0-based offsets relative to the SunSpec Common Model Block (DID 1). |
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.