Xantrex Freedom SW inverter-charger

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
device_state	64	U16	1
device_present	65	U16	1
inverter_enabled	66	U16	1
charger_enabled	67	U16	1
active_faults_flag	68	U16	1
active_warnings_flag	69	U16	1
charge_mode_status	70	U16	1
fault_bitmap_0	71	U16	1
fault_bitmap_1	72	U16	1
fault_bitmap_2	73	U16	1
warning_bitmap_0	74	U16	1
inverter_status	75	U16	1
configuration_errors	76	U32BE	1
battery_voltage	78	U32BE	0.001	V
battery_current	80	U32BE	0.001	A
battery_power	82	U32BE	1	W
battery_temperature	84	U16	0.01	deg C
charger_status	85	U16	1
invert_dc_current	86	U32BE	0.001	A
invert_dc_power	88	U32BE	1	W
charge_dc_current	90	U32BE	0.001	A
charge_dc_power	92	U32BE	1	W
charge_dc_power_percentage	94	U16	1	%
ac1_frequency	95	U16	0.01	Hz
ac1_voltage	96	U32BE	0.001	V
ac1_input_current	98	U32BE	0.001	A
ac1_input_power	100	U32BE	1	W
ac1_input_power_apparent	102	U32BE	1	VA
ac1_voltage_qualified	112	U16	1
ac1_frequency_qualified	113	U16	1
ac1_qualified_duration	114	U32BE	1	s
load_ac_voltage	120	U32BE	0.001	V
load_ac_current	130	U32BE	0.001	A
load_ac_power	132	U32BE	1	W
load_ac_power_apparent	138	U32BE	1	VA
load_ac_frequency	140	U16	0.01	Hz
energy_from_battery_this_hour	144	U32BE	0.001	kWh
battery_discharge_active_this_hour	146	U32BE	1	s
energy_from_battery_today	148	U32BE	0.001	kWh
battery_discharge_active_today	150	U32BE	1	s
energy_from_battery_this_week	152	U32BE	0.001	kWh
battery_discharge_active_this_week	154	U32BE	1	s
energy_from_battery_this_month	156	U32BE	0.001	kWh
battery_discharge_active_this_month	158	U32BE	1	s
energy_from_battery_this_year	160	U32BE	0.001	kWh
battery_discharge_active_this_year	162	U32BE	1	s
energy_from_battery_lifetime	164	U32BE	0.001	kWh
battery_discharge_active_lifetime	166	U32BE	1	s
energy_to_battery_this_hour	168	U32BE	0.001	kWh
battery_charge_active_this_hour	170	U32BE	1	s
energy_to_battery_today	172	U32BE	0.001	kWh
battery_charge_active_today	174	U32BE	1	s
energy_to_battery_this_week	176	U32BE	0.001	kWh
battery_charge_active_this_week	178	U32BE	1	s
energy_to_battery_this_month	180	U32BE	0.001	kWh
battery_charge_active_this_month	182	U32BE	1	s
energy_to_battery_this_year	184	U32BE	0.001	kWh
battery_charge_active_this_year	186	U32BE	1	s
energy_to_battery_lifetime	188	U32BE	0.001	kWh
battery_charge_active_lifetime	190	U32BE	1	s
ac1_input_energy_this_hour	192	U32BE	0.001	kWh
ac1_input_active_this_hour	194	U32BE	1	s
ac1_input_energy_today	196	U32BE	0.001	kWh
ac1_input_active_today	198	U32BE	1	s
ac1_input_energy_this_week	200	U32BE	0.001	kWh
ac1_input_active_this_week	202	U32BE	1	s
ac1_input_energy_this_month	204	U32BE	0.001	kWh
ac1_input_active_this_month	206	U32BE	1	s
ac1_input_energy_this_year	208	U32BE	0.001	kWh
ac1_input_active_this_year	210	U32BE	1	s
ac1_input_energy_lifetime	212	U32BE	0.001	kWh
ac1_input_active_lifetime	214	U32BE	1	s
load_output_energy_this_hour	216	U32BE	0.001	kWh
load_output_active_this_hour	218	U32BE	1	s
load_output_energy_today	220	U32BE	0.001	kWh
load_output_active_today	222	U32BE	1	s
load_output_energy_this_week	224	U32BE	0.001	kWh
load_output_active_this_week	226	U32BE	1	s
load_output_energy_this_month	228	U32BE	0.001	kWh
load_output_active_this_month	230	U32BE	1	s
load_output_energy_this_year	232	U32BE	0.001	kWh
load_output_active_this_year	234	U32BE	1	s
load_output_energy_lifetime	236	U32BE	0.001	kWh
load_output_active_lifetime	238	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. 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.
serial register	0x002B
firmware register	0x001E
identification notes	Device Name is at 0x0000, FGA Number is at 0x000A, Unique ID Number is at 0x0014.
doc revision	Revision A.4
firmware applicability	The Conext Freedom SW Device Modbus map applies to the following products: 815-2012, 815-2024, 815-2524-02, 815-3012, 815-3024, 815-3524-02.

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.

If your device isn't here, upload its register map. Generation is free, and the connector keeps the rung it earns under testing.

To prove a connector against your own device, order hardware verification. If it doesn't verify, you don't pay.

Platform builders can license the verified library: machine-readable maps, the firmware matrix, API access.