Accuenergy Acuvim II power meter

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
frequency	16384	F32BE	1
phase_1_voltage	16386	F32BE	1
phase_2_voltage	16388	F32BE	1
phase_3_voltage	16390	F32BE	1
average_phase_voltage	16392	F32BE	1
line_voltage_1_2	16394	F32BE	1
line_voltage_2_3	16396	F32BE	1
line_voltage_3_1	16398	F32BE	1
average_line_voltage	16400	F32BE	1
phase_a_current	16402	F32BE	1
phase_b_current	16404	F32BE	1
phase_c_current	16406	F32BE	1
average_phase_current	16408	F32BE	1
neutral_current	16410	F32BE	1
phase_a_power	16412	F32BE	1
phase_b_power	16414	F32BE	1
phase_c_power	16416	F32BE	1
total_system_power	16418	F32BE	1
phase_a_reactive_power	16420	F32BE	1
phase_b_reactive_power	16422	F32BE	1
phase_c_reactive_power	16424	F32BE	1
total_reactive_power	16426	F32BE	1
phase_a_apparent_power	16428	F32BE	1
phase_b_apparent_power	16430	F32BE	1
phase_c_apparent_power	16432	F32BE	1
total_apparent_power	16434	F32BE	1
phase_a_power_factor	16436	F32BE	1
phase_b_power_factor	16438	F32BE	1
phase_c_power_factor	16440	F32BE	1
total_power_factor	16442	F32BE	1
voltage_unbalance	16444	F32BE	1
current_unbalance	16446	F32BE	1
power_demand	16450	F32BE	1
reactive_power_demand	16452	F32BE	1
apparent_power_demand	16454	F32BE	1
consumed_energy	16456	U32BE	0.1
generated_energy	16458	U32BE	0.1
consumed_reactive_energy	16460	U32BE	0.1
generated_reactive_energy	16462	U32BE	0.1
total_energy	16464	U32BE	0.1
net_energy	16466	U32BE	0.1
total_reactive_energy	16468	U32BE	0.1
net_reactive_energy	16470	U32BE	0.1
apparent_energy	16472	U32BE	0.1
thd_v1	16474	U16	0.01
thd_v2	16475	U16	0.01
thd_v3	16476	U16	0.01
thd_avg_voltage	16477	U16	0.01
thd_i1	16478	U16	0.01
thd_i2	16479	U16	0.01
thd_i3	16480	U16	0.01
thd_avg_current	16481	U16	0.01

link settings as documented (unverified): RTU; default 19200 8N1; unit ID 1; FC 03,16

bench facts as documented (unverified)

protocol notes

The default value of CT1 and CT2 depends on the Current Input of the meter (CT2).

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

By default, the meter is in Secondary Mode, which requires Modbus register values to be scaled by a relationship (e.g., multiplying by PT1/PT2 or CT1/CT2). To read the actual physical values directly without manual scaling, the 'Real-Time Reading' setting (S28 Para Mode) must be manually changed to 'Primary' mode. [source]
confirmed: Baud rates [1200, 2400, 4800, 9600, 19200, 38400] — confirmed by Acuvim II Series Power Meter User Manual
confirmed: Default baud rate 19200 — confirmed by Acuvim II Series Power Meter User Manual
confirmed: Default unit ID 1 — confirmed by Acuvim II Series Power Meter User Manual
confirmed: Framing RTU — confirmed by Acuvim II Series Power Meter User Manual
confirmed: Function codes 3 and 16 — confirmed by Acuvim II Series Power Meter User Manual
confirmed: Parity N and stop bits 1 — confirmed by Acuvim II Series Power Meter User Manual
confirmed: The default value of CT1 and CT2 depends on the Current Input of the meter (CT2) — confirmed by Acuvim II Series Power Meter User Manual
confirmed: Register map summary (e.g., frequency @ 16384, phase_1_voltage @ 16386, total_system_power @ 16418, total_energy @ 16464) — confirmed by Acuvim II Modbus Map

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.