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.
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 |
|---|---|---|---|---|
| voltage_v1 | 0 | F32BE | 1 | |
| voltage_v2 | 2 | F32BE | 1 | |
| voltage_v3 | 4 | F32BE | 1 | |
| voltage_v12 | 6 | F32BE | 1 | |
| voltage_v23 | 8 | F32BE | 1 | |
| voltage_v31 | 10 | F32BE | 1 | |
| voltage_avg_ln | 12 | F32BE | 1 | |
| voltage_avg_ll | 14 | F32BE | 1 | |
| current_i1 | 16 | F32BE | 1 | |
| current_i2 | 18 | F32BE | 1 | |
| current_i3 | 20 | F32BE | 1 | |
| current_avg | 22 | F32BE | 1 | |
| active_power_p1 | 24 | F32BE | 1 | |
| active_power_p2 | 26 | F32BE | 1 | |
| active_power_p3 | 28 | F32BE | 1 | |
| active_power_total | 30 | F32BE | 1 | |
| reactive_power_q1 | 32 | F32BE | 1 | |
| reactive_power_q2 | 34 | F32BE | 1 | |
| reactive_power_q3 | 36 | F32BE | 1 | |
| reactive_power_total | 38 | F32BE | 1 | |
| apparent_power_s1 | 40 | F32BE | 1 | |
| apparent_power_s2 | 42 | F32BE | 1 | |
| apparent_power_s3 | 44 | F32BE | 1 | |
| apparent_power_total | 46 | F32BE | 1 | |
| power_factor_pf1 | 48 | F32BE | 1 | |
| power_factor_pf2 | 50 | F32BE | 1 | |
| power_factor_pf3 | 52 | F32BE | 1 | |
| power_factor_avg | 54 | F32BE | 1 | |
| frequency | 56 | F32BE | 1 | |
| active_energy | 58 | F32BE | 1 | |
| reactive_energy | 60 | F32BE | 1 | |
| apparent_energy | 62 | F32BE | 1 |
| terminals | Screw terminals with protection covering |
| A/B polarity | RS485 + and - |
| termination | Suggested terminating resistor (120 ohm, 1/4 watt) |
| shield/ground | Shielded cable |
| wiring notes | Transmission distance 500 m maximum |
| response timeout | 100 ms |
| protocol notes | Response time is 100 ms independent of baud rate |
| power | 85 to 270V AC/DC auxiliary supply, 50/60Hz, Power Consumption: 0.5 VA max. @ 5A per phase |
| environment | Operating temperature: 0 to +50°C, Storage temperature: -20 to +75°C, Humidity: 95% (non condensing) |
| accuracy | Voltage/Current: ±0.5% of Full scale, Frequency: ±0.1%, Active/Apparent/Reactive Power & Energy: Class 1 |
| doc revision | Operating / 1008 / MFM384 / Ver1A, OP278-V01A |
⚠ disputed: Power Consumption: 0.5 VA max. @ 5A per phase — disputed by Selec MFM384 official manuals which state that 0.5 VA @ 5A per phase is the CT input burden, whereas the actual auxiliary power consumption is less than 8VA (or less than 2VA for the 24V version) [1.2.7]
⚠ disputed: Operating temperature: 0 to +50°C, Humidity: 95% (non condensing) — disputed by Selec MFM384 official manuals which state operating temperature is -10°C to 55°C (or -5°C to 60°C) and humidity is up to 85% non-condensing
⚠ disputed: voltage_v12 @ 6 — disputed by Selec MFM384 official manuals which place Average Voltage LN at 30006 (0-based address 6) and Voltage V12 at 30008 (0-based address 8)
⚠ disputed: voltage_v23 @ 8 — disputed by Selec MFM384 official manuals which place Voltage V12 at 30008 (0-based address 8) and Voltage V23 at 30010 (0-based address 10)
⚠ disputed: voltage_v31 @ 10 — disputed by Selec MFM384 official manuals which place Voltage V23 at 30010 (0-based address 10) and Voltage V31 at 30012 (0-based address 12)
⚠ disputed: voltage_avg_ln @ 12 — disputed by Selec MFM384 official manuals which place Voltage V31 at 30012 (0-based address 12) and Average Voltage LN at 30006 (0-based address 6)
⚠ disputed: active_power_total @ 30 — disputed by Selec MFM384 official manuals which place kVA1 at 30030 (0-based address 30) and Total kW (active_power_total) at 30042 (0-based address 42)
⚠ disputed: reactive_power_q1 @ 32 — disputed by Selec MFM384 official manuals which place kVA2 at 30032 (0-based address 32) and Reactive Power Q1 (kVAr1) at 30036 (0-based address 36)
Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.
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.