ABB ACS880 drive (primary control)

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.

coherence-checked

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
motor_speed_percent	102	I16	0.1
motor_current_percent	107	I16	1
dc_voltage	110	I16	0.1
output_voltage	112	I16	1
output_power_percent	114	I16	0.1
motor_shaft_power	116	I16	1
inverter_gwh_motoring	117	U16	1
inverter_mwh_motoring	118	U16	1
inverter_kwh_motoring	119	U16	0.1
flux_actual_percent	123	I16	1
speed_change_rate	128	I16	1
nominal_torque_scale	129	U16	1
ambient_temperature	130	I16	1
inverter_kwh_regenerating	133	U16	0.1
mot_regen_energy_gwh	134	I16	1
mot_regen_energy_mwh	135	I16	1
mot_regen_energy_kwh	136	I16	0.1
abs_motor_speed_percent	161	U16	0.1
abs_motor_torque	163	U16	0.1
abs_output_power_percent	165	U16	0.1
ambient_temperature_percent	169	I16	0.1
inverter_temperature	510	I16	1
ai1_actual_value	1210	I16	0.001
ai2_actual_value	1220	I16	0.001
ao1_actual_value	1310	I16	0.001
ao2_actual_value	1320	I16	0.001

link settings as documented (unverified): RTU; default 19200 8E1; unit ID 1; FC 01,02,03,05,06,08,11,15,16,22,23; Embedded fieldbus interface supports Modbus RTU protocol.

bench facts as documented (unverified)

terminals	XD2D
A/B polarity	A, B
termination	Termination ON/OFF switch on XD2D connector
connector	XD2D (RS-485) connector
shield/ground	Shield terminal on XD2D
wiring notes	Connect the fieldbus to terminal XD2D on the control unit of the drive.
protocol notes	The drive control program can handle 10 Modbus registers in a 10-millisecond time level. For example, if the drive receives a request to read 20 registers, it will start its response within 22 ms of receiving the request – 20 ms for processing the request and 2 ms overhead for handling the bus.
identification notes	Supported Object IDs: 00h: Vendor Name ('ABB'), 01h: Product Code, 02h: Major Minor Revision, 03h: Vendor URL, 04h: Product name ('ACS880')
FC 43 device ID	supported
doc revision	3AUA0000085967 Rev V EN, EFFECTIVE: 2020-08-21
firmware applicability	ACS880 primary control program

⚠ disputed: Baud rates list [9600, 19200, 38400, 57600, 76800, 115200] — disputed by the ACS880 firmware manual which also supports 4800 bps (4.8 kbps) under parameter 58.04

⚠ disputed: Quirks performance note regarding handling 10 Modbus registers in a 10-millisecond time level with 22 ms response time — disputed by the ACS880 firmware manual (3AUA0000085967) which does not contain this performance note; it is actually from the ACH580, ACS580, ACS380, ACQ580, and ACS480 manuals

field reports — community-sourced, unverified (checked 2026-06-11)

RS-485 wiring polarity surprise: ABB defines A as (-) and B as (+), which is opposite to some other manufacturers' conventions, often requiring swapping the A and B lines to establish communication. [source]
Off-by-one register addressing issues: Integrators frequently report offset issues (+1 or -1) when mapping registers because some Modbus masters/HMIs use 0-based addressing while others use 1-based addressing. [source]
confirmed: Document revision '3AUA0000085967 Rev V EN, EFFECTIVE: 2020-08-21' — confirmed by ABB Library and manual listings [9.2.1]
confirmed: Default baud rate of 19200, default unit ID of 1, RTU framing, Even parity, and 1 stop bit — confirmed by the ACS880 primary control program firmware manual (Section: Setting up the embedded fieldbus interface)
confirmed: Physical connector XD2D (RS-485) on the control unit with polarity A, B, shield ground on pin 4, and termination switch/jumper J3 — confirmed by the ACS880 hardware manuals
confirmed: FC43 Read Device Identification support with Object IDs 00h to 04h — confirmed by the ACS880 firmware manual
confirmed: Register map summary mapping parameters to 0-based offsets (e.g., motor_speed_percent @ 102, motor_current_percent @ 107, dc_voltage @ 110) — confirmed by the standard 100 * Group + Index mapping in the ACS880 firmware manual

The trust ladder

Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.

generated — A prompt produced it. Unproven — anyone can regenerate this.
structure-verified — Decode path is structurally sound (addresses, widths, finite values). Does NOT prove word order or scaling.
coherence-checked — 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.
hardware-verified (software-key) x1 — Matched a real device with operator-attested readings as ground truth — the only rung that confirms word order + scaling on the wire.

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.