Eaton IQ250/IQ260 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 only confirmed at the hardware-verified rung.

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
volts_a_n	999	F32BE	1	V
volts_b_n	1001	F32BE	1	V
volts_c_n	1003	F32BE	1	V
volts_a_b	1005	F32BE	1
volts_b_c	1007	F32BE	1
volts_c_a	1009	F32BE	1
amps_a	1011	F32BE	1	A
amps_b	1013	F32BE	1	A
amps_c	1015	F32BE	1	A
watts_3ph_total	1017	F32BE	1	W
vars_3ph_total	1019	F32BE	1	var
vas_3ph_total	1021	F32BE	1	VA
power_factor_3ph_total	1023	F32BE	1	none
frequency	1025	F32BE	1	Hz
neutral_current	1027	F32BE	1	A
watts_phase_a	1029	F32BE	1
watts_phase_b	1031	F32BE	1
watts_phase_c	1033	F32BE	1
vars_phase_a	1035	F32BE	1
vars_phase_b	1037	F32BE	1
vars_phase_c	1039	F32BE	1
vas_phase_a	1041	F32BE	1
vas_phase_b	1043	F32BE	1
vas_phase_c	1045	F32BE	1
power_factor_phase_a	1047	F32BE	1
power_factor_phase_b	1049	F32BE	1
power_factor_phase_c	1051	F32BE	1
w_hours_received	1499	U32BE	1
w_hours_delivered	1501	U32BE	1
w_hours_net	1503	U32BE	1
w_hours_total	1505	U32BE	1
var_hours_positive	1507	U32BE	1
var_hours_negative	1509	U32BE	1
var_hours_net	1511	U32BE	1
var_hours_total	1513	U32BE	1
va_hours_total	1515	U32BE	1
volts_a_n_thd	5999	U16	0.01
volts_b_n_thd	6000	U16	0.01
volts_c_n_thd	6001	U16	0.01
amps_a_thd	6002	U16	0.01
amps_b_thd	6003	U16	0.01
amps_c_thd	6004	U16	0.01

link settings as documented (unverified): RTU/ASCII; baud 9600/19200/38400/57600; FC 03,06,16,35; Modbus Function Code 0x23 (35) is a user-defined function code used for log retrieval with repeat counts.

bench facts as documented (unverified)

protocol notes	A 'babbling log' occurs when a log fills a flash sector in less than an hour. In LIMP state, the meter reboots at 5 minute intervals.
model register	0010
serial register	0008
firmware register	0011
identification notes	Meter Serial Number is located at registers 0008 - 000F (Hex).
FC 43 device ID	not supported

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

confirmed: Baud rates [9600, 19200, 38400, 57600], framing [RTU, ASCII], parity [N], and stop bits [1] — confirmed by Eaton IQ 250/260 series power meters technical datasheet
confirmed: Modbus Function Code 0x23 (35) is a user-defined function code used for log retrieval with repeat counts — confirmed by Eaton IQ 250/260 Modbus Register Map Guide
confirmed: Meter Serial Number is located at registers 0008 - 000F (Hex) — confirmed by Eaton IQ 250/260 Modbus Register Map Guide
confirmed: Model register is 0010 (Hex) and Firmware register is 0011 (Hex) — confirmed by Eaton IQ 250/260 Modbus Register Map Guide
confirmed: A 'babbling log' occurs when a log fills a flash sector in less than an hour, and in LIMP state, the meter reboots at 5 minute intervals — confirmed by Eaton IQ 250/260 Modbus Register Map Guide
confirmed: Register map addresses (e.g., volts_a_n @ 999, w_hours_received @ 1499, volts_a_n_thd @ 5999) — confirmed by Eaton IQ 250/260 Modbus Register Map Guide

generated by gemini:gemini-3.5-flash · harvested from https://www.eaton.com/content/dam/eaton/products/low-voltage-power-distribution-controls-systems/power-energy-meters/power-xpert-meter-2000-series/iq250-260-and-pxm2k-modbus-register-map-ib02601006e.pdf (Eaton); manual-faithful — the document's claims, panel risk: ELEVATED — panel is not confident; proved interop-verified on 2026-06-10 · recorded 2026-06-10

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.

Have a device that isn't here? Upload its register map — generation is free, and the connector earns its rung by being proven, not claimed.

Need it proven on your own device? Hardware verification — if it doesn't verify, you don't pay.

Building a platform? License the verified library — machine-readable maps, firmware matrix, API access.