Schneider Lexium LXM28 Servo Drive Fault Codes:
| Fault Code and Meaning | Cause and Remedy |
|---|---|
| AL014 Negative hardware limit switch triggered | Cause: (Not specified in documentation) Remedy: (Not specified in documentation) |
| AL015 Positive hardware limit switch triggered | Cause: (Not specified in documentation) Remedy: (Not specified in documentation) |
| AL283 Positive software limit switch triggered | Cause: (Not specified in documentation) Remedy: (Not specified in documentation) |
| AL285 Negative software limit switch triggered | Cause: (Not specified in documentation) Remedy: (Not specified in documentation) |
| Wn023 Alert threshold reached: Motor overload (foldback) | Cause: The foldback current of the motor has dropped below the alert threshold specified via the parameter P1-28. Remedy: Verify correct settings of the parameter P1-28 for the foldback current of the motor. |
| Wn123 PDO packet too short | Cause: – Remedy: Verify correct PDO mapping. |
| Wn124 Data in PDO out of range | Cause: – Remedy: Verify that the minimum and maximum limit values are not exceeded. |
| Wn127 R_PDO data cannot be written while the power stage is enabled | Cause: – Remedy: – |
| Wn185 CANopen: A communication error was detected | Cause: – Remedy: – |
| Wn283 Target value will cause movement to positive software limit switch | Cause: – Remedy: Verify correct target positions. |
| Wn285 Target value will cause movement to negative software limit switch | Cause: – Remedy: Verify correct target positions. |
| Wn380 Position deviation via signal output function MC_OK | Cause: After a movement has been successfully completed, MC_OK was active. Then TPOS became inactive which caused MC_OK to become inactive as well. Remedy: If you want this condition to cause a detected error instead of an alert, set the parameter P1-48 accordingly. |
| Wn700 Safety function Safe Torque Off (STO) triggered while the power stage was disabled | Cause: The safety function STO has been triggered or the signal for the safety function STO is not properly connected. If this condition is detected while the power stage is enabled, the drive detects an error. If this condition is detected while the power stage is disabled, the drive detects an alert. Remedy: Check whether the safety function STO was triggered intentionally. If not, verify correct connection of the signal of the safety function STO. |
| Wn701 Alert threshold reached: Drive overload (foldback) | Cause: The foldback current of the drive has dropped below the alert threshold specified via the parameter P1-24. Remedy: Verify correct settings of the parameter P1-24 for the foldback current of the drive. |
| Wn702 The DC bus voltage has dropped below the alert threshold | Cause: Power supply loss, poor power supply. Remedy: Verify correct mains supply. Verify that the undervoltage limit is set correctly via the parameter P4-24. |
| Wn703 Alert threshold reached: Power stage overtemperature | Cause: Ambient temperature is too high, fan is inoperative, dust. Remedy: Verify correct operation of the fan. Improve the heat dissipation in the control cabinet. Remove pollution and verify that dust cannot get into the control cabinet or into the drive. |
| Wn704 Alert threshold reached: Motor overtemperature | Cause: The motor temperature is excessively high. Remedy: Verify correct settings of the parameters for temperature monitoring. Verify proper ventilation and heat dissipation of the motor. Clean off pollutants such as dust. Verify that the motor is evenly mounted to the flange plate. Increase the size of the flange plate to which the motor is mounted to improve heat dissipation. Verify that the motor is properly sized for the application. |
| Wn707 Alert threshold reached: Drive overtemperature (controller) | Cause: Ambient temperature is too high, fan is inoperative, dust. Remedy: Verify correct operation of the fan. Improve the heat dissipation in the control cabinet. Remove pollution and verify that dust cannot get into the control cabinet or into the drive. |
| Wn709 PLL not synchronized | Cause: – Remedy: – |
| Wn713 Positive hardware limit switch and negative hardware limit triggered | Cause: – Remedy: – |
| Wn716 Positive software limit switch and negative software limit triggered | Cause: – Remedy: – |
| Wn728 Alert: Missing mains supply, undervoltage mains supply | Cause: At least one mains phase is missing. Mains voltage is out of range. Mains frequency is out of range. Remedy: Verify correct connection of mains supply. Verify that the values of the mains power supply network comply with the technical data. |
| Wn729 Modbus: Node Guarding error detected | Cause: Incorrect Modbus connection, incorrect data from Modbus master. Remedy: Verify correct Modbus connection. Verify correct operation of Modbus master. |
| Wn730 Alert threshold reached: Braking resistor overload | Cause: The permissible braking resistor power has been exceeded. Remedy: Verify correct rating of the braking resistor used. Verify your application. |
| Wn731 Encoder error detected | Cause: – Remedy: – |
| Wn732 Alert threshold reached: Processing time too long | Cause: – Remedy: – |
| Wn734 Alert threshold reached: Drive overtemperature (IPM) | Cause: Ambient temperature is too high, fan is inoperative, dust. Remedy: Verify correct operation of the fan. Improve the heat dissipation in the control cabinet. Remove pollution and verify that dust cannot get into the control cabinet or into the drive. |
| Wn736 PDO packet too long | Cause: – Remedy: Verify correct PDO mapping. |
| Wn737 The parameters have been reset to the factory settings, but not yet been saved to the non volatile memory. | Cause: – Remedy: Use parameter P2-08 = 11 to save the parameters reset to the factory settings to the non volatile memory and restart the drive. |
| Wn738 No target values received via the fieldbus | Cause: No target values have been received via the fieldbus three times in succession. Remedy: Verify that target values are transmitted via the fieldbus. Verify that the fieldbus has exclusive access. |
| Wn739 Temperature value for monitoring function not available | Cause: – Remedy: – |
| Wn742 Motor type has changed. | Cause: The type of motor connected is different from the previously connected type of motor. Remedy: Reset the drive to the factory settings. |
| AL001 Power stage overcurrent | Cause: An overcurrent has been detected at the power stage which may be caused by a short circuit or by incorrect settings of the current loop parameters. This condition may occur up to three times in succession. After the third time, a time delay of one minute must pass before the power stage can be enabled again. Remedy: Verify correct connection of the motor. Verify correct settings of the parameters for the current loop. |
| AL002 DC bus overvoltage | Cause: The DC bus voltage exceeded the maximum value. Remedy: Verify your application. Reduce the external load, the motor velocity or the deceleration. Use an appropriately rated braking resistor, if necessary. |
| AL003 DC bus undervoltage | Cause: Power supply loss, poor power supply. Remedy: Verify correct mains supply. Verify that the undervoltage limitation is set correctly via the parameter P4-24. |
| AL005 Braking resistor overload | Cause: The braking resistor has been on for such a long period of time that its overload capability has been exceeded. Remedy: Verify your application. Reduce the external load, the motor velocity or the deceleration. Use a braking resistor with a higher rating, if necessary. |
| AL006 Motor overload (foldback) | Cause: The foldback current of the motor has dropped below the value specified via the parameter P1-27. Remedy: Verify correct settings for the parameter P1-27. |
| AL007 Actual motor velocity too high | Cause: The actual motor velocity exceeded the velocity limitation by more than 20% (P1-55). The analog input signal is not stable. Remedy: Verify that the velocity limitation set via the parameter P1-55 matches the requirements of the application. Verify that the values for the tuning parameters are suitable. Verify that the frequency of the analog input signal is stable using a signal detector. Use a filter function. |
| AL008 Frequency of reference value signal is too high | Cause: The frequency of the pulse signal (A/B, Pulse/Direction, CW/CCW) exceeds the specified range. Received pulses may be lost. Remedy: Adapt the output pulse frequency of the external source to fit the input specification of the drive. Adapt the gear ratios to the application requirements (parameters P1-44, P1-45, P2-60, P2-61 and P2-62). |
| AL009 Position deviation too high (following error) | Cause: The position deviation has exceeded the maximum permissible position deviation specified via the parameter P2-35 and the drive has detected a following error. Remedy: Verify your application. Reduce the external load. Increase the permissible position deviation via the parameter P2-35. Reduce the motor velocity via the parameters P1-09 ? P1-11 or the analog input V_REF. Increase the torque limitation via the parameters P1-12 ? P1-14 or the analog input T_REF. |
| AL013 The input to which the signal input function OPST is assigned has been activated. | Cause: – Remedy: Identify the cause which has triggered the signal input function OPST. Remove the cause. If your application does not require the signal input function OPST, disable this signal input function. |
| AL016 Power stage overtemperature | Cause: Ambient temperature is too high, fan is inoperative, dust. Remedy: Verify correct operation of the fan. Improve the heat dissipation in the control cabinet. Remove pollution and verify that dust cannot get into the control cabinet or into the drive. |
| AL017 Error detected in non-volatile memory | Cause: The drive was reset to the factory settings via parameter P2-08. Remedy: Use parameter P2-08 = 11 to save the parameters reset to the factory settings to the non volatile memory and restart the drive. Contact technical support. |
| AL018 Encoder simulation frequency exceeded 4 MHz | Cause: The computed equivalent encoder output frequency exceeds the maximum limit of 4 MHz for this signal. Remedy: Reduce the resolution of the encoder simulation via the parameter P1-46 or reduce the maximum velocity. |
| AL020 Modbus: Node Guarding error detected | Cause: Incorrect Modbus connection, incorrect data from Modbus master. Remedy: Verify correct Modbus connection. Verify correct operation of Modbus master. |
| AL022 Missing mains supply, undervoltage mains supply | Cause: At least one mains phase is missing. Mains voltage is out of range. Mains frequency is out of range. Remedy: Verify correct connection of mains supply. Verify that the values of the mains power supply network comply with the technical data. |
| AL025 Not possible to read data of electronic motor nameplate | Cause: Incorrect or missing motor data. Motor without electronic motor nameplate has been connected. Remedy: Verify that the drive and the connected motor are a permissible product combination. Verify correct connection of the encoder. Contact Technical Support or replace the motor. |
| AL026 Error detected in communication with motor encoder | Cause: Communication with the encoder was not initialized correctly. Remedy: Verify correct connection of the encoder. Contact Technical Support or replace the motor. |
| AL030 Motor torque too high for an excessive period of time | Cause: The motor torque has exceeded the value specified via the parameter P1-57 for a period of time exceeding the value specified via the parameter P1-58. Remedy: Verify your application. Verify that no movements are made up to a mechanical stop (for example, use limit switches). Verify that the values for the parameters P1-57 and P1-58 are suitable. |
| AL180 CANopen: Heartbeat error detected | Cause: The bus cycle time of the CANopen master is higher than the programmed heartbeat or node guard time. The connection between the CANopen master and the drive is lost. Remedy: Verify correct CANopen connection. Check the CANopen master. Verify correct CANopen configuration, increase the Heartbeat or Node Guarding time. |
| AL3E1 Drive is not synchronous with master cycle | Cause: Operating mode has been activated but drive is not synchronized to external synchronization signal. Remedy: Verify correct CANopen connection. After having started the synchronization mechanism, wait for 120 cycles before activating the operating mode. |
| AL401 Fieldbus: Communication error detected | Cause: While the power stage was enabled, a command was received requesting a different communication state. Remedy: Verify that the master does not try to change the communication state while the power stage of the drive is enabled. |
| AL501 Safety function Safe Torque Off (STO) triggered | Cause: The safety function STO has been triggered or the signal for the safety function STO is not properly connected. If this condition is detected while the power stage is enabled, the drive detects an error. If this condition is detected while the power stage is disabled, the drive detects an alert. Remedy: Check whether the safety function STO was triggered intentionally. If not, verify correct connection of the signal of the safety function STO. |
| AL502 System error detected (FPGA) | Cause: – Remedy: Contact technical support. |
| AL503 System error detected (non volatile memory) | Cause: – Remedy: Contact technical support. |
| AL504 System error detected (non volatile memory) | Cause: – Remedy: Contact technical support. |
| AL505 DC bus voltage measurement | Cause: An error was detected in the circuit that measures the DC bus voltage. Remedy: Perform a Fault Reset. Restart the drive. If the error persists, contact Technical Support. |
| AL507 System error detected (NV access) | Cause: – Remedy: Contact technical support. |
| AL508 Drive overload (foldback) | Cause: The foldback current of the drive has dropped below the value specified via the parameter P1-23. Remedy: Verify correct settings for the parameter P1-23. |
| AL514 Motor overtemperature | Cause: The motor temperature is excessively high. Remedy: Verify correct settings of the parameters P8-59 and P8-60 for temperature monitoring. Verify proper ventilation and heat dissipation of the motor. Clean off pollutants such as dust. Verify that the motor is evenly mounted to the flange plate. Increase the size of the flange plate to which the motor is mounted to improve heat dissipation. Verify that the motor is properly sized for the application. |
| AL517 Encoder overvoltage or overcurrent | Cause: The current supplied by the drive for the 5 V encoder supply has exceeded the limit. This condition may occur up to three times in succession. After the third time, a time delay of one second must pass before the power stage can be enabled again. Remedy: Verify correct connection of the encoder (short circuits). Verify the current consumption of the encoder. |
| AL520 Target position rejected | Cause: A target position was rejected because it would have caused the motor to exceed the maximum velocity. Remedy: Verify that target positions do not lead to excessive motor velocities. |
| AL522 System error detected (CAN power supply) | Cause: The internal supply voltage for the CAN bus is not correct. Remedy: Contact technical support. |
| AL523 System error detected (self test) | Cause: The self test has detected an error. Remedy: Contact technical support. |
| AL525 Reserved | Cause: Reserved Remedy: Reserved |
| AL526 Reserved | Cause: Reserved Remedy: Reserved |
| AL527 System error detected (Watchdog) | Cause: The Watchdog function has detected a system error. Remedy: Restart the drive. If the error persists, contact Technical Support. |
| AL528 Drive overtemperature (IPM) | Cause: Ambient temperature is too high, fan is inoperative, dust. Remedy: Verify correct operation of the fan. Improve the heat dissipation in the control cabinet. Remove pollution and verify that dust cannot get into the control cabinet or into the drive. |
| AL529 Drive overtemperature (controller) | Cause: Ambient temperature is too high, fan is inoperative, dust. Remedy: Verify correct operation of the fan. Improve the heat dissipation in the control cabinet. Remove pollution and verify that dust cannot get into the control cabinet or into the drive. |
| AL532 Calculated offsets for current sensors out of range | Cause: The calculated offsets for the current sensors are out of range. Remedy: Perform a Fault Reset. Restart the drive. If the error persists, contact Technical Support. |
| AL533 Reserved | Cause: Reserved Remedy: Reserved |
| AL534 Pulse signal missing | Cause: One of the pulse signals is not connected. Remedy: Verify correct connection of the pulse inputs. |
| AL535 System error detected (FPGA does not match firmware) | Cause: The firmware version is not suitable for the drive. Remedy: Update the firmware of the drive. Contact technical support. |
| AL539 Motor phase missing | Cause: One of the motor phases is not connected. Remedy: Verify correct connection of the motor phases. Contact technical support. |
| AL547 Motor blocked | Cause: The motor was blocked mechanically, for example, by a mechanical stop or by the load. Remedy: Remove condition causing the mechanical blocking. Verify your application. |
| AL553 No connection between master and drive | Cause: – Remedy: Connect master and drive. |
| AL554 Target position rejected | Cause: A target position was rejected because it would have caused the motor to exceed the maximum acceleration/deceleration. Remedy: Verify that target positions do not lead to excessive acceleration/deceleration. |
| AL555 Velocity deviation too high | Cause: The deviation between actual velocity and reference velocity has exceeded the maximum velocity deviation specified via the parameter P2-34. Remedy: Verify your application. Verify that the values for the tuning parameters are suitable. Increase the value for the maximum velocity deviation in the parameter P2-34. |
| AL557 No target values received via the fieldbus | Cause: No target values have been received via the fieldbus three times in succession. Remedy: Perform a Fault Reset. Verify that target values are transmitted via the fieldbus. |
| AL558 System error detected | Cause: – Remedy: Contact technical support. |
| AL560 Controller supply off | Cause: – Remedy: Power on the controller supply. |
| AL561 Temperature sensor inoperative | Cause: – Remedy: Restart the drive. If the error persists, contact Technical Support. |
| AL563 Commutation error detected | Cause: Motor phases have been interchanged. Remedy: Verify correct connection of the motor phases. |
| AL564 Position deviation via signal output function MC_OK | Cause: After a movement has been successfully completed, MC_OK was active. Then TPOS became inactive which caused MC_OK to become inactive as well. Remedy: Use the signal input function FAULT_RESET to perform a Fault Reset and set the parameter P0-01 to 0. If you want this condition to cause an alert instead of a detected error, set the parameter P1-48 accordingly. |
| AL567 System error detected (encoder) | Cause: – Remedy: Contact technical support. |
| AL568 Braking resistor overload | Cause: The permissible braking resistor power has been exceeded. Remedy: Verify correct rating of the braking resistor used. Verify your application. |
| AL569 Configuration not correctly transferred via Modbus | Cause: – Remedy: Verify correct connection. Verify that configuration file and drive are compatible. |
| AL570 Overcurrent detected at one of the digital outputs | Cause: – Remedy: Verify correct wiring of the digital outputs. Verify there are no short circuits. |
| AL572 Position deviation too high (following error) | Cause: The position deviation has exceeded the maximum permissible position deviation specified via the parameter P2-35 and the drive has detected a following error. Remedy: Verify your application. Reduce the external load. Increase the permissible position deviation via the parameter P2-35. Reduce the motor velocity via the parameters P1-09 ? P1-11 or the analog input V_REF. Increase the torque limitation via the parameters P1-12 ? P1-14 or the analog input T_REF. |
| AL585 CANopen device in state bus-off | Cause: Too many error frames have been detected. CANopen devices have different baud rates. Remedy: Verify correct baud rates. Verify CANopen bus installation. |
| AL588 Reserved | Cause: Reserved Remedy: Reserved |
| AL595 Impermissible combination of drive and motor | Cause: – Remedy: Use an approved drive/motor combination. |