Finder 7M.24/7M.38 energy meter

Register map(s) for this device, with a note of how far each has been checked. Addresses are 0-based, as on the wire. Scale and byte order are confirmed only at the hardware-verified rung.

coherence-checked

Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.

point	address (0-based)	type	scale
run_time	2480	F32BE	1
uavg_ln	2484	F32BE	1
uavg_ll	2486	F32BE	1
active_power_total	2490	F32BE	1
reactive_power_total	2492	F32BE	1
apparent_power_total	2494	F32BE	1
power_factor_total	2496	F32BE	1
frequency	2498	F32BE	1
u1	2500	F32BE	1
u2	2502	F32BE	1
u3	2504	F32BE	1
u12	2508	F32BE	1
u23	2510	F32BE	1
u31	2512	F32BE	1
i1	2516	F32BE	1
i2	2518	F32BE	1
i3	2520	F32BE	1
iavg	2528	F32BE	1
active_power_l1	2530	F32BE	1
active_power_l2	2532	F32BE	1
active_power_l3	2534	F32BE	1
reactive_power_l1	2538	F32BE	1
reactive_power_l2	2540	F32BE	1
reactive_power_l3	2542	F32BE	1
apparent_power_l1	2546	F32BE	1
apparent_power_l2	2548	F32BE	1
apparent_power_l3	2550	F32BE	1
power_factor_l1	2554	F32BE	1
power_factor_l2	2556	F32BE	1
power_factor_l3	2558	F32BE	1
i1_thd	2588	F32BE	1
i2_thd	2590	F32BE	1
i3_thd	2592	F32BE	1
u1_thd	2594	F32BE	1
u2_thd	2596	F32BE	1
u3_thd	2598	F32BE	1
internal_temperature	2658	F32BE	1
energy_counter_n1	2752	F32BE	1
energy_counter_n2	2754	F32BE	1
energy_counter_n3	2756	F32BE	1
energy_counter_n4	2758	F32BE	1
energy_counter_1	2760	F32BE	1
energy_counter_2	2762	F32BE	1
energy_counter_3	2764	F32BE	1
energy_counter_4	2766	F32BE	1
energy_counter_5	2768	F32BE	1
energy_counter_6	2770	F32BE	1
energy_counter_7	2772	F32BE	1
energy_counter_8	2774	F32BE	1

link settings as documented (unverified): RTU/TCP; baud 1200/2400/4800/9600/19200/38400/57600/115200; FC 03,04,06,16; Supports Unicast and Broadcast modes. Modbus address 0 is reserved for broadcast.

bench facts as documented (unverified)

connector	RS485
broadcast	supported
model register	30001
serial register	30009
firmware register	30013

⚠ disputed: Framing ["RTU", "TCP"] — disputed by Finder 7M Series Datasheet; the physical meters only support RS485 (Modbus RTU) natively, requiring an external gateway (like Type 6M.BU) or OPTA PLC for Modbus TCP connectivity

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

Reading legacy registers (e.g., U1 at 30107) using standard 32-bit integer parsing yields incorrect values (e.g., 4278192.50 instead of ~237V) due to Finder's custom T5/T6 decade-exponent data format. [source]
Modbus RTU communication fails with timeouts unless the master is explicitly configured to use 2 stop bits (8N2) when parity is set to None, which is the meter's default behavior. [source]
confirmed: Baud rates [1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200] — confirmed by Finder 7M Series Datasheet
confirmed: Function codes [3, 4, 6, 16] — confirmed by Finder 7M Modbus Protocol Manual
confirmed: Identification registers (Model @ 30001, Serial @ 30009, Firmware @ 30013) — confirmed by Finder 7M User Manual
confirmed: Broadcast address 0 support — confirmed by Finder 7M User Manual
confirmed: Register map addresses (e.g., u1 @ 2500, i1 @ 2516, active_power_total @ 2490) — confirmed by evcc-io integration and Finder Modbus Enhanced documentation

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.
coherence-checked — Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.
hardware-verified (software-key) x1 — Matched a real device with operator-attested readings as ground truth — the only rung that confirms word order + scaling on the wire.

Device not here? Upload its manual and get a checked map back. It's free.

Want it confirmed against your own device? Order hardware verification. If it doesn't check out, you don't pay.

Building on a lot of devices? License the library — machine-readable maps, the firmware matrix, and API access.