verified connector library

Allen-Bradley PowerFlex 4/40/4M drive (DSI Modbus)

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.

interop-verified

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.

pointaddress (0-based)typescaleunit
logic_command8192U161
speed_reference8193U160.1Hz
logic_status8448U161
drive_error_codes8449U161
feedback8451U160.1Hz
output_freq1U160.1Hz
commanded_freq2U160.1
output_current3U160.01
output_voltage4U160.1
dc_bus_voltage5U161
drive_status6U161
fault_1_code7U161
fault_2_code8U161
fault_3_code9U161
control_source12U161
contrl_in_status13U161
dig_in_status14U161
comm_status15U161
elapsed_run_time18U1610
analog_in_0_10v20U160.1
analog_in_4_20ma21U160.1
drive_temp22U161

link settings as documented (unverified): RTU; default 9600 8N1; unit ID 100; FC 03,06,16; Power to drive must be cycled before any changes will affect drive operation. Supported formats include RTU 8-N-1, 8-E-1, 8-O-1, 8-N-2, 8-E-2, and 8-O-2.

⚠ Risk of equipment damage exists if writing parameter data to Non-Volatile Storage (NVS) frequently. NVS will quickly exceed its life cycle. — Starkest reads only; we never write a control register.

bench facts as documented (unverified)
terminalsControl Terminal 16, RJ45 DSI port pins 4 and 5
A/B polarityTxRxD+, TxRxD-
termination120 ohm resistor at each end of the network cable
connectorRJ45
isolationNetwork Common is internally tied to I/O Terminal 04 (Digital Common)
shield/groundThe shield should be grounded at ONLY ONE location.
wiring notesOnly pins 4 and 5 on the RJ45 plug should be wired.
protocol notesModbus devices can be 0-based or 1-based. Register addresses may need to be offset by +1 depending on the master.
identification notesTo access drive parameters, the Modbus register address equals the parameter number.
power120V AC 1-Phase, 240V AC 1-Phase, 240V AC 3-Phase, 480V AC 3-Phase
environmentAmbient Operating Temperature: -10°C to 40°C (0 mm clearance) or 50°C (25 mm clearance). Storage: -40°C to +85°C, 0% to 95% RH non-condensing.
certificationsUL, CE
doc revisionPublication 22F-UM001D-EN-E
firmware applicabilityFRN 1.xx - 2.xx
field reports — community-sourced, unverified (checked 2026-06-11)
  • Standard RJ45 Ethernet cables should not be plugged directly into the DSI port without isolating pins, as other pins (such as pins carrying power for HIM modules) can cause communication issues or hardware damage if connected to standard RS-485 transceivers. Only pins 4 and 5 should be wired for Modbus RTU. [source]
  • confirmed: comms.default_baud: 9600 — confirmed by PowerFlex 4M User Manual (Publication 22F-UM001E-EN-E) parameter C302 [Comm Data Rate] default
  • confirmed: comms.default_unit_id: 100 — confirmed by PowerFlex 4M User Manual parameter C303 [Comm Node Addr] default
  • confirmed: physical.connector: RJ45 — confirmed by manual and application notes describing the DSI port
  • confirmed: physical.notes: Only pins 4 and 5 on the RJ45 plug should be wired — confirmed by field guides and forum discussions identifying Pin 4 as TxRxD+ (Data+) and Pin 5 as TxRxD- (Data-)
  • confirmed: quirks.notes: Modbus devices can be 0-based or 1-based — confirmed by Rockwell Publication 2080-UM002H-EN-E noting that register addresses may need to be offset by +1 depending on the master

The trust ladder

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.