EIG Shark 100 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
watts_3ph_total_6_cycles	899	F32BE	1	W
vars_3ph_total_6_cycles	901	F32BE	1	VAR
vas_3ph_total_6_cycles	903	F32BE	1	VA
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	V
volts_b_c	1007	F32BE	1	V
volts_c_a	1009	F32BE	1	V
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
frequency	1025	F32BE	1	Hz
neutral_current	1027	F32BE	1	A
w_hours_received	1099	U32BE	1	Wh
w_hours_delivered	1101	U32BE	1	Wh
w_hours_net	1103	U32BE	1	Wh
w_hours_total	1105	U32BE	1	Wh
var_hours_positive	1107	U32BE	1	VARh
var_hours_negative	1109	U32BE	1	VARh
var_hours_net	1111	U32BE	1	VARh
var_hours_total	1113	U32BE	1	VARh
va_hours_total	1115	U32BE	1	VAh

link settings as documented (unverified): RTU/ASCII; default 9600 8N?; unit ID 1; Com 1 is an Optical IrDA Port communicating via Modbus ASCII only. Com 2 is RS-485 supporting Modbus RTU, Modbus ASCII, and DNP 3.0.

⚠ Do not use the meter or any I/O Output Device for primary protection or in an energy-limiting capacity. — Starkest reads only; we never write a control register.

bench facts as documented (unverified)

terminals	Screw terminal, Nickel-Plated Brass Studs (Current Gills) with screws, Quick Connect 0.25" Male Tab
A/B polarity	connect + to + and - to -
termination	meter has some level of termination internally, Termination Resistors may not be needed
connector	RS-485 connector is located on the terminal section
isolation	All Inputs and Outputs are galvanically isolated to 2500 Vac
shield/ground	grounding the shield at one end only
response timeout	750 ms
model register	16
serial register	8
firmware register	17
power	D2 Option: Universal, (90 to 265) VAC @50/60Hz or (100 to 370) VDC; D Option: (18-60) VDC; Power Consumption: 5 VA, 3.5W
environment	Storage: (-40 to +85) C, Operating: (-30 to +70) C, Humidity: to 95% RH Non-condensing, Faceplate Rating: NEMA12
accuracy	0.2% Class Revenue Certifiable Energy and Demand Metering. Meets ANSI C12.20 (0.2%) and IEC 687 (0.2%) Classes
certifications	IEC 687, ANSI C12.20, ANSI (IEEE) C37.90.1, ANSI C62.41, IEC1000-4-2, IEC1000-4-3, IEC1000-4-4, IEC1000-4-5
doc revision	1.13

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

Floating-point values (such as Amps A at 1011/1012) are represented in IEEE 754 32-bit float format with the lower-addressed register containing the high-order half (exponent), which often requires word-swapping depending on the Modbus master's default endianness. [source]
confirmed: comms defaults (baud rates [9600, 19200, 38400, 57600], default baud 9600, default unit ID 1, parity N) — confirmed by Shark 100 User Manual and brochures
confirmed: Com 1 is an Optical IrDA Port communicating via Modbus ASCII only. Com 2 is RS-485 supporting Modbus RTU, Modbus ASCII, and DNP 3.0 — confirmed by Shark 100 User Manual
confirmed: accuracy: 0.2% Class Revenue Certifiable Energy and Demand Metering. Meets ANSI C12.20 (0.2%) and IEC 687 (0.2%) Classes — confirmed by Shark 100 Brochure
confirmed: identification registers (firmware_register 17, model_register 16, serial_register 8) — confirmed by Shark 100 Modbus Map where 0-based addresses 17, 16, and 8 correspond to 1-based registers 18 (Firmware Version), 17 (Meter Type), and 9 (Meter Serial Number)
confirmed: register map (watts_3ph_total_6_cycles @ 899, volts_a_n @ 999, w_hours_received @ 1099) — confirmed by Shark 100 Modbus Map where 0-based addresses 899, 999, and 1099 correspond to 1-based registers 900 (Watts, 3-Ph total 6-cycle), 1000 (Volts A-N), and 1100 (W-hours, Received)

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.