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.
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 |
|---|---|---|---|---|
| max_voltage_l_l_avg | 2308 | F32BE | 1 | V |
| starting_current | 998 | U16 | 1 | |
| number_of_control_power_failures | 1827 | U16 | 1 | kW |
| energy_led_mode | 2124 | U16 | 1 | kWh |
| nominal_frequency | 2015 | U16 | 1 | Hz |
| pf_standard | 999 | U16 | 1 | |
| demand_method | 1005 | U16 | 1 | kW |
| revenue_security_status | 1919 | U16 | 1 | |
| supported_features | 93 | U16 | 1 | |
| pf_lock | 1001 | U16 | 1 |
Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.
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.