ABB ACS580 Communication Compatibility

Compatibility Overview

The ABB ACS580 is an all-compatible general-purpose variable frequency drive (VFD) designed for a broad range of industrial applications. To maintain seamless integration within automated environments, the ACS580 supports various industrial ethernet, fieldbus, and serial protocols. The system architecture utilizes the drive's embedded fieldbus (EFB) interface or modular F-series fieldbus adapters inserted directly into the drive’s control unit interface slot (typically Slot 1).

By default, the ACS580 features an embedded EIA-485 Modbus RTU interface. For advanced networks like PROFINET, EtherNet/IP, or EtherCAT, external fieldbus adapters must be installed. Compatibility depends on the drive frame size, control unit firmware (ASDK2/ASDK4), and adapter module execution series. Establishing stable cyclic data exchange (I/O communication) and acyclic messaging requires precise coordination between the network master (PLC/DCS) and the option module configurations.

Supported Models

The modular structure of the ACS580 series ensures wide communication compatibility across the standard product range. The drive's logic and communication parameters are handled by the CCU-24 (standard on wall-mounted models) or the CCU-23 control unit.

The ASDK2 firmware branch natively recognizes the parameter indexing structures of modernized F-series adapters, ensuring automatic hardware detection upon insertion.

Unsupported Models

While most models allow full modular network expansion, specific hardware limitations, power classes, and safety module configurations can restrict communication options:

1. Legacy R-Series Adapters: The ACS580 is physically and logically incompatible with older legacy R-series fieldbus adapters (e.g., RPBA-01, RETA-02) used with the ACS800 series. Standardizing on F-series adapters is mandatory.
2. Mechanical Interference in Special Frame Sizes: Certain custom-built ACS580-07 cabinets utilizing specific side-mounted option brackets may physically block the mounting or access path of oversized standard fieldbus connection plugs unless right-angle connectors are selected.
3. Functional Safety Conflict (Slot Constraints): If a functional safety module (like standard FSO-12 or FSO-21 modules) is occupied in option allocation spaces, ensure that the communication adapter is properly paired in designated slots. If the physical layout restricts slot availability, communication adapters must be evaluated. In standard ACS580 packages, Slot 1 is reserved exclusively for the fieldbus module, meaning safety interfaces must not conflict with primary physical layout rules.

Communication Options

To bridge the ACS580 to modern control networks, various F-series option modules are available. These modules convert the drive’s internal native communication interface into standard industrial protocol structures.

Each adapter utilizes specific device description configuration files (GSDML for PROFINET, EDS for EtherNet/IP, GSD for PROFIBUS, and XML/ESI for EtherCAT) to simplify drive mapping in configuration engines like Siemens TIA Portal or Rockwell Automation Studio 5000.

Integration Notes

Successful integration of an ACS580 drive into a controller network hinges on precise configuration of control and status parameters. The primary drive parameters that govern communication include:

• Parameter Group 50 (Fieldbus Adapter (FBA)): Configures basic FBA communications, including adapter enabling (Parameter 50.01 set to "Option slot 1") and raw diagnostics.
• Parameter Group 51 (FBA A Settings): Configures card-specific network parameters such as IP address, subnet mask, gateway, or station address, depending on the active fieldbus card.
• Parameter Group 52 (FBA A Data In) & Group 53 (FBA A Data Out): Sets the cyclic parameters mapped between the master and drive. Typical mappings include:
  • Word 1: Control Word (from PLC) / Status Word (to PLC)
  • Word 2: Reference Speed (from PLC) / Actual Speed (to PLC)
  • Word 3 to 12: Customizable variables such as Output Current, Torque, Motor Temperature, or Fault Codes.

PLC Configuration Protocol Example (EtherNet/IP / FENA-21)

When integrating via EtherNet/IP with a Rockwell Automation GuardLogix or ControlLogix processor, the connection must be configured in Studio 5000 as a Generic Ethernet Module or utilizing the native ACS580 Add-on Profile (AOP).

• Input Assembly Instance: 101 (Standard ABB Drive Profile - 4 words) or 71 (ODVA AC/DC Profile - 2 words)
• Output Assembly Instance: 100 (Standard ABB Drive Profile - 4 words) or 70 (ODVA AC/DC Profile - 2 words)
• Configuration Assembly Instance: 1

Common Compatibility Issues

Integrating variable speed drives on industrial buses can occasionally run into communication dropouts or parsing errors due to network configuration oversights:

• FBA Communication Loss (Fault 7510 / Warning A7C1): Occurs if the drive loses connection to the master controller. Verify Parameter 50.02 (FBA A comm loss func) settings. Setting this to standard "Fault" safely stops the motor, while "Last speed" or "Safe speed" provides system fallback options. Check cable shielding and termination resistors (120 Ohm for RS-485 / Profibus segments).
• Control Word Format Mismatch: A classic symptom is when a drive reports an "Online" status on the PLC bus but refuses to run. This or a zero-speed state occurs if the Control Word profile standard selected in the PLC (e.g., ODVA AC/DC) conflicts with the configuration on Parameter 50.04 (FBA A ref1 type) or Parameter 19.11 (Ext1/Ext2 control mode).
• Duplicated IP Addresses and Subnet Mismatches: When inserting FENA-21 or FEIP-21 modules, ensure static IP configurations via Parameter Group 51 match the network topology. Always cycle drive auxiliary power (or perform FBA reset via Parameter 51.27) to apply configuration changes.
• MRP / DLR Ring Network Instability: Daisy-chaining dual-port adapters can cause temporary control loops if the managing switch has Media Redundancy Protocol (PROFINET) or Device Level Ring (EtherNet/IP) disabled or misconfigured. Ensure correct loop-prevision software runs on the local infrastructure managed by switches.

FAQ

Q: Can I run standard Modbus RTU via the embedded terminals while simultaneously running PROFINET on an FENA-21 module?

Yes. The ACS580 can process control signals from both fields. However, control source priority must be configured. Under Parameter Group 19 (Operation Mode) and Group 20 (Start/Stop/Direction), you must specify which input source (Embedded Fieldbus or FBA A) controls the drive state machine and speed references. Only one source can control the active speed reference (Ext1 or Ext2) simultaneously.

Q: What is the maximum physical network distance supported by the FSCA-01 Modbus RTU module?

For RS-485 lines using the FSCA-01 or the built-in EIA-485 port, the maximum total network segment length is 1200 meters (3900 feet) when running at 19.2 kbps or lower. This requires high-quality Category 5e (or better) STP cables with appropriate end-of-line active termination switches engaged on the final physical nodes of the bus.

Q: Does the ACS580 support EtherCAT, and which specific file is needed for PLC integration?

Yes, the ACS580 supports EtherCAT protocol via the FECA-01 adapter. To integrate it into systems like Beckhoff TwinCAT or Omron Sysmac Studio, you must download and import the specific XML Device Description File (.xml or .esi format) corresponding to the ACS580 and FECA-01 system configurations from the official ABB documentation library.

Q: What is the purpose of Parameter 51.27 (FBA A par refresh) during setup?

Parameter 51.27 is a configuration command used to force the drive's CCU control unit to read any new or altered parameter settings stored on the attached fieldbus adapter. Without initiating a parameter refresh (setting Parameter 51.27 to "Configure"), changes saved in Group 51 or Group 52 will not take effect until the drive’s control board is completely power-cycled.

Q: Can I use CC-Link communication profiles with the ACS580 drive design?

Yes, CC-Link networks are supported by integrating the FBCG-02 CANopen/CC-Link gateway or dedicated fieldbus adapter options designed for standard industrial automation topologies. Make sure to download the corresponding profile map to map the Drive Control Word and register arrays correctly into your CC-Link master configuration.