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 |
|---|---|---|---|---|
| inverter_reset | 1 | U16 | 1 | |
| parameter_clear | 2 | U16 | 1 | |
| all_parameter_clear | 3 | U16 | 1 | |
| inverter_status_control_extended | 7 | U16 | 1 | |
| inverter_status_control | 8 | U16 | 1 | |
| operation_mode_setting | 9 | U16 | 1 | |
| set_frequency_ram | 13 | U16 | 0.01 | Hz |
| set_frequency_eeprom | 14 | U16 | 0.01 | Hz |
| fault_record_1 | 500 | U16 | 1 |
⚠ Always set the communication check time interval before starting operation to prevent hazardous conditions. — Starkest reads only; we never write a control register.
| terminals | PU connector (RJ-45) |
| A/B polarity | RDA, RDB, SDA, SDB |
| termination | Connect a 100 Ohm 1/2 W terminating resistor between RDA (pin 3) and RDB (pin 6) |
| connector | RJ-45 |
| shield/ground | SG (pins 1 and 7) connected to terminal 5 |
| wiring notes | Pins 2 and 8 provide power to the operation panel or parameter unit. Do not use these pins for RS-485 communication. |
| max registers/read | 125 |
| response timeout | 50 ms |
| broadcast | supported |
| protocol notes | No response is returned in the case of broadcast communication. |
| model register | 44001 |
| identification notes | Model name can be read in ASCII code from registers 44001 to 44010. |
| power | Pins 2 and 8 of PU connector provide power to the operation panel or parameter unit. |
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.