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 only confirmed at the hardware-verified rung.
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 |
|---|---|---|---|---|
| phase_1_phase_voltage | 769 | U32BE | 0.001 | mV |
| phase_2_phase_voltage | 773 | U32BE | 0.001 | mV |
| phase_3_phase_voltage | 777 | U32BE | 0.001 | mV |
| phase_1_current | 781 | U32BE | 0.001 | mA |
| phase_2_current | 785 | U32BE | 0.001 | mA |
| phase_3_current | 789 | U32BE | 0.001 | mA |
| three_phase_active_power | 793 | U32BE | 1 | W or W/100 |
| three_phase_reactive_power | 797 | U32BE | 1 | var or var/100 |
| three_phase_apparent_power | 801 | U32BE | 1 | VA or VA/100 |
| three_phase_positive_active_energy | 805 | U32BE | 1 | Wh or kWh or MWh |
| chained_voltage_l1_l2 | 809 | U32BE | 0.001 | mV |
| chained_voltage_l2_l3 | 813 | U32BE | 0.001 | mV |
| chained_voltage_l3_l1 | 817 | U32BE | 0.001 | mV |
| three_phase_negative_active_energy | 821 | U32BE | 1 | Wh or kWh or MWh |
| frequency | 825 | U16 | 0.1 | Hz/10 |
| operating_timer_counter | 827 | U16 | 1 | h |
| three_phase_power_factor | 829 | I16 | 0.01 | 1/100 |
| three_phase_positive_reactive_energy | 835 | U32BE | 1 | varh or kvarh or Mvarh |
| three_phase_negative_reactive_energy | 840 | U32BE | 1 | varh or kvarh or Mvarh |
| three_phase_average_power | 848 | U32BE | 1 | W or W/100 |
| three_phase_peak_maximum_demand | 852 | U32BE | 1 | W or W/100 |
| neutral_current | 857 | U32BE | 0.001 | mA |
| phase_1_active_power | 861 | U32BE | 1 | W or W/100 |
| phase_2_active_power | 865 | U32BE | 1 | W or W/100 |
| phase_3_active_power | 869 | U32BE | 1 | W or W/100 |
| phase_1_reactive_power | 876 | U32BE | 1 | var or var/100 |
| phase_2_reactive_power | 880 | U32BE | 1 | var or var/100 |
| phase_3_reactive_power | 884 | U32BE | 1 | var or var/100 |
| phase_1_apparent_power | 891 | U32BE | 1 | VA or VA/100 |
| phase_2_apparent_power | 895 | U32BE | 1 | VA or VA/100 |
| phase_3_apparent_power | 899 | U32BE | 1 | VA or VA/100 |
| phase_1_power_factor | 903 | I16 | 0.01 | 1/100 |
| phase_2_power_factor | 905 | I16 | 0.01 | 1/100 |
| phase_3_power_factor | 907 | I16 | 0.01 | 1/100 |
| phase_1_thd_v1 | 912 | U16 | 1 | % |
| phase_2_thd_v2 | 914 | U16 | 1 | % |
| phase_3_thd_v3 | 916 | U16 | 1 | % |
| phase_1_thd_i1 | 918 | U16 | 1 | % |
| phase_2_thd_i2 | 920 | U16 | 1 | % |
| phase_3_thd_i3 | 922 | U16 | 1 | % |
| phase_1_i1_average | 924 | U32BE | 0.001 | mA |
| phase_2_i2_average | 928 | U32BE | 0.001 | mA |
| phase_3_i3_average | 932 | U32BE | 0.001 | mA |
| phase_1_i1_peak_maximum | 936 | U32BE | 0.001 | mA |
| phase_2_i2_peak_maximum | 940 | U32BE | 0.001 | mA |
| phase_3_i3_peak_maximum | 944 | U32BE | 0.001 | mA |
| average_current_i1_i2_i3_3 | 948 | U32BE | 0.001 | mA |
| phase_1_v1_min | 952 | U32BE | 0.001 | mV |
| phase_2_v2_min | 956 | U32BE | 0.001 | mV |
| phase_3_v3_min | 960 | U32BE | 0.001 | mV |
| phase_1_v1_max | 964 | U32BE | 0.001 | mV |
| phase_2_v2_max | 968 | U32BE | 0.001 | mV |
| phase_3_v3_max | 972 | U32BE | 0.001 | mV |
| temperature_first_channel | 1016 | U32BE | 0.01 | |
| temperature_second_channel | 1020 | U32BE | 0.01 |
| terminals | 2-wire |
| wiring notes | EIA-RS485 standard in half-duplex modality. Only 32 instruments can be attached on the same physical line (master included). |
| max registers/read | 120 |
| broadcast | supported |
| protocol notes | Variables or groups of variables may be required up to 100 BYTES (sw. version < 1.09) or up to 240 BYTES (sw. version >= 1.09). |
| identification notes | Device identifier register at 0x300 (value 0x10) or 0x1204 (value 0x10). |
| doc revision | B |
| firmware applicability | 3.18 |
Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.
Have a device that isn't here? Upload its register map — generation is free, and the connector earns its rung by being proven, not claimed.
Need it proven on your own device? Hardware verification — if it doesn't verify, you don't pay.
Building a platform? License the verified library — machine-readable maps, firmware matrix, API access.