ABB ACS880 Firmware

The drive has detected a significant earth fault or current unbalance in the motor or motor cable and has tripped to protect the system. This indicates a severe insulation breakdown or wiring issue that poses a high risk of equipment damage, fire, or electric shock if not addressed immediately.

The drive has detected a loss of one or more phases in the incoming supply power and has tripped. This fault prevents operation on an unbalanced supply which can cause severe damage to the drive's input rectifier stage and other internal components. It indicates a problem in the electrical supply chain.

The drive has detected an incorrect connection between the input power cables and the motor cables, specifically if the input power is connected to the motor output terminals. This is a critical wiring error that will trip the drive to prevent severe damage to the power unit and motor due to incorrect voltage application.

The drive has detected a loss of one or more phases in the motor's connection. This fault will trip the drive based on the setting in parameter 31.19 Motor phase loss to protect the motor from damage due to unbalanced currents. Running a motor with a phase loss can cause severe winding damage and overheating.

The drive's internal IGBT temperature has exceeded its safe operating limit, indicating potential overheating. This can lead to reduced lifespan or premature failure of the IGBTs if the root cause is not identified and resolved promptly.

An external temperature sensor (either 1 or 2) connected to the drive has registered a temperature beyond its configured fault limit. This indicates a potential overheating condition in the monitored equipment (e.g., motor), risking damage if not addressed.

The drive's cooling fan is either stuck, disconnected, or faulty, leading to insufficient cooling. This will cause the drive to overheat, potentially leading to other temperature-related faults and reduced component lifespan if not resolved promptly.

A critical hardware failure has occurred within the Safe Torque Off (STO) circuit of the drive, compromising safety functionality. This means the drive cannot guarantee safe disconnection of motor torque, requiring specialist intervention to ensure safety integrity.

The Safe Torque Off (STO) function has been activated, meaning the motor's torque production is safely disabled. This usually results from a break in the external safety circuit connected to the XSTO connector or a diagnostic fault setting, preventing the motor from starting or running.

The memory within the drive's Power Unit has been cleared, indicating a loss of configuration or operational data. This internal fault requires expert diagnosis to restore functionality and prevent reoccurrence, as it affects the core logic of the power unit.

There is a discrepancy between the drive's physical hardware identification and the information stored in its memory unit. This often occurs after maintenance such as a firmware update or memory unit replacement, potentially preventing the drive from operating correctly or safely.

The feedback signal from the charging system is missing or not detected. This typically indicates a problem with the charging circuit or its monitoring, which could prevent the drive's DC bus from charging correctly, leading to operational failure or preventing the drive from starting.

An unidentified logical fault has occurred within the power unit. This suggests a deep internal problem with the power unit's control or processing, possibly due to corrupted firmware, a hardware malfunction, or an unexpected state. Unresolved, this prevents the drive from operating reliably and requires expert attention.

An internal software error has occurred within the drive's operating system or application. This is a critical fault indicating a software anomaly that prevents normal operation and usually requires expert intervention to resolve. This can be caused by corrupted memory or an unexpected program state.

The firmware installed on the control board is incompatible with the FPGA logic version on the power unit. This mismatch can occur after updates where one component was updated but the other was not, preventing proper communication and control between the two main drive components. This issue prevents the drive from operating.

A read error occurred with the mapping file for fieldbus adapter A. This file is essential for establishing proper data exchange between the drive and the PLC or control system via the fieldbus. Without a valid mapping file, fieldbus communication will fail, preventing remote control or monitoring.

An internal fault where the drive's processor is experiencing an overload of its internal tasks. This indicates a critical condition where the drive cannot maintain its real-time operations and cannot be reset normally. Continued operation is impossible and typically points to a fundamental software or hardware issue.

An internal fault indicating that the drive's program stack has overflowed its allocated memory. This is a severe internal software issue that prevents the drive from executing code correctly and cannot be reset by the user. It signifies a critical programming error or memory corruption.

An internal file read error has occurred within the drive. This means the drive cannot access critical internal files required for its operation, leading to a non-resettable fault. This could indicate corrupted internal storage or a hardware issue.

An internal error occurred while loading a data record within the drive. This suggests issues with internal data storage integrity or access, which is crucial for drive configuration and operational data. This fault can impact the drive's ability to maintain its settings or proper functionality.

The drive's application file is either incompatible with the current hardware/firmware or has become corrupted during storage or transfer. This critical fault prevents the application from loading and operating the drive, rendering it inoperable.

Loading of a user-defined parameter set failed. This can happen if the requested set does not exist, is incompatible with the control program's version, or if the drive lost power during the loading process. This prevents the drive from operating with the desired configuration, potentially defaulting to an unsafe or incorrect state.

An operating system error indicating that the drive's internal kernel (core operating system) is experiencing an overload. This is a severe internal fault preventing normal drive operation and cannot be reset by the user. It points to a critical issue with the drive's core processing capabilities.

An attempt to load or save drive parameters has failed. This could indicate an issue with internal memory, configuration storage, or a transient software problem during the parameter operation. This can lead to loss of configuration settings or prevent proper drive setup.

The drive has encountered a conflict where a functionality requested by the PLC via Fieldbus Adapter A is either not available on the drive or has not been activated in its configuration. This prevents proper fieldbus control and data exchange, leading to communication errors or incorrect drive behavior.

An internal fault indicating an overflow in the drive's text data storage. This is a software anomaly where the allocated memory for text strings has been exceeded. While often transient, persistent occurrences suggest a deeper software issue.

An internal fault indicating an overflow specifically within a 32-bit text table in the drive's memory. This is a software anomaly where the allocated memory for a specific text data structure has been exceeded. Persistent occurrences indicate a software bug.

An internal fault indicating an overflow specifically within a 64-bit text table in the drive's memory. This is a software anomaly where the allocated memory for a specific text data structure has been exceeded. Persistent occurrences indicate a software bug.

This indicates an internal fault within the drive's system, likely related to memory or file handling. If unaddressed, it could lead to unstable drive operation or data corruption, impacting the drive's reliability and functionality.

Communication has failed between the drive and an installed option module (e.g., FEN-xx or FIO-xx), preventing proper control or feedback. This can lead to loss of specific functionalities controlled by the module, hindering system operation.

The drive has lost communication with its active control location, which could be a control panel or a connected PC tool. This prevents local monitoring and control, making the drive inoperable from that interface and hindering diagnostic efforts.

The motor has entered a stall condition, meaning it's unable to rotate due to excessive mechanical load or insufficient power from the drive. Prolonged stalling can lead to motor and drive overheating and damage if not quickly addressed.

The drive detects an issue with the brake resistor, indicating it might be disconnected, physically damaged, or improperly sized. This prevents proper dissipation of regenerative energy, potentially leading to DC bus overvoltage and drive trips during deceleration.

The brake resistor has overheated beyond its fault limit, indicating it's dissipating too much energy. This can be caused by continuous heavy braking cycles, improper resistor sizing, or inadequate cooling, posing a risk of resistor damage or fire.

A short circuit has been detected in the brake resistor wiring, or there's an issue with the brake chopper control circuit. This prevents the brake resistor from functioning correctly, leading to potential DC bus overvoltage and can damage the chopper or drive components.

A short circuit has occurred within the brake chopper's IGBT, indicating a component failure that disables the regenerative braking function. This prevents the dissipation of excess energy, potentially leading to DC bus overvoltage and further drive damage if not addressed.

The IGBT within the brake chopper has overheated beyond its internal fault limit, often due to high ambient temperatures, cooling fan failure, or excessive braking cycles. This fault protects the IGBT from permanent damage but requires investigation into the cooling system or operational demands.

A mechanical brake control fault has occurred because the brake acknowledgment signal was not as expected during the brake closing sequence. This implies either the brake did not close, its feedback mechanism failed, or an obstruction is present, leaving the motor potentially unsecured or unable to hold position.

A mechanical brake control fault has occurred because the brake acknowledgment signal was not as expected during the brake opening sequence. This implies either the brake did not open, its feedback mechanism failed, or it is stuck, potentially preventing motor rotation or causing excessive load.

The conditions required for opening the mechanical brake cannot be met, often because the brake is being intentionally kept closed by a parameter setting (e.g., 44.11 Keep brake closed) or due to a safety interlock. This prevents motor operation and is usually a configuration or interlock issue.

No motor speed feedback signal is being received by the drive. This fault means the drive cannot accurately monitor motor speed, which is critical for closed-loop control and protection. The drive will likely trip or fail to start reliably, impacting performance and safety.

The motor is rotating at a speed exceeding its configured maximum allowed speed. This can be caused by incorrect speed limits, insufficient braking capacity, or changes in mechanical load under torque control. Uncontrolled overspeed can cause severe mechanical damage to the motor or connected machinery and poses a safety risk.

An internal fault has occurred within the encoder system itself, indicating a problem with the encoder's electronics or processing. This is a critical fault preventing accurate speed/position feedback, rendering closed-loop control impossible. This typically requires specialized assistance.

A feedback fault has occurred with Encoder 1. This can manifest during initial setup due to incorrect wiring, or after sustained operation due to damage, electromagnetic interference, or module failure. It results in a loss of accurate motor position/speed data, which is critical for precise motor control.

A feedback fault has occurred with Encoder 2. This is identical in nature to the Encoder 1 fault but pertains to the second encoder feedback channel, leading to similar loss of accurate motor position/speed data. This can affect dual-feedback systems or applications requiring redundant speed/position control.

This warning signifies an earth fault or current unbalance detected in the motor or its cable. While initially a warning, a persistent or severe leakage indicates a potential insulation breakdown. If left unresolved, it can escalate to a fault trip (2330), cause equipment damage, or pose safety hazards.

This warning is generated when the drive is stopped and either one or both Safe Torque Off (STO) signals are lost. It indicates that the STO function is active or improperly engaged, preventing the drive from starting, but not necessarily tripping if already stopped. This is a crucial indication of a safety circuit status.

This warning is generated by an on-time timer or a value counter configured to monitor motor bearing conditions. The event log provides an auxiliary code to pinpoint the specific source timer/counter that triggered the warning. Unresolved bearing issues can lead to increased friction, overheating, and eventual motor failure.

This warning is generated by an edge counter, likely configured to monitor the number of operations or switching cycles of an output relay. An auxiliary code in the event log will specify which edge counter triggered the warning. Excessive relay operations can indicate a control issue or impending relay failure.

This warning is generated because on-time timer 1 has reached its configured threshold. This indicates that a specific component or process monitored by this timer has been active for a set duration, which might signal a need for maintenance or inspection.

This warning is generated because on-time timer 2 has reached its configured threshold. This indicates that a specific component or process monitored by this timer has been active for a set duration, which might signal a need for maintenance or inspection.

This warning is generated because edge counter 1 has reached its configured threshold. This indicates that a specific event or action monitored by this counter has occurred a set number of times, potentially signaling the end of a component's lifecycle or a need for inspection.

This warning is generated because edge counter 2 has reached its configured threshold. This indicates that a specific event or action monitored by this counter has occurred a set number of times, potentially signaling the end of a component's lifecycle or a need for inspection.

This warning is generated because value counter 1 (also referred to as a value integrator) has reached its configured threshold. This indicates that an integrated value, such as accumulated energy or material flow, has accumulated to a set limit, potentially signaling a need for a process check or maintenance.

This warning is generated because value counter 2 (also referred to as a value integrator) has reached its configured threshold. This indicates that an integrated value, such as accumulated energy or material flow, has accumulated to a set limit, potentially signaling a need for a process check or maintenance.

This warning is generated by an on-time timer, signaling that a specific device requires cleaning based on its operational duration. An auxiliary code in the event log indicates which timer is responsible for triggering this warning. Ignoring this warning can lead to reduced efficiency, overheating, or premature failure of the device.

This warning is generated by a signal supervision function, indicating an abnormality or unexpected condition in a monitored signal, potentially due to out-of-range values, signal loss, or noise. This can affect the drive's control accuracy or lead to unexpected behavior.

Safe Torque Off (STO) signal 1 has been lost or is not correctly applied. This fault often occurs in conjunction with 5091 (if running) or A5A0 (if stopped) and signifies a problem with one leg of the dual-channel STO safety circuit. This compromise of the STO function prevents safe operation.

Safe Torque Off (STO) signal 2 has been lost or is not correctly applied. This fault often occurs in conjunction with 5091 (if running) or A5A0 (if stopped) and signifies a problem with the second leg of the dual-channel STO safety circuit. This compromise of the STO function prevents safe operation.