Veris Enercept H8035/H8036 power 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	unit
Energy Consumption, LSW	0	U16	1	kWh
Energy Consumption, MSW	1	U16	1	kWh
Demand (power)	2	U16	1	kW
Reactive Power	3	U16	1	VAR
Apparent Power	4	U16	1	VA
Power Factor	5	U16	1
Voltage, line to line	6	U16	1	V
Voltage, line to neutral	7	U16	1	V
Current	8	U16	1	A
Demand (power), phase A	9	U16	1	kW
Demand (power), phase B	10	U16	1	kW
Demand (power), phase C	11	U16	1	kW
Power Factor, phase A	12	U16	1
Power Factor, phase B	13	U16	1
Power Factor, phase C	14	U16	1
Voltage, phase A-B	15	U16	1	V
Voltage, phase B-C	16	U16	1	V
Voltage, phase A-C	17	U16	1	V
Voltage, phase A-N	18	U16	1	V
Voltage, phase B-N	19	U16	1	V
Voltage, phase C-N	20	U16	1	V
Current, phase A	21	U16	1	A
Current, phase B	22	U16	1	A
Current, phase C	23	U16	1	A
Average Demand	24	U16	1	kW
Minimum Demand	25	U16	1	kW
Maximum Demand	26	U16	1	kW
Energy Consumption	256	F32BE	1	kWh
Energy Consumption (same 40257)	258	F32BE	1	kWh
Demand (power)	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 (power), phase A	274	F32BE	1	kW
Demand (power), phase B	276	F32BE	1	kW
Demand (power), 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.
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.