Alarm and Fault Indications

+ Alarm/Fault Codes: The drive displays a four-digit code on its 7-segment display, indicating a specific alarm or fault. This code is crucial for identifying the cause of the problem.
+ Field Communication: The code number given in parentheses after the message is used for field communication.

How to Reset

+ Reset Methods: The drive can be reset by pressing the reset button on the PC tool or the RESET button on the control panel, or by temporarily turning off the supply voltage. The motor can be restarted after the fault is cleared.
+ External Reset: A fault can also be reset from an external source using the 10.08 FAULT RESET SEL parameter.

Fault History

+ Fault Recording: When a fault is detected, it is stored in the fault recorder with a timestamp. The fault history stores information on the last 16 faults of the drive. The last three faults are preserved at the top when the power is turned off.
+ Signals: The 8.01 ACTIVE FAULT and 8.02 LAST FAULT signals store the codes of the latest faults.
+ Alarm Monitoring: Alarm information can be monitored through the 8.05 ALARM WORD 1 to 8.08 ALARM WORD 4 alarm words. Alarm information is lost when the power is turned off or the fault is reset.

These details are important for understanding and troubleshooting alarms and faults encountered during the management and maintenance of the ABB ACSM1 drive.

0029 INTERNAL CHOKE TEMPERATURE (0xFF81)

    Issue: The internal AC choke temperature is excessive.
- Check the cooling fan.

0030 EXTERNAL (0x9000)

    Issue: There is a fault in an external device. (This information is configured via one of the programmable digital inputs.)
- Check for faults in external devices.
- Check the setting of the 46.01 EXTERNAL FAULT parameter.

0031 SAFE TORQUE OFF (0xFF7A)

    Issue: Safe Torque Off (STO) function is active, i.e., the safety circuit signal(s) connected to X6 is lost:
- When the drive is starting or running,
- Or when the drive is stopped and the 46.07 STO DIAGNOSTIC setting is (1) Fault.
- Check the safety circuit connections. Refer to the appropriate drive hardware manual for more information.

0032 OVERSPEED (0x7310)

    Issue: The motor is rotating faster than the allowed maximum speed; this may be due to incorrect minimum/maximum speed settings, insufficient brake torque, or changes in load while using torque reference.
- Check the minimum/maximum speed settings, parameters 20.01 MAXIMUM SPEED and 20.02 MINIMUM SPEED.
- Check the adequacy of the motor's brake torque.
- Check the applicability of torque control.
- Check the need for a brake chopper and resistor(s).

0033 BRAKE OPENING TORQUE (0x7185)

    Issue: Mechanical brake fault. The fault is activated when the required motor starting torque, 35.06 BRAKE OPEN TORQ, cannot be provided.
- Check the brake opening torque setting, parameter 35.06.
- Check the torque and current limits of the drive. Refer to the 20 LIMITS parameter group on page 102.

0034 BRAKE NOT CLOSING (0x7186)

    Issue: Mechanical brake control fault. The fault is activated if the expected brake confirmation is not received during brake closure.
- Check the mechanical brake connection.
- Check the mechanical brake settings, parameters 35.01…35.09.
- To determine whether the issue is with the confirmation signal or the brake: Check whether the brake is closed or open.

0035 BRAKE NOT OPENING (0x7187)

    Issue: Mechanical brake control fault. The fault is activated if the expected brake confirmation is not received during brake opening.
- Check the mechanical brake connection.
- Check the mechanical brake settings, parameters 35.01…35.08.
- To determine whether the issue is with the confirmation signal or the brake: Check whether the brake is closed or open.

0036 LOCAL CONTROL LOSS (0x5300)

    Issue: The control panel or PC tool selected as the active control position for the drive has lost communication.
- Check the PC tool or control panel connection.
- Check the control panel connector.
- Replace the control panel in the mounting platform.

0037 NVMEMCORRUPTED (0x6320)

    Issue: Drive internal fault. Note: This fault cannot be reset.
- Check for a fault code extension in the fault recorder.
- Code extension: 2051 The total number of parameters (including unused space between parameters) exceeds the firmware's maximum. Move parameters from firmware groups to application groups. Reduce the number of parameters.
- For other code extensions: Drive internal fault. Contact your local ABB representative.

0038 OPTION COMMUNICATION LOSS (0x7000)

    Issue: Communication has been lost between the drive and the option module (FEN-xx and/or FIO-xx).
- Check that the option modules are correctly connected to Slot 1 and (or) Slot 2.
- Check if the option modules or Slot 1/2 connectors are damaged. To determine whether the module or connector is damaged: Test each module separately in Slot 1 and Slot 2.

0039 ENCODER1 (0x7301)

    Issue: Encoder 1 feedback fault. If the fault occurs during the first initialization without using encoder feedback or while the drive is running with encoder feedback already used, different steps are followed.

If the Fault Occurs During the First Initialization:

    Checks:
- Check the cable and the order of the connector signal wires between the encoder and the encoder interface module (FEN-xx).
- If an absolute encoder is used (EnDat/Hyperface)
- If an absolute encoder is used (EnDat/Hyperface/SSI, plus incremental sin/cos pulses), incorrect cable connection can be detected as follows:
     - Disable serial connection (zero position) by setting parameter 91.02 ABS ENC INTERF to (0) None and test the encoder operation:
        - If the encoder fault is not activated, check the serial connection data cable connection. Note that the zero position is not considered when the serial connection is disabled.
        - If the encoder fault is activated, check the serial connection and sin/cos signal cable connection.
Note: Only the zero position is requested via the serial connection and updated during operation based on the position from sin/cos pulses.
- Check the encoder parameter settings.

If Encoder Feedback Was Already Used or the Fault Occurs While the Drive Is Running:

    Checks:
- Ensure that the encoder connection cable or encoder is not damaged.
- Ensure that the encoder interface module (FEN-xx) connection or module is not damaged.
- Check for grounding issues when communication errors are detected between the encoder interface module and the encoder.

For more information on encoders, refer to parameter groups: 90 ENC MODULE SEL (page 169), 91 ABSOL ENC CONF (page 173), 92 RESOLVER CONF (page 178), and 93 PULSE ENC CONF (page 179). These steps provide basic guidelines to help troubleshoot encoder-related issues. Careful attention to encoder installation, cable connections, and parameter settings is important in preventing such faults.

0040 ENCODER2 (0x7381)

    Issue: Encoder 2 feedback fault, handled similarly to the ENCODER1 fault. An EnDat or SSI encoder is used as encoder 2 in continuous mode.
    Configuration:
- 90.02 ENCODER 2 SEL = (3) FEN-11 ABS
- 91.02 ABS ENC INTERF = (2) EnDat or (4) SSI
- 91.30 ENDAT MODE = (1) Continuous (or 91.25 SSI MODE = (1) Continuous).

    Checks:
- If possible, use single position transfer instead of continuous position transfer (i.e., if the encoder has incremental sin/cos signals):
     - Change the value of parameter 91.25 SSI MODE / 91.30 ENDAT MODE to (0) Initial pos.
- Otherwise, use the Endat/SSI encoder as encoder 1:
     - Change the value of parameter 90.01 ENCODER 1 SEL to (3) FEN-11 ABS and parameter 90.02 ENCODER 2 SEL to (0) None.

0045 FIELDBUS COMMUNICATION (0x7510)

    Issue: Programmable fault: 50.02 COMM LOSS FUNC. The cyclic communication between the drive and the fieldbus adapter module or PLC and the fieldbus adapter module is lost.
- Check the status of the fieldbus communication. Refer to the Fieldbus Adapter Module User Manual.
- Check the fieldbus parameter settings. Refer to the 50 FIELDBUS parameter group on page 156.
- Check the cable connections.
- Check if the communication master can communicate.

0046 FB MAPPING FILE (0x6306)

    Issue: Drive internal fault. Contact your local ABB representative.

0047 MOTOR OVERTEMPERATURE (0x4310)

    Issue: The estimated temperature of the motor (based on the motor thermal model) exceeds the fault limit defined by parameter 45.04 MOT TEMP FLT LIM.
- Check the motor ratings and load.
- Allow the motor to cool down. Ensure proper motor cooling: Check the cooling fan, clean cooling surfaces, etc.
- Check the fault limit value.
- Check the motor thermal model settings, parameters 45.06…45.08 and 45.10 MOT THERM TIME.

Additional Checks>> for MOTOR OVERTEMPERATURE (0047):

    Additional Checks:
- Verify that the actual number of motor temperature sensors matches the value set by parameter 45.02 MOT TEMP SOURCE.
- Ensure proper motor cooling: Check the cooling fan, clean cooling surfaces, etc.
- Check the fault limit value. This is important for safely managing the operating temperature of the motor.

These general checks and suggestions can help in identifying and resolving various encoder and motor overtemperature-related issues, as well as fieldbus communication and analog input supervision faults in the ABB ACSM1 drive.

0049 AI CONTROL (0x8110)

    Issue: Programmable fault: 13.12 AI SUPERVISION. The analog input AI1 or AI2 signal reaches the limit defined by parameter 13.13 AI SUPERVIS ACT.
- Check the source and connections of analog input AI1/2.
- Check the minimum and maximum limit settings of analog input AI1/2, parameters 13.02 and 13.03 / 13.07 and 13.08.
- Ensure that the analog input signals are within the specified limits and that there are no wiring issues.

Important Notes:

    Encoder and motor overtemperature issues are often related to hardware connections, settings, or environmental conditions. Therefore, it is important to review physical checks and parameter settings to resolve these issues.
    Fieldbus communication issues usually arise due to incorrect network connections or settings. These problems can be resolved by carefully checking communication parameters and cable connections.
    AI supervision-related issues are often due to incorrect configuration of analog inputs or source connection errors. Checking analog input settings and connections can help resolve these issues.

By following the steps outlined for each situation and seeking technical support from your local ABB representative if needed, you can ensure the safe and effective operation of your drive.