Independent manufacturer reference

ABBProduct families & fault codes

A maintenance reference for ABB controllers, drives and robot controllers. Understand the product families, compare diagnostic methods, and look up documented ACS580-01 fault codes.

Last reviewed

ABB at a glance

Manufacturer
ABB
Relevant areas
Programmable controllers, variable-speed drives and robot controllers
Selected families
AC500, ACS580 and OmniCore
Engineering environments
Automation Builder, drive control panel and Drive Composer, FlexPendant, RobotWare and device-specific ABB documentation
Manufacturer website
abb.com ↗

Selected ABB product families

ABB AC500

Role
Modular programmable controller for machine and process automation.
Typical use
Machine logic, I/O, communications, process control and motion-related functions.
Diagnostic identifiers
Contextual CPU, module, application and communication messages rather than one universal family-wide fault list.
Important
Meaning depends on the exact CPU, I/O modules, project, safety configuration and firmware.

ABB ACS580

Role
General-purpose variable-speed drive for electric motors.
Typical use
Variable- and constant-torque applications including conveyors, pumps, fans, compressors and mixers.
Diagnostic identifiers
Panel warning labels, numbered faults and auxiliary codes; this reference includes ACS580-01 codes 2310, 2330, 3130, 3210 and 3220.
Important
Meaning depends on the drive variant, voltage class, control program, motor, firmware and installed options.

ABB OmniCore

Role
Robot-controller platform for ABB robotic systems and processes.
Typical use
Material handling, machine tending, picking, packaging, welding, dispensing, cutting and assembly.
Diagnostic identifiers
RobotWare event logs, controller and robot status, system information and configured event domains.
Important
Meaning depends on the controller, robot, RobotWare version, process package, options and configured system.

How to diagnose an ABB device

Use the identifier together with the exact ABB product and its full diagnostic context. A number or display label alone does not establish the cause.

  1. 01Identify the device

    What to check: Exact controller, drive or robot controller, type designation, options and firmware.

    Why it matters: ABB diagnostic meanings depend on the product family and installed configuration.

  2. 02Capture the exact identifier

    What to check: Complete warning or fault number, auxiliary code, message, timestamp and operating state.

    Why it matters: One displayed number can omit the context needed to identify the event.

  3. 03Identify the source

    What to check: Controller, I/O module, drive, communication stack, application, safety component or robot system.

    Why it matters: Similar-looking messages can belong to different ABB diagnostic systems.

  4. 04Read the detailed diagnostics

    What to check: Automation Builder, drive panel and event history, Drive Composer, FlexPendant or RobotStudio.

    Why it matters: Detailed records provide the event context and affected component.

  5. 05Match the correct ABB manual

    What to check: The documentation for the installed product, control program, hardware and firmware version.

    Why it matters: This avoids applying a code meaning from the wrong ABB product or release.

AC500CPU/module LEDs · Automation Builder · Device/application messages
ACS580Warning/fault/auxiliary code · Event history · Parameters · Operating state
OmniCoreFlexPendant event log · RobotWare data · RobotStudio information

ABB ACS580-01 fault codes

Five source-verified fault codes for the ABB ACS580-01 wall-mounted drive. These concise references are not repair instructions. The current ABB firmware and hardware manuals for the installed unit remain authoritative.

2310 · Overcurrent

2310Overcurrent

Documented meaning: ABB documents this as drive output current above the internal limit. The cited guide also notes that an earth fault or phase loss can produce this condition.

Scope: ACS580-01, document 3AXD50001020187. The exact drive variant, control program and firmware manual remain authoritative.

Open the ABB source ↗
2330 · Earth leakage

2330Earth leakage

Documented meaning: ABB describes a load unbalance typically caused by an earth fault in the motor or motor cable.

Scope: ACS580-01, document 3AXD50001020187. The guide identifies the motor and motor cable as relevant context; use the applicable hardware-manual precautions for any testing.

Open the ABB source ↗
3130 · Input phase loss

3130Input phase loss

Documented meaning: ABB states that intermediate DC-circuit voltage is oscillating because an input power-line phase is missing.

Scope: ACS580-01, document 3AXD50001020187. Interpret the event using the installed drive’s voltage configuration and current documentation.

Open the ABB source ↗
3210 · DC link overvoltage

3210DC link overvoltage

Documented meaning: ABB describes the intermediate DC-circuit voltage as too high.

Scope: ACS580-01, document 3AXD50001020187. The installed control-program firmware manual determines the applicable cause and remedy information.

Open the ABB source ↗
3220 · DC link undervoltage

3220DC link undervoltage

Documented meaning: ABB describes the intermediate DC-circuit voltage as too low.

Scope: ACS580-01, document 3AXD50001020187. Match the full event with the installed drive, supply configuration and firmware documentation.

Open the ABB source ↗

ABB-specific questions

What is the difference between ABB AC500 and ACS580?

AC500 is a programmable-controller platform that executes automation logic. ACS580 is a variable-speed drive that controls a motor. They may exchange commands and status in one machine, but their diagnostic messages, engineering tools and electrical hazards are different.

What is the difference between ACS580 and ACS580-01?

ACS580 names the broader general-purpose-drive family. ACS580-01 is the wall-mounted drive variant. A code meaning documented for ACS580-01 should not automatically be applied to ACS580-04 modules, ACS580-07 cabinets or another ABB drive family.

Does ABB use one universal fault-code list?

No. Diagnostics can originate from a controller, I/O module, drive, communication stack, application, safety component or robot system. Use the complete message and exact hardware, project and firmware context rather than treating an isolated number as universal.

Where are OmniCore robot alarms read?

Use the FlexPendant event log and RobotWare system information, supported by RobotStudio when appropriate. Preserve the full event text and configured system rather than searching only for a number.

Manufacturer sources