Schneider Lexium Easy LXM26 Drive Fault Codes
Complete reference list of Schneider Lexium Easy LXM26 servo drive fault codes. Learn to troubleshoot AL codes like AL006 (Overload), AL008 (Encoder Battery), and AL009 (Deviation).
Schneider LXM26 Fault Codes Reference Table
Schneider LXM26 Fault Codes Reference Table
Schneider LXM26 Fault Codes Reference Table
| Fault Code and Meaning | Cause and Remedy |
|---|---|
| AL014 Negative hardware limit switch triggered |
Cause: - Remedy: - |
| AL015 Positive hardware limit switch triggered |
Cause: - Remedy: - |
| AL283 Positive software limit switch triggered |
Cause: - Remedy: - |
| AL285 Negative software limit switch triggered |
Cause: - Remedy: - |
| 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. |
| 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. |
| 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: Refer to parameter P8-49 for details. 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. |
| Wn737 Parameters have been reset to the factory settings, but are not yet saved |
Cause: - Remedy: Use parameter P2-08 = 11 to save parameters reset to the factory settings to the non-volatile memory and restart the drive. |
| 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. |
| Wn743 Fan circuit warning |
Cause: The fan circuit is either overloaded or disconnected. Remedy: Check for fan short circuit or disconnection. |
| Wn744 Excessive electronic noise |
Cause: - Remedy: Check proper grounding and shielding. Use line filter. |
| Wn745 Configured feedbacktype and actual connected encoder mismatch |
Cause: The connected encoder does not correspond to configured feedback type. Remedy: Check that configured feedback type and connected encoder match. |
| Wn746 Encoder overtemperature |
Cause: - Remedy: - |
| Wn747 Encoder internal flash memory error detected |
Cause: - Remedy: - |
| Wn748 Encoderfeedback error detected |
Cause: The device has detected unusually high shaft displacement. The device can still operate correctly; but position error might be higher than usual. Remedy: - |
| Wn749 The multi turn battery voltage is within range: 3 V < VBAT < 3.15V |
Cause: Battery voltage has started to drop; but the multi turn information is still reliable. Remedy: Replace encoder battery. |
| Wn750 The multi turn counter exceeded the range of 16 bit signed value |
Cause: Multi turn Counter < -32768 Or multi turn Counter > 32767 Remedy: Execute multi turn Config/Reset (Set Reference Point) by command P8-44=3/2. For some applications which will rotate motor in one direction, the warning Wn750 can be turned off by parameter P5-80=1. |
| Wn751 The last save operation was interrupted |
Cause: The last save operation was interrupted by power cycle. The old set of parameters are active. Remedy: Set the new parameter configuration and perform save command. |
| Wn752 Stop filter command cannot be set |
Cause: SensAR Encoder Filter Mode is not supported on the connected Motor. Remedy: Set P8-71 to 0 ignore the warning. OR: Upgrade Motor Hardware version. |
| Wn753 Reference position lost |
Cause: AL576 or homing procedure failure or the multi turn roll over will cause this warning. Remedy: Execute multi turnConfig/Reset (Set Reference Point) by command P8-44 = 2. Or Execute a homing procedure. Or set P5-80 to 1. |
| 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 greater 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:
|
| 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:
|
| AL026 Error detected in communication with motor encoder |
Cause: Communication with the encoder was not initialized correctly. Remedy:
|
| 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:
|
| 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:
|
| 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. |
| AL523 System error detected (self-test) |
Cause: The self-test has detected an error. Remedy: Contact technical support. |
| AL525 Reserved |
Cause: - Remedy: - |
| AL526 Reserved |
Cause: - Remedy: - |
| 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:
|
| AL529 Drive overtemperature (controller) |
Cause: Ambient temperature is too high, fan is inoperative, dust. Remedy:
|
| 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: - Remedy: - |
| 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. |
| 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. |
| AL558 System error detected |
Cause: - Remedy: Contact technical support. |
| AL560 Power stage supply off |
Cause: - Remedy: Power on the power stage 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. |
| AL567 System error detected (encoder) |
Cause: Refer to parameter P8-48 for details. 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 that there are no short circuits. |
| AL571 Reference position operation rejected |
Cause: If user direct perform Homing/P8-44 2 after change P1-01 C without power-cycle the drive, then AL571 will report. Remedy: Power-cycle the drive and then perform Homing/P8-44 to 2. |
| 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:
|
| AL573 The returned position values are no longer considered valid |
Cause: Usually caused by bad encoder hardware or bad encoder assembly. For example: damaged hall sensors, damaged encoder rotor, displacement between motor shaft and encoder is too big, corrupted encoder FLASH memory - corrupts calibration tables, SW bug. Remedy: Replace new motor. |
| AL574 The encoder temperature is too high |
Cause: Caused when temperature on encoder is too high relative to what was configured. Remedy: Reduce temperature applied on encoder replace new motor. |
| AL575 The encoder supply voltage has dropped under operational value |
Cause: The device supply voltage has dropped under operational value. Remedy: Make sure power supplied to encoder is according to specifications. |
| AL576 The multi turn encoder battery voltage has dropped under 3 Vdc |
Cause: The multi turn encoder battery voltage has dropped under 3 Vdc; battery box cable disconnect from motor encoder side. Remedy:
|
| AL577 The multi turn encoder requires an explicit configuration command |
Cause: - Remedy: Execute multi turn Config/Reset (Set Reference Point) by command P8-44=3/2. |
| AL578 Internal position synchronization error detected between the multi turn and the single turn modules |
Cause: Possible likely reasons: bad multi turn calibration, corrupted multi turn calibration data on FLASH, Internal multi turn chip failure, bad multi turn chip magnetic screw, SW Bug. Remedy: Replace new motor. |
| AL579 Generic error code of the multi turn module is detected |
Cause: Encoder is damaged or that a magnetic screw is missing or multi turn calibration is either missing or corrupt or battery disconnect form encoder for a long time or the FW version of encoder is below 13020023. Remedy: Reconnect battery to encoder and execute multi turn Config /Reset (Set Reference Point) by command P8-44=3/2. Then, power cycle the drive. If error happen again, replace motor. |
| AL580 The encoder firmware cannot operate on the provided hardware |
Cause: - Remedy: - |
| AL581 The drive firmware cannot operate with the provided encoder version |
Cause: - Remedy: - |
| AL582 Unsupported HW (110V/Multi Turn Encoder/Size 5 power stage) |
Cause: - Remedy: - |
| AL588 RT Overload Fault |
Cause: Real time execution time is more than 31.25 us Mapping large amount of PDO Remedy: Too much load on the real time loop- such as: too much PDO (RX/TX) are mapped/ sync-position/record/touch probe are tasks with large impact to the CPU. |
| AL595 Impermissible combination of drive and motor |
Cause: - Remedy: Use an approved drive/motor combination. |
| AL596 Unstable current loop |
Cause: Excessive overshoot in current loop. Remedy: Verify correct settings of the parameters for the current loop. |
| AL5A0 Drive Locked |
Cause: HW issue causing problem to access the EEprom Remedy: Return drive to factory check HW |
| AL5A1 Drive is not configure |
Cause: - Remedy: Implement factory restore |
How to Read LXM26 Servo Faults
The LXM26 interface is streamlined for quick diagnostics. Here is how to interpret the feedback:
- AL Display: When a fault occurs, the drive stops the motor and flashes AL followed by a 3-digit number.
- AL001 – AL005: Typically Critical Power/Hardware faults (Overcurrent, Overvoltage).
- AL006 – AL009: Typically Motor/Encoder or Overload issues.
- Clearing Faults: Unlike VFDs, many servo faults (like Limit Switch triggers) can be cleared by removing the trigger condition and toggling the Alarm Reset (ALRS) digital input, or by pressing the SET button on the keypad.
- SoMove Software: For deep analysis, connect the drive to a PC using the Schneider SoMove commissioning software. This allows you to view the “Scope” function to see if the motor is oscillating (tuning issue) right before the fault trips.
Frequently Asked Questions (FAQ)
Q: What does “AL008” or “AL012” (Battery Voltage Low) mean?
A: This applies if you are using an Absolute Encoder motor.
The battery providing backup power to the encoder (to remember position when power is off) is dead or disconnected.
Critical: Replace the battery while the control power is ON. If you power down to change it, the absolute position data will be lost, and you will have to re-home (Zero) the machine.
Q: How do I fix “AL006” (Motor Overload)?
A: The motor is working beyond its rated torque for too long.
Causes:
1. Mechanical Binding: Check linear guides, ball screws, or gearboxes for jams.
2. Brake: Ensure the electromagnetic brake is receiving 24V and releasing fully.
3. Tuning: If the “Stiffness” or Gain settings are too high, the motor may be vibrating (buzzing), causing it to overheat.
Q: Why do I get “AL009” or “AL024” (Position Deviation)?
A: This happens in Pulse Train mode. The PLC is sending pulses, but the motor cannot keep up.
Fix:
1. Increase the Position Loop Gain (P1-00) to make the servo more responsive.
2. Check if the max speed limit parameter is capping the motor speed.
3. Verify the electronic gear ratio isn’t set aggressively high.
Q: What is “AL013” (Reverse Limit Switch)?
A: This is not a hardware failure. The axis has moved too far and triggered the Hardware Limit Switch (N-OT) connected to the Digital Inputs.
Fix: Switch the drive to Manual/Jog mode and move the axis in the opposite direction (Positive) to clear the switch.
Comments
Post a Comment