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.

0050 ENCODER 1 CABLE (0x7389)
    Issue: A fault has been detected in the Encoder 1 cable.
- Check the cable between the FEN-xx interface and Encoder 1.
- After any changes in cable connections, reconfigure the interface by turning the drive power off and on or by activating the 90.10 ENC PAR REFRESH parameter.

0051 ENCODER 2 CABLE (0x738A)
    Issue: A fault has been detected in the Encoder 2 cable.
- Similarly, check the cable between the FEN-xx interface and Encoder 2 and reconfigure the interface if necessary.

0052 D2D CONFIGURATION (0x7583)
    Issue: The drive-to-drive connection configuration has failed.
    Action: Contact your local ABB representative.

0053 D2D COMMUNICATION (0x7520)
    Issue: No response was received from a follower that was activated in five consecutive polling cycles from the master drive.
- Ensure that all drives are powered, the connection is correct, and they have the correct node address.
- Check the drive-to-drive connection cabling.

0054 D2D BUF OVLOAD (0x7520)
    Issue: The transmission of references from drive to drive failed due to message buffer overflow.
    Action: Contact your local ABB representative.

0055 TECHNOLOGY LIBRARY (0x6382)
    Issue: A resettable fault generated by a technology library.
    Action: Refer to the documentation of the technology library.

0056 TECHNOLOGY LIBRARY CRITICAL (0x6382)
    Issue: A permanent fault generated by a technology library.
    Action: Refer to the documentation of the technology library.

0057 EMERGENCY STOP (0xFF90)
    Issue: General Drive Communication Profile stop command.
- Check the status of the PLC.

0058 FIELDBUS PARAMETER ERROR (0x6320)
    Issue: The drive does not have the functionality requested by the PLC or the requested functionality is not enabled.
- Check the PLC programming.
- Check the fieldbus parameter settings.

0061 SPEED FEEDBACK (0x8480)
    Issue: Speed feedback is not being received.
- Check the settings of the 22 SPEED FEEDBACK parameter group.
- Check the encoder setup. For more information, see the description of fault 0039 (ENCODER1).

These steps provide basic checks and suggestions to guide you in troubleshooting encoder cable, D2D (Drive to Drive) communication and configuration issues, technology library errors, fieldbus parameter errors, and speed feedback problems, as well as other related issues in your ABB ACSM1 drive.

0062 D2D SLOT COMMUNICATION (0x7584)

    Issue: The drive-to-drive connection is set to use an FMBA module for communication, but no module is detected in the specified slot.
- Check the settings of parameters 57.01 LINK MODE and 57.15 D2D COMM PORT.
- Ensure that the FMBA module is detected by checking parameters 9.20…9.22.
- Check that the FMBA module is correctly cabled.
- If the problem persists, try moving the FMBA module to another slot. If the problem continues, contact your local ABB representative.

0067 - 0069 FPGA and ADC ERRORS (0x5401, 0x5402, 0x5403)
    Issue: Drive internal errors.
    Action: These types of errors are usually more technical and complex, so contact your local ABB representative.

0201 - 0209 FIRMWARE AND APPLICATION TIMEOUT ERRORS (0x0201, 0x6100 series)
    Issue: Overload and startup errors at firmware and application time levels.
>> Note: These errors cannot be reset and usually indicate serious issues within the drive's internal workings.
    Action: Contact your local ABB representative. These types of errors may require an in-depth analysis of the hardware or software and possibly servicing or replacing the drive.

0210 JMU MISSING (0xFF61)
    Issue: The JMU (Jog Memory Unit) is missing or faulty.
- Check if the JMU is properly installed.
- If the problem persists, replace the JMU.

0301 UFF FILE READ (0x6300)
    Issue: File read error.
    Action: Contact your local ABB representative.

0302 - 0307 DRIVE INTERNAL ERRORS (0x6100 series)
    Issues: Drive internal errors include file creation, FPGA configuration directory, drive internal evaluation ID, evaluation database, licensing, and default file errors.
    Action: These errors cannot be reset. Contact your local ABB representative for resolution.

0308 APPLICATION FILE PAR CONFIGURATION (0x6300)
    Issue: Corrupted application file.
- Reload the application.
- If the problem persists, contact your local ABB representative.

0309 APPLICATION LOADING (0x6300)
    Issue: Application file is incompatible or corrupted.
- Check for a fault code extension in the fault recorder and see the appropriate actions for each extension.
> Extension 8: The template used in the application is incompatible with the drive software. Change the application template in DriveSPC.
> Extension 10: The parameters defined in the application clash with the existing drive parameters. Check the conflicting parameters in the application.
> Extension 35: Application memory is full. Contact your local ABB representative.
> Other Extensions: Corrupted application file. Reload the application. If the problem persists, contact your local ABB representative.

0310 USER SETTING LOADING (0xFF69)
    Issue: Loading of user settings failed because:
- The requested user setting is not available.
- The user setting is not compatible with the drive program.
- The drive was turned off during loading.
    Solution: Try reloading.

0311 USER SETTING SAVING (0xFF69)

    Issue: User setting cannot be saved due to memory corruption.
- Check the setting of parameter 95.01 CTRL UNIT SUPPLY.
- If the problem persists, contact your local ABB representative.

0312 UFF SIZE OVERFLOW (0x6300)
    Issue: UFF file is too large.
    Action: Contact your local ABB representative.

0313 UFF EOF (0x6300)
    Issue: Error in the structure of the UFF file.
    Action: Contact your local ABB representative.

0314 TECHNOLOGY LIBRARY INTERFACE (0x6100)
    Issue: Firmware interface is incompatible.
    Action: Contact your local ABB representative.

0315 RESTORE FILE (0x630D)
    Issue: Failed to restore backed-up parameters.
    Action: Contact your local ABB representative.

0316 DAPS INCOMPATIBILITY (0x5484)
    Issue: Incompatibility between the JCU Control Unit firmware and the power unit logic versions.
    Action: Contact your local ABB representative.

0317 SOLUTION FAULT (0x6200)

    Issue: Fault generated by the SOLUTION_FAULT function block in the application program.
- Check the use of the SOLUTION_FAULT block in the application program.

-----

+ ABB ACSM1 User Manuals >

+ ACSM1 Fault Codes 1 >>

+ ACSM1 Fault Codes 2 >>

+ ACSM1 Fault Codes 3 >>

+ ACSM1 Fault Codes 4 >>   


++ ABB Home page (2)

+ VFD Main page  

-