OutBack Radian/FX/FLEXmax (needs AXS Port module, SunSpec)
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 |
|---|
| 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 | |
link settings as documented (unverified): TCP; Uses Ethernet access implemented by Modbus TCP. Default Modbus IP port is 502.
bench facts as documented (unverified)
| 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). |
field reports — community-sourced, unverified (checked 2026-06-11)
- Modbus TCP connections frequently drop or disconnect (often every 1 to 2 minutes, or up to 16 minutes) when OPTICSre is enabled or under high polling frequencies. OutBack introduced an 'OPTICS Auto Reboot Interval' setting to reboot the device every few hours to mitigate lockups. [source]
- A low-level Modbus socket error is occasionally triggered by a Modbus Write action, requiring a reset that takes approximately 42 seconds for the MATE3 to recover. [source]
- MATE3 firmware version 003.015.005 introduced changes to the Modbus protocol that rendered older versions of monitoring software (like WattPlot Monitor, VisualMATE, NetMATE) inoperative until patched. [source]
- AXS Port firmware version 003.017.000 fixed bugs where disabling Modbus encryption after it was set to encrypt did not operate correctly, and Modbus read/write to devices connected to HUB port 10 failed. [source]
- AXS Port firmware version 003.015.001 fixed bugs where reading of charge controller kW data was incorrect, and 120VAC Radians displayed 2X kW values for Buy, Sell, Charge, and Invert. [source]
- confirmed: Framing is TCP and default Modbus IP port is 502 — confirmed by OutBack AXS Port SunSpec Modbus Interface Owner's Manual and Application Note.
- confirmed: Identification registers (firmware_register 42, model_register 18, serial_register 50) are 0-based offsets relative to SunSpec Common Model Block (DID 1) — confirmed by the open-source mate3/sunspec Python library implementation of SunSpecCommonModel.
- confirmed: Physical connector is RJ45 — confirmed by AXS Port specifications showing a 10/100 Ethernet interface.
- confirmed: Register map summary for Basic Charge Controller Block (DID 64111) matches 0-based offsets — confirmed by OutBack Power SunSpec Data Blocks Application Note (Table 2).
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.