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 |
|---|---|---|---|---|
| output_frequency | 400 | I16 | 0.01 | |
| output_voltage | 401 | U16 | 1 | |
| output_power | 402 | I16 | 0.01 | |
| motor_rpm | 403 | I16 | 0.1 | |
| dc_bus_voltage | 404 | U16 | 1 | |
| current_magnitude | 300 | U16 | 0.01 | |
| torque_producing_current | 301 | I16 | 0.01 | |
| analog_input_1 | 600 | I16 | 0.01 | |
| analog_input_2 | 601 | I16 | 0.01 | |
| drive_ok | 900 | U16 | 1 | |
| drive_active | 901 | U16 | 1 | |
| status_word | 939 | U16 | 1 | |
| active_trip | 919 | U16 | 1 | |
| motor_rated_current | 406 | U16 | 0.01 | |
| motor_rated_speed | 407 | U16 | 0.1 | |
| motor_rated_voltage | 408 | U16 | 1 | |
| motor_rated_power_factor | 409 | U16 | 0.01 | |
| motor_rated_frequency | 405 | U16 | 0.01 |
⚠ The STOP and Safe Torque Off functions of the drive do not isolate dangerous voltages from the output of the drive or from any external option unit. — Starkest reads only; we never write a control register.
| terminals | RJ45 or screw terminals |
| A/B polarity | |
| termination | 120 Ohm termination resistor available on RJ45 pin 1 or screw terminal pin 4 |
| connector | RJ45 or screw terminal block |
| isolation | Single insulated, meets ELV requirements |
| shield/ground | Minimum number of connections are 2, 3, 7 and shield |
| wiring notes | Standard Ethernet cables must not be used when connecting drives on a EIA 485 network as they do not have the correct twisted pairs for the pinout of the serial comms port. |
| inter-frame delay | 20 ms |
| broadcast | supported |
| sentinel values | |
| protocol notes | The Modbus slave device increments the register address by 1 before processing the command, which effectively prevents access to parameter Pr 00.000 in the drive or option module. |
| model register | 11.028 |
| serial register | 11.052 |
| firmware register | 11.029 |
| identification notes | Serial number is split into LS (11.052) and MS (11.053). |
| FC 43 device ID | not supported |
| power | 24 Vdc backup supply input on AI-Backup adaptor |
| environment | Pollution Degree 2 environment or better (dry, non-conductive pollution only). Ambient temperature up to 40 °C (up to 55 °C with derating) |
| accuracy | |
| certifications | CE, C Tick, UL / cUL, RoHS, Functional safety, EurAsian Conformity |
| doc revision | Issue: 2 |
| firmware applicability |
⚠ disputed: output_frequency @ 400, output_voltage @ 401, output_power @ 402, motor_rpm @ 403, dc_bus_voltage @ 404, current_magnitude @ 300, torque_producing_current @ 301, analog_input_1 @ 600, analog_input_2 @ 601, drive_ok @ 900, drive_active @ 901, status_word @ 939, active_trip @ 919, motor_rated_current @ 406, motor_rated_speed @ 407, motor_rated_voltage @ 408, motor_rated_power_factor @ 409, motor_rated_frequency @ 405 — disputed by Commander C200/C300 Control User Guide and Parameter Reference Guide. The standard Modbus address formula is (Menu * 100) + Parameter - 1. Therefore, Menu 5 parameters (like output_frequency Pr 05.001) map to 500, not 400. Menu 4 parameters (like current_magnitude Pr 04.001) map to 400, not 300. Menu 7 parameters (like analog_input_1 Pr 07.001) map to 700, not 600. Menu 10 parameters (like drive_ok Pr 10.001) map to 1000, not 900. The entire register map is shifted down by exactly 100 registers.
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.