Variable frequency drive

ABB ACS580Manual, data sheet and how to read its data

Two things on one page: where the official manufacturer documentation lives and, below, the integration sheet (where data comes out of this unit and which protocol it speaks), which the manual never sums up anywhere.

Official manufacturer documentation

We do not host third-party manuals: the right version is always the manufacturer's, who also updates the PDFs when the firmware changes. This link takes you to the ABB ACS580 document catalog.

This is the standard control program manual: start-up, macros, parameters, fault codes and both fieldbus chapters. Mounting and power wiring are in the hardware manual for your build (ACS580-01, -04 or -07).

ACS580 firmware manual · ABB PDF ACS580-01 hardware manual

Where the data comes out

Built-in Modbus RTU
EIA-485 bus on connector X5 of the control unit, no extra card. It has termination and bias switches: termination at both ends of the bus and bias on one device only.
Response rate
The control program handles 10 Modbus registers per 10 ms cycle: a 20-register read starts answering in about 22 ms. Polling once a second leaves plenty of headroom.
Ethernet: Modbus TCP, EtherNet/IP and PROFINET
With the optional FENA-21 module in slot 1 of the control unit. For Modbus TCP there is also the FMBT-21.
Other fieldbuses
PROFIBUS DP (FPBA-01), CANopen (FCAN-01), DeviceNet (FDNA-01), EtherCAT (FECA-01), ControlNet (FCNA-01) and Ethernet POWERLINK (FEPL-02), always as a module in the same slot.

Parameter numbers and register maps change between firmware versions, so those belong in the manufacturer manual, not in this table. Always confirm the exact part number in your panel.

What you can read without rewiring the panel

The ACS580 ships with Modbus RTU: in most panels there is nothing to buy to start reading current, speed, torque, running hours and the active fault. If the drive already has an Ethernet module because the PLC controls it, it is read through that without touching the control.

  1. 1Identify the exact part number and firmware: within one family there are models with Ethernet and models with only a serial port.
  2. 2Write down the communication parameters already loaded (baud rate, parity, slave address). Changing them to experiment is what takes a production line down.
  3. 3Read in query mode, with the equipment running. iGromi only reads: it does not write to the device or change its parameters; if a value suggests an adjustment, a person decides.
  4. 4Store each value with its timestamp and context (shift, order, operator). A bare number will not tell you later why the machine stopped.

When the unit is not alone

Reading one ACS580 is a short job. The problem starts when the plant has fifteen units from six brands, each with its own protocol and wiring. The iGromi Bridge speaks Modbus RTU and TCP, OPC UA, BACnet, CANopen and MQTT on the same node, and when a unit's parameters are unknown it finds them by trying combinations until it communicates. Always read-only.

Talk to an engineer
Start without hardware

Safe industrial AI, starting free from the app.

The app gathers what your team knows: each trade with its helpers, and @igromi answers citing the source. AI reads, proposes and cites; a person decides. When you add systems and equipment, the Edge reads PLCs in read-only mode.

  • AssetsPLCs, sensors, cameras, GPS
  • SystemsSAP, ERP, MES, SCADA, spreadsheets
  • PeopleOperators and managers: judgment and fixes

No credit card. Your data stays yours.