eTactica Power Meter EM

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
cpu_temperature_common	8206	I16	0.01	0.01°C
frequency	8207	U16	0.001	mHz
current_phase_1	8208	U32BE	0.001	mA
current_phase_2	8210	U32BE	0.001	mA
current_phase_3	8212	U32BE	0.001	mA
voltage_phase_1	8214	U32BE	0.001	mV
voltage_phase_2	8216	U32BE	0.001	mV
voltage_phase_3	8218	U32BE	0.001	mV
power_factor_phase_1	8222	I16	0.01
power_factor_phase_2	8223	I16	0.01
power_factor_phase_3	8224	I16	0.01
status	8225	U16	1
nominal_full_scale_amperage	8226	U16	1	A
cpu_temperature_em2	8448	I16	0.01	0.01°C
rms_voltage_phase_1_1s	8457	U32BE	0.001	mV
rms_voltage_phase_2_1s	8459	U32BE	0.001	mV
rms_voltage_phase_3_1s	8461	U32BE	0.001	mV
rms_current_phase_1_1s	8463	U32BE	0.001	mA
rms_current_phase_2_1s	8465	U32BE	0.001	mA
rms_current_phase_3_1s	8467	U32BE	0.001	mA
power_factor_phase_1_1s	8469	I16	0.0001
power_factor_phase_2_1s	8470	I16	0.0001
power_factor_phase_3_1s	8471	I16	0.0001
frequency_em2	8472	U16	0.001	mHz
rms_voltage_phase_1_60s	8521	U32BE	0.001	mV
rms_voltage_phase_2_60s	8523	U32BE	0.001	mV
rms_voltage_phase_3_60s	8525	U32BE	0.001	mV
rms_current_phase_1_60s	8527	U32BE	0.001	mA
rms_current_phase_2_60s	8529	U32BE	0.001	mA
rms_current_phase_3_60s	8531	U32BE	0.001	mA
power_factor_phase_1_60s	8533	I16	0.0001
power_factor_phase_2_60s	8534	I16	0.0001
power_factor_phase_3_60s	8535	I16	0.0001
rms_voltage_phase_1_last_cycle	8536	U32BE	0.001	mV
rms_voltage_phase_2_last_cycle	8538	U32BE	0.001	mV
rms_voltage_phase_3_last_cycle	8540	U32BE	0.001	mV
rms_current_phase_1_last_cycle	8542	U32BE	0.001	mA
rms_current_phase_2_last_cycle	8544	U32BE	0.001	mA
rms_current_phase_3_last_cycle	8546	U32BE	0.001	mA
power_factor_phase_1_latest	8548	I16	0.0001
power_factor_phase_2_latest	8549	I16	0.0001
power_factor_phase_3_latest	8550	I16	0.0001
sign_power_factor_phase_1	8551	I16	1
sign_power_factor_phase_2	8552	I16	1
sign_power_factor_phase_3	8553	I16	1

link settings as documented (unverified): RTU; default 19200 8E1; FC 03,16; RS485 half-duplex. Default settings: 19200 baud, 8 data bits, Even parity, 1 stop bit. Configurable in firmware 3.2 or higher.

bench facts as documented (unverified)

terminals	RS485 half-duplex
wiring notes	EM-SC uses split-core current sensors, EM-FC uses flexible-coil current sensors
response timeout	4 ms
protocol notes	Typically, the device will respond in 3-4 milliseconds. There is no limit on back to back requests.
model register	0x2001
serial register	0x2003
firmware register	0x2002
doc revision	2.1
firmware applicability	EM2 extended registers require firmware version 4.0 or greater. Serial settings configurable in firmware 3.2 or higher.

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

confirmed: Default serial settings: 19200 baud, 8 data bits, Even parity, 1 stop bit — confirmed by eTactica EM-SC/FC Modbus Register Map document [1.1.1] and product data sheet
confirmed: Baud rates supported: 600 to 115200 — confirmed by eTactica EM-SC/FC Modbus Register Map document (register 0x2008)
confirmed: EM-SC uses split-core current sensors, EM-FC uses flexible-coil current sensors — confirmed by eTactica PowerSync Network Product Data Sheet
confirmed: EM2 extended registers require firmware version 4.0 or greater — confirmed by eTactica EM-SC/FC Modbus Register Map document
confirmed: Typically, the device will respond in 3-4 milliseconds — confirmed by eTactica EM-SC/FC Modbus Register Map document
confirmed: Register addresses (e.g., cpu_temperature_common @ 8206, frequency @ 8207, current_phase_1 @ 8208, etc.) — confirmed by eTactica EM-SC/FC Modbus Register Map document

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.