Pace P16S-series LiFePO4 BMS (RS485 Modbus)

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
current	0	I16	0.01	10mA
voltage_of_pack	1	U16	0.01	10mV
soc	2	U16	1	%
soh	3	U16	1	%
remain_capacity	4	U16	0.01	10mAH
full_capacity	5	U16	0.01	10mAH
design_capacity	6	U16	0.01	10mAH
battery_cycle_counts	7	U16	1	Cyc.
warning_flag	9	U16	1	Hex
protection_flag	10	U16	1	Hex
status_fault_flag	11	U16	1	Hex
balance_status	12	U16	1	Hex
cell_voltage_1	15	U16	0.001	mV
cell_voltage_2	16	U16	0.001	mV
cell_voltage_3	17	U16	0.001	mV
cell_voltage_4	18	U16	0.001	mV
cell_voltage_5	19	U16	0.001	mV
cell_voltage_6	20	U16	0.001	mV
cell_voltage_7	21	U16	0.001	mV
cell_voltage_8	22	U16	0.001	mV
cell_voltage_9	23	U16	0.001	mV
cell_voltage_10	24	U16	0.001	mV
cell_voltage_11	25	U16	0.001	mV
cell_voltage_12	26	U16	0.001	mV
cell_voltage_13	27	U16	0.001	mV
cell_voltage_14	28	U16	0.001	mV
cell_voltage_15	29	U16	0.001	mV
cell_voltage_16	30	U16	0.001	mV
cell_temperature_1	31	I16	0.1	0.1°C
cell_temperature_2	32	I16	0.1	0.1°C
cell_temperature_3	33	I16	0.1	0.1°C
cell_temperature_4	34	I16	0.1	0.1°C
mosfet_temperature	35	I16	0.1	0.1°C
environment_temperature	36	I16	0.1	0.1°C

link settings as documented (unverified): RTU; default 9600 8N1; FC 03,16; Timeout: 200mS, Interval time of the frame: > 100mS

bench facts as documented (unverified)

max registers/read	125
response timeout	200 ms
inter-frame delay	100 ms
model register	160
serial register	170
firmware register	150
doc revision	V1.3

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

The PACE_MODBUS protocol is often not enabled by default on many firmware versions and must be manually activated using PbmsTools.exe (System Config -> Inverter protocol -> RS485 Protocol). [source]
confirmed: comms defaults (9600 baud, 8N1, RTU, Function Codes 3 and 16) — confirmed by PACE BMS Modbus Protocol for RS485 V1.3 [2.3.1]
confirmed: register map (current @ 0, voltage_of_pack @ 1, cell_voltage_1 @ 15, cell_temperature_1 @ 31, etc.) — confirmed by PACE BMS Modbus Protocol for RS485 V1.3
confirmed: identification registers (firmware @ 150, model @ 160, serial @ 170) — confirmed by PACE BMS Modbus Protocol for RS485 V1.3
confirmed: quirks (inter-frame delay > 100ms, response timeout 200ms) — confirmed by PACE BMS Modbus Protocol for RS485 V1.3

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.