Veris Enercept H8035/H8036 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	unit
energy_consumption	256	F32BE	1	kWh
energy_consumption_dup	258	F32BE	1	kWh
demand	260	F32BE	1	kW
reactive_power	262	F32BE	1	VAR
apparent_power	264	F32BE	1	VA
power_factor	266	F32BE	1
voltage_line_to_line	268	F32BE	1	V
voltage_line_to_neutral	270	F32BE	1	V
current	272	F32BE	1	A
demand_phase_a	274	F32BE	1	kW
demand_phase_b	276	F32BE	1	kW
demand_phase_c	278	F32BE	1	kW
power_factor_phase_a	280	F32BE	1
power_factor_phase_b	282	F32BE	1
power_factor_phase_c	284	F32BE	1
voltage_phase_a_b	286	F32BE	1	V
voltage_phase_b_c	288	F32BE	1	V
voltage_phase_a_c	290	F32BE	1	V
voltage_phase_a_n	292	F32BE	1	V
voltage_phase_b_n	294	F32BE	1	V
voltage_phase_c_n	296	F32BE	1	V
current_phase_a	298	F32BE	1	A
current_phase_b	300	F32BE	1	A
current_phase_c	302	F32BE	1	A
average_demand	304	F32BE	1	kW
minimum_demand	306	F32BE	1	kW
maximum_demand	308	F32BE	1	kW

link settings as documented (unverified): RTU; default 9600 8N1; FC 03,06,17; The power meter operates as a slave device. It expects a Modbus master device to transmit queries, which it will answer.

bench facts as documented (unverified)

response timeout	40 ms
inter-frame delay	2 ms
protocol notes	The E/node meter will typically respond to a query within 12 ms to 18 ms. All responses will be generated within 40 ms. If the master device sends a query with more than approx 2 characters silent time between any of the bytes, it will not be properly recognized. Variables are internally updated every 200 ms. There is no timeout of how long the previously requested float value will be retained in the buffer.
identification notes	Function 17 (Report Slave ID) will return data which identifies the power meter.
FC 43 device ID	not supported

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

The H8035/H8036 only supports Modbus Function Code 6 (Preset Single Register) for writing, which causes write failures on PLCs or master devices that default to Function Code 16 (Preset Multiple Registers) for writing blocks of data. Users must implement custom sequencing logic to write registers individually. [source]
There is no timeout for how long a previously requested floating-point value is retained in the buffer. To avoid re-reading buffered/stale values, the master must request a different floating-point value before requesting the first one again. [source]
confirmed: Baud rate of 9600, No Parity, 1 Stop Bit (8N1 format) — confirmed by Veris H8035 & H8036 Series Datasheet [7.1.2]
confirmed: Supported Modbus RTU function codes are 3 (Read Holding Registers), 6 (Preset Single Register), and 17 (Report Slave ID) — confirmed by Veris H8035/8036 Modbus Point Map
confirmed: Floating-point register map starting at offset 256 (Modbus address 40257) — confirmed by Veris H8035/8036 Modbus Point Map
confirmed: Response time typically 12 ms to 18 ms, with all responses generated within 40 ms — confirmed by PowerLogic Enercept Modbus Specification
confirmed: Inter-character silent time limit of approximately 2 characters — confirmed by PowerLogic Enercept Modbus Specification

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.