CPS 14-36kW SC/SCA inverter

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
inverter_firmware_version	5	U16	0.01
total_lifetime_energy	22	U32BE	1	kWh
daily_energy	24	U16	0.1	kWh
power_factor	26	I16	0.001
max_active_power_daily	27	U16	0.1	kW
active_power	29	U16	0.1	kW
apparent_power	30	U16	0.1	kVA
grid_voltage_uab	31	U16	0.1	V
grid_voltage_ubc	32	U16	0.1	V
grid_voltage_uca	33	U16	0.1	V
grid_a_phase_current	34	U16	0.1	A
grid_b_phase_current	35	U16	0.1	A
grid_c_phase_current	36	U16	0.1	A
dc_voltage_mppt1	37	U16	0.1	V
dc_current_mppt1	38	U16	0.1	A
dc_voltage_mppt2	39	U16	0.1	V
dc_current_mppt2	40	U16	0.1	A
grid_frequency	43	U16	0.1	Hz
heatsink_temperature	44	I16	0.1	C
internal_temperature	45	I16	0.1	C
inverter_state	47	U16	1
permanent_fault_alarm	52	U16	1
warning_alarm	53	U16	1
fault0_alarm	54	U16	1
fault1_alarm	55	U16	1
fault2_alarm	56	U16	1
fault3_alarm	57	U16	1
fault4_alarm	58	U16	1
power_on_off_cmd	4096	U16	1
temporary_active_power_setting	4097	U16	0.1	%
temporary_power_factor_setting	4098	I16	0.001
temporary_reactive_power_setting	4099	U16	0.1	%

link settings as documented (unverified): RTU; baud 9600/19200; FC 03,04,06,16; Half-Duplex, Data Bits: 8

bench facts as documented (unverified)

connector	RS485
sentinel values	Not Implemented for an int16 is 0x8000. Not Implemented for a uint16 is 0xFFFF. Not Implemented for an int32 is 0x80000000. Not Implemented for a uint32 is 0xFFFFFFFF. Not Implemented for a string is 0x00.
model register	0x000A
serial register	0x0006
firmware register	0x0005
doc revision	1.0

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

confirmed: comms defaults (baud rates [9600, 19200], RTU framing, parity N, stop bits 1, half-duplex, 8 data bits) — confirmed by 'CPS Modbus Communications For Inverter Models CPS 14-36kW Version 1.0' manual
confirmed: function codes (3, 4, 6, 16) — confirmed by 'CPS Modbus Communications' manual sections 2.1 and 2.3
confirmed: identification registers (firmware_register 0x0005, model_register 0x000A, serial_register 0x0006) — confirmed by 'CPS Modbus Communications' manual register tables
confirmed: sentinel values for un-implemented data types (int16: 0x8000, uint16: 0xFFFF, int32: 0x80000000, uint32: 0xFFFFFFFF, string: 0x00) — confirmed by 'CPS Modbus Communications' manual section 1.3
confirmed: register map addresses (e.g., daily_energy @ 24, active_power @ 29, grid_voltage_uab @ 31, heatsink_temperature @ 44, inverter_state @ 47, power_on_off_cmd @ 4096) — confirmed by 'CPS Modbus Communications' manual register tables and AGG Software Chint Power mapping

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.