ACS880 Spinning Traverse

The drive tripped because the motor did not stop within the maximum allowed time for an emergency stop (mode Off3). This time is defined by parameter 31.33 (Emergency ramp supervision delay). When this fault occurs, bit 8 of parameter 06.17 (Drive status word 2) is set, and the drive coasts to a stop.

The parameter settings for the Embedded Fieldbus (EFB) are inconsistent or not compatible with the selected fieldbus protocol. This fault indicates a configuration error within the drive's fieldbus communication setup, preventing proper communication initialization or operation.

The embedded fieldbus (EFB) protocol firmware could not be loaded into the drive. This fault is often caused by a version mismatch between the EFB protocol firmware and the main drive firmware, or by a corrupted firmware image.

An internal fault indicating an overflow condition related to text data within the drive's memory. This typically signifies an internal software or memory management issue, potentially due to unexpected data accumulation or a software bug.

An internal fault indicating an overflow condition in a 32-bit text table within the drive's memory. This is a specific internal software or memory management issue related to the handling of 32-bit data structures for text.

An internal fault indicating an overflow condition in a 64-bit text table within the drive's memory. This is a specific internal software or memory management issue related to the handling of 64-bit data structures for text.

An internal fault indicating an overflow condition related to text files within the drive's memory. This is an internal software or memory management issue, possibly associated with internal logging, diagnostic data storage, or file system limitations.

Communication between the drive and an installed option module has been lost. This fault can be caused by improper seating, physical damage to the module or its slot, or a malfunction of the module itself.

The control panel or PC tool, which is configured as the active control location for the drive, has ceased communicating. This is a programmable fault, influenced by parameter 49.05 (Communication loss action). The auxiliary code specifies the I/O port used for communication (0: Panel, 1: Fieldbus interface A, 2: Fieldbus interface B, 3: Ethernet, 4: D2D/EFB port).

Communication with an I/O extension module has failed, or the module types specified by parameters do not match the detected configuration. The auxiliary code (format XXYY YYYY) provides details: 'XX' specifies the I/O extension module number (01 for parameter group 14, 02 for 15, 03 for 16), and 'YY YYYY' indicates the problem (00 0001: Communication with module failed).

The Safe Torque Off (STO) function is active, meaning the safety circuit signal(s) connected to the XSTO connector have been lost or are incorrect. This programmable warning, indicated by parameter 31.22 (STO indication run/stop), prevents the drive from generating torque, ensuring a safe machine state.

A problem has been detected with an internal temperature measurement circuit within the drive. The auxiliary code (format XXXY YYZZ) specifies the exact location of the issue: 'Y YY' indicates the BCU control unit channel (000 for a ZCU control unit), and 'ZZ' specifies the location (e.g., 1: U-phase IGBT, 2: V-phase IGBT, 3: W-phase IGBT, 4: Power unit INT board, 5: Brake chopper, 6: Air inlet, 7: Power supply board, 8: du/dt filter, FAh: Air in temp).

A power supply failure has occurred on the power unit (PU) board. This indicates an internal issue with the drive's power unit, specifically its power supply circuitry.

Communication errors have been detected between the drive control unit and the power unit. The auxiliary code (format XXXY YYZZ) provides specific details, where 'Y YY' specifies the affected BCU control unit channel (0 for broadcast or ZCU control units), and 'ZZ' indicates the error source (8 for Transmission errors in PSL link, 9 for Transmitter FIFO warning limit hit). 'XXX' specifies the transmission error direction and detailed warning code (e.g., 0 for Rx/communication error, 1 for Tx/Reed-Solomon symbol error).

A main cooling fan is either stuck or disconnected. This warning can be triggered based on the setting of parameter 31.35 (Main fan fault function). The auxiliary code identifies the specific fan (e.g., Main fan 1, 2, or 3) and its state (ID run or normal operation).

An auxiliary cooling fan, typically connected to the control unit's fan connectors, is stuck or disconnected. The auxiliary code specifies which auxiliary fan (1 or 2) is affected. This warning can be generated even when fault 5081 (Auxiliary fan broken) is bypassed, for example, if parameter 31.36 (Aux fan fault bypass) is active during commissioning with the front cover removed.

An error in temperature measurement has been detected when a KTY or PTC temperature sensor is connected to an FEN-xx encoder interface. Specifically, the FEN-01 interface module does not support KTY sensors, which would trigger this warning if incorrectly configured. This indicates a mismatch between sensor type, encoder interface settings, or module activation.

The brake resistor is either broken (indicating an open circuit) or not connected to the drive's brake chopper terminals. This warning signifies a critical issue with the drive's ability to dissipate regenerative energy, potentially leading to overvoltage faults if braking is required.

The temperature of the brake resistor has exceeded the warning limit defined by parameter 43.12 (Brake resistor warning limit). This indicates that the brake resistor is undergoing excessive thermal stress due to continuous or heavy regenerative braking cycles, or insufficient cooling.

One or more of the brake resistor data settings (parameters 43.08, 43.09, 43.10) are incorrect or have not been provided. The auxiliary code specifies the exact parameter at fault: 0000 0001 (Resistance value too low), 0000 0002 (Thermal time constant not given), or 0000 0003 (Maximum continuous power not given).

The speed feedback configuration has either changed or is inconsistent. The auxiliary code (format XXYY ZZZZ) provides detailed information: 'XX' specifies the encoder interface module number (e.g., 01 for 91.11/91.12), 'YY' specifies the encoder (01 for 92 Encoder 1 configuration, 02 for 93 Encoder 2 configuration), and 'ZZZZ' indicates the specific problem (e.g., adapter not found, module type mismatch, logic/software version too old).