Schneider Lexium LXM16D Servo Drive

Schneider Lexium LXM16D Servo Drive Fault Codes:

Fault Code and Meaning	Cause and Remedy
1100 Parameter out of permissible value range	Cause: The value entered was outside of the permissible value range for this parameter. Remedy: The entered value must be within the permissible value range.
1101 Parameter does not exist	Cause: Error detected by parameter management: Parameter (subindex) does not exist. Remedy: Select a different parameter (index).
1102 Parameter does not exist	Cause: Error detected by parameter management: Parameter (subindex) does not exist. Remedy: Select a different parameter (sub-index).
1103 Parameter write not permissible (READ only)	Cause: Write access to read only parameter. Remedy: Write only to parameters that are not read-only.
1104 Write access denied (no access authorization)	Cause: Parameter only accessible at expert level. Remedy: The write access level expert is required.
1105 Block upload / Download not initialized	Cause: N/A Remedy: N/A
1106 Command not permissible while power stage is active	Cause: Command not permissible while the power stage is enabled (operating state Operation Enabled or Quick Stop Active). Remedy: Disable the power stage and repeat the command.
1107 Access via other interfaces blocked	Cause: Access occupied by another channel (for example: Commissioning software is active and fieldbus access was tried at the same time). Remedy: Verify the channel that blocks access.
1108 File cannot be uploaded: Incorrect file ID	Cause: N/A Remedy: N/A
1109 Data stored after a power outage is invalid	Cause: N/A Remedy: N/A
110A System error detected: No Bootloader available	Cause: N/A Remedy: N/A
110B Configuration download error detected	Cause: Error detected during parameter check (for example, reference velocity value for operating mode Profile Position is greater than maximum permissible velocity of drive). Remedy: Value in additional error information shows the Modbus register address of the parameter where the initialization error was detected.
110D Basic configuration of drive required after factory setting	Cause: “The ‘First Setup’ (FSU) was not run at all or not completed. Remedy: Perform a First Setup.
110E Parameter changed that requires a restart of the drive	Cause: Only displayed by the commissioning software. A parameter modification requires the drive to be powered off and on. Remedy: Restart the drive to activate the parameter functionality. See the chapter Parameters for the parameter that requires a restart of the drive.
110F Function not available in this type of device	Cause: The specific type of device does not support this function or this parameter value. Remedy: Verify that you have the correct device type, in particular type of motor, type of encoder, holding brake.
1110 Incorrect file ID for upload or download	Cause: The specific type of device does not support this kind of file. Remedy: Verify that you have the correct device type or the correct configuration file.
1111 File transfer not correctly initialized	Cause: A previous file transfer has been aborted. Remedy: N/A
1112 Locking of configuration denied	Cause: An external tool has tried to lock the configuration of the drive for upload or download. This may not work because another tool had already locked the configuration of the drive or the drive is in an operating state that does not allow locking. Remedy: N/A
1113 System not locked for configuration transfer	Cause: An external tool has tried to transfer the configuration without locking the drive. Remedy: N/A
1114 Configuration download aborted	Cause: During a configuration download, a communication error or an error in the external tool was detected. The configuration was only partially transferred to the drive and might be inconsistent now. Remedy: Power the drive off/on and retry to download the configuration or restore the factory settings.
1115 Incorrect configuration file format	Cause: An external tool has downloaded a configuration which has an incorrect format. Remedy: N/A
1116 Request is processed asynchronously	Cause: N/A Remedy: N/A
1117 Asynchronous request blocked	Cause: Request to a module is blocked because the module is currently processing another request. Remedy: N/A
1118 Configuration data incompatible with device	Cause: The configuration data contains data from a different device. Remedy: Verify device type including type of power stage.
1119 Incorrect data length, too many bytes	Cause: N/A Remedy: N/A
111A Incorrect data length, insufficient number of bytes	Cause: N/A Remedy: N/A
111B Configuration download error detected	Cause: During a configuration download, one or more configuration values were not accepted by the drive. Remedy: Verify that the configuration file is valid and matches the type and version of the drive. The value in the additional error info shows the Modbus register address of the parameter where the initialization error was detected.
111C Not possible to initialize recalculation for scaling	Cause: A parameter could not be initialized. Remedy: The address of the parameter that caused the detected error can be read via the parameter _PAR_ScalingError.
111D Original state of a parameter cannot be restored	Cause: The drive contained an invalid configuration before the recalculation was started. An error was detected during the recalculation. Remedy: Power the drive off and on again. This may help you to identify the affected parameter(s). Change the parameters as required. Verify that the parameter configuration is valid before starting the recalculation procedure.
1123 Parameter cannot be changed	Cause: Recalculation for scaling is running. Remedy: Wait for the running recalculation for scaling to finish.
1124 Timeout during recalculation for scaling	Cause: The time between the initialization of the recalculation and the start of the recalculation has been exceeded (30 seconds). Remedy: Recalculation must be started within 30 seconds after initialization.
1125 Scaling not possible	Cause: The scaling factors for position, velocity or acceleration/deceleration are beyond internal calculation limits. Remedy: Retry with different scaling factors.
1126 Configuration is blocked by another access channel	Cause: N/A Remedy: Close other access channel (for example, other instance of commissioning software).
1127 Invalid key received	Cause: N/A Remedy: N/A
112D Configuration of edges is not supported	Cause: The selected capture input does not support rising and falling edge at the same time. Remedy: Set the edge to either “rising” or “falling”.
1130 PTI pulse conflicts with home return in gear mode	Cause: Home return is not allowable when PTI has pulse. Remedy: Don’t perform home return when PTI has pulse.
1131 PTI pulse conflicts with Jog test run in gear mode	Cause: Jog test run is not allowable when PTI has pulse. Remedy: Don’t perform Jog test run when PTI has pulse.
1310 Frequency of the external reference value signal too high	Cause: The frequency of the external reference signals (A/B signals, P/D signals or CW/CCW signals) is higher than the permissible value. Remedy: Verify the frequency of the external reference values. Verify the gear ratio in the operating mode Electronic Gear.
1311 The selected signal input function… cannot be configured	Cause: The selected signal input function or signal output function cannot be used in the selected operating mode. Remedy: Select another function or change the operating mode.
1312 Limit switch or reference switch signal not defined	Cause: Reference movements require limit switches. These limit switches are not assigned to inputs. Remedy: Assign the signal input functions Positive Limit Switch, Negative Limit Switch, and Reference Switch.
1313 Configured debounce time not possible for this signal input function	Cause: The signal input function does not support the selected debounce time. Remedy: Set the debounce time to a valid value.
1314 At least two inputs have the same signal input function	Cause: The same signal input function has been assigned to at least two inputs. Remedy: Reconfigure the inputs.
1315 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 frequency of the reference value signal to match the input specification of the drive. Also adapt the gear ratio in the operating mode Electronic Gear to the application requirements (position accuracy and velocity).
1317 Interference at PTI input	Cause: Interfering pulses or impermissible edge transitions (A and B signal simultaneously) have been detected. Remedy: Verify cable specifications, shield connection and EMC.
1600 Oscilloscope: No additional data available	Cause: N/A Remedy: N/A
1601 Oscilloscope: Parameterization incomplete	Cause: N/A Remedy: N/A
1602 Oscilloscope: Trigger variable not defined	Cause: N/A Remedy: N/A
1606 Logging still active	Cause: N/A Remedy: N/A
1607 Logging: No trigger defined	Cause: N/A Remedy: N/A
1608 Logging: Invalid trigger option	Cause: N/A Remedy: N/A
1609 Logging: No channel selected	Cause: N/A Remedy: N/A
160A Logging: No data available	Cause: N/A Remedy: N/A
160B Parameter cannot be logged	Cause: N/A Remedy: N/A
160C Autotuning: Moment of inertia outside permissible range	Cause: The load inertia is too high. Remedy: Verify that the system can easily be moved. Verify the load. Use a differently rated drive.
160E Autotuning: Test movement could not be started	Cause: N/A Remedy: N/A
160F Autotuning: Power stage cannot be enabled	Cause: Autotuning was not started in the operating state Ready to Switch On. Remedy: Start Autotuning when the drive is in the operating state Ready to Switch On.
1610 Autotuning: Processing stopped	Cause: Autotuning stopped by user command or by detected error (see additional error message in error memory, for example, DC bus undervoltage, limit switches triggered). Remedy: Remove the cause of the stop and restart Autotuning.
1611 System error detected: Parameter could not be written during Autotuning	Cause: N/A Remedy: N/A
1612 System error detected: Parameter could not be read during Autotuning	Cause: N/A Remedy: N/A
1613 Autotuning: Maximum permissible movement range exceeded	Cause: The movement exceeded the adjusted movement range during Autotuning. Remedy: Increase the movement range value.
1614 Autotuning: Already active	Cause: Autotuning has been started twice simultaneously or an Autotuning parameter is modified during Autotuning. Remedy: Wait for Autotuning to finish before restarting Autotuning.
1615 Autotuning: This parameter cannot be changed while Autotuning is active	Cause: Parameter AT_gain or AT_J are written during Autotuning. Remedy: Wait for Autotuning to finish before changing the parameter.
1617 Autotuning: Friction torque or load torque too great	Cause: The current limit has been reached (parameter P4-08). Remedy: Verify that the system can easily be moved. Verify the load. Use a differently rated drive.
1618 Autotuning: Optimization aborted	Cause: The internal Autotuning sequence has not been finished, there may have been a following error. Remedy: See the additional information provided in the error memory.
1619 Autotuning: Velocity jump in parameter AT_n_ref is not sufficient	Cause: Parameter AT_n_ref < 2 * AT_n_tolerance. The drive only checks this for the first velocity jump. Remedy: Modify the parameter AT_n_ref or AT_n_tolerance to meet the required condition.
1620 Autotuning: Load torque too high	Cause: Product rating is not suitable for the machine load. Detected machine inertia is too high compared to the inertia of the motor. Remedy: Reduce load, verify rating.
1621 System error detected: Calculation error	Cause: N/A Remedy: N/A
1622 Autotuning: Not possible to perform Autotuning	Cause: Autotuning can only be performed if no operating mode is active. Remedy: Terminate the active operating mode or disable the power stage.
1623 Autotuning: HALT request has stopped the autotuning process	Cause: Autotuning can only be performed if no operating mode is active. Remedy: Terminate the active operating mode or disable the power stage.
1624 Auto adaptive tuning: The acceleration and deceleration below the lower limit	Cause: Acceleration below lower limit; inaccurate identification of real-time auto tuning. Remedy: Increase the operational acceleration and deceleration.
1625 Adaptive notch filter: Oscillation frequency below the lower limit	Cause: When the oscillation frequency is less than 150Hz, the adaptive notch filter exhibits no obvious suppression effect. Remedy: N/A
1A00 System error detected: FIFO memory overflow	Cause: N/A Remedy: N/A
1A01 Motor has been changed (different type of motor)	Cause: Detected motor type is different from previously detected motor. Remedy: Confirm the change.
1A03 System error detected: Hardware and firmware do not match	Cause: N/A Remedy: N/A
1A04 System error detected: SDFM value not read in time	Cause: N/A Remedy: Please contact the Technical Support Department.
1B00 System error detected: Incorrect parameters for motor and power stage	Cause: Incorrect manufacturer parameter value (data) non-volatile memory of device. Remedy: Replace device.
1B02 Target value too high.	Cause: N/A Remedy: N/A
1B04 Product of encoder simulation resolution and the maximum velocity is too high	Cause: Value in parameter P4-07 or resolution or the encoder simulation P0-18 are too high. Remedy: Reduce the resolution of the encoder simulation in parameter P0-18 or the maximum velocity in parameter P4-07.
1B05 Error detected during parameter switching	Cause: N/A Remedy: N/A
1B0B The operating state at the beginning of the commutation offset identification must be Ready To Switch On	Cause: N/A Remedy: Set the operating state to Ready To Switch On and restart commutation offset identification.
1B0C Motor velocity too high.	Cause: N/A Remedy: N/A
1B0F Velocity deviation too high	Cause: N/A Remedy: N/A
2201 System error detected: DC bus transfer error	Cause: N/A Remedy: N/A
2300 Power stage overcurrent	Cause: Motor short circuit and disabling of the power stage. Motor phases are inverted. Remedy: Verify the motor power connection.
2301 Braking resistor overcurrent	Cause: Braking resistor short circuit. Remedy: If you use an external braking resistor, verify correct wiring and rating of the braking resistor.
2302 Output stage U-phase Sigma Delta overcurrent	Cause: Short circuit of the U phase of motor to the ground and other phases occurs or the output stage is disabled. Wrong wiring of phase line for motor. Remedy: Eliminate the short circuit and ensure the power cable connection of motor is correct.
2303 Output stage W-phase Sigma Delta overcurrent	Cause: Short circuit of the W phase of motor to the ground and other phases occurs or the output stage is disabled. Wrong wiring of phase line for motor. Remedy: Eliminate the short circuit and ensure the power cable connection of motor is correct.
2304 Output stage U- and W-phase Sigma Delta overcurrent	Cause: Short circuit of the U and W phases of motor to the ground and other phases occurs or the output stage is disabled. Wrong wiring of phase line for motor. Remedy: Eliminate the short circuit and ensure the power cable connection of motor is correct.
2305 Excessively large output stage current offset	Cause: Excessively high load, motor stalling, loss of encoder connection, or incorrect connection of motor phase lines. Remedy: Check the connection between motor and load; check the encoder connection; check the power cable connection of motor.
3100 Absence of power supply, undervoltage or overvoltage	Cause: The absence of phase lasts longer than 50 ms. The supply voltage is outside the valid range. The supply frequency is outside the valid range. Remedy: Assure the consistency of supply voltage with technical parameters.
3101 Absence of 24V output of switching power supply	Cause: Switching power supply is out of service. Remedy: Please contact the Technical Support Department.
3200 DC bus overvoltage	Cause: Excessively regeneration during deceleration. Remedy: Verify correct deceleration ramp, rating of drive and braking resistor.
3201 DC bus undervoltage (shutdown threshold)	Cause: Power supply outage, insufficient power supply. Remedy: Verify mains supply.
3202 DC bus undervoltage (Quick Stop threshold)	Cause: Power supply outage, insufficient power supply. Remedy: Verify mains supply.
3206 Undervoltage DC bus, missing mains supply…	Cause: Lack of power supply or insufficient supply voltage. Remedy: Verify that the values of the mains power supply network comply with the technical data.
4100 Power stage overtemperature	Cause: Transistors overtemperature: Ambient temperature is too high, fan is inoperative, dust. Remedy: Verify the fan, improve the heat dissipation in the cabinet.
4101 Power stage overtemperature	Cause: Transistors overtemperature: Ambient temperature is too high, fan is inoperative, dust. Remedy: Verify the fan, improve the heat dissipation in the cabinet.
4102 Power stage overload (I²t)	Cause: The current has exceeded the nominal value for an extended period of time. Remedy: Verify rating, reduce cycle time.
4200 Device overtemperature	Cause: Excessively high ambient temperature due to, for example, dust. Remedy: Improve heat dissipation in the control cabinet. If a fan is installed, verify correct operation of the fan. Install a fan in the control cabinet. Improve heat transfer from the rear wall of the device to the control cabinet.
4201 Excessively high temperature of CPU	Cause: Excessively high ambient temperature, dust or other factors impair the heat dissipation. Remedy: Improve the heat dissipation of control cabinet. Please assure the proper functioning of fan (if any). Please install a fan in the control cabinet. Please improve the thermal conductivity from the back of equipment to the control cabinet.
4302 Motor overload (I²t)	Cause: The current has exceeded the nominal value for an extended period of time. Remedy: Verify that the system can easily be moved. Verify the load. Use a differently sized motor, if necessary.
4402 Braking resistor overload (I²t > 75%)	Cause: Regeneration energy too high. External loads too high. Motor velocity too high. Deceleration too fast. Insufficient braking resistor. Remedy: Reduce load, velocity, deceleration. Verify correct braking resistor rating.
4403 Braking resistor overload (I²t > 100%)	Cause: Regeneration energy too high. External loads too high. Motor velocity too high. Deceleration too fast. Insufficient braking resistor. Remedy: Reduce load, velocity, deceleration. Verify correct braking resistor rating.
5207 Function is not supported	Cause: The hardware revision does not support the function. Remedy:
5430 System error detected: EEPROM read error	Cause: System error detected. Remedy:
5431 System error: EEPROM write error	Cause: System error detected. Remedy:
5446 System error detected: EEPROM checksum error (used for power outage data)	Cause: Internal EEPROM not operative. Remedy: Restart the drive. If the detected error persists, contact Technical Support.
5600 Motor connection phase error detected	Cause: Missing motor phase. Remedy: Verify connection of motor phases.
5603 Commutation error detected	Cause: Incorrect wiring of motor cable. Encoder signals are lost or subject to interference. The load torque is greater than the motor torque. The encoder EEPROM contains incorrect data. Remedy: Verify motor phases, verify encoder wiring. Improve EMC, verify grounding and shield connection. Use a differently sized motor that can withstand the load torque. Verify the motor data. Contact Technical Support.
5604 Output stage overcurrent is detected	Cause: Incorrect encoder signal/incorrect connection of motor phase line/motor overload. Remedy: Assure the correct connection of encoder/ensure the correct power connection for motor/check the mechanical system to avoid stalling; check the matching between motor and load; check the acceleration ramp.
610D Error detected in selection parameter	Cause: Incorrect parameter value selected. Remedy: Verify the value to be written.
6114 System error detected: Impermissible function call from interrupt service routine	Cause: Incorrect programming. Remedy:
7100 System error detected: Invalid power stage data	Cause: Error detected in power stage data stored in device (incorrect CRC), error detected in internal memory data. Remedy: Contact Technical Support or replace the device.
7111 Parameter cannot be changed because the external braking resistor is active	Cause: An attempt is made to change one of the parameters P0-22, P0-23 or P0-24 even though the external braking resistor is active. Remedy: Verify that the external braking resistor is not active if one of the parameters P0-22, P0-23 or P0-24 has to be changed.
7122 Invalid motor data parameter	Cause: Error detected in motor data stored in motor encoder, error detected in internal memory data. Remedy: Contact Technical Support or replace the motor.
712D Motor model data not configured	Cause: Motor model data not configured. Remedy: Perform FSU “first setup” or set the parameter P6-00.
7136 Incorrect encoder type selected with parameter P6-01	Cause: Remedy: Perform FSU “first setup” or set the parameter P6-01.
7139 Encoder offset: Data segment in encoder is incorrect	Cause: Remedy:
713B Motor has been changed (different type of motor)	Cause: Detected motor type is different from previously detected motor. Remedy: Power-on the servo drive again. Restore the servo drive to factory default. Contact Technical Support or replace the device.
7200 System error detected: Calibration analog/digital converter during manufacturing / incorrect BLE file	Cause: Remedy:
7347 System error detected: Position initialization not possible	Cause: Analog and digital encoder signals subject to massive interference. Remedy: Reduce encoder signal interference, verify shield connection. Contact Technical Support.
7500 RS485/Modbus: Overflow error detected	Cause: EMC, cabling. Remedy: Verify cables.
7501 RS485/Modbus: Framing error detected	Cause: EMC, cabling. Remedy: Verify cables.
7502 RS485/Modbus: Parity error detected	Cause: EMC, cabling. Remedy: Verify cables.
7503 RS485/Modbus: Receive error detected	Cause: EMC, cabling. Remedy: Verify cables.
760C Maximum encoder frequency exceeded	Cause: Velocity too high for the encoder. Remedy:
7619 Incorrect communication between module and encoder	Cause: Incorrect encoder wiring/adjustment or incorrect encoder parameter settings. Remedy: Verify encoder cable: wiring and shield connection. Verify encoder parameter settings. Verify encoder adjustment.
761A Incorrect communication between module and encoder	Cause: Incorrect encoder wiring. Remedy: Verify encoder cable: wiring and shield connection.
761D Maximum velocity of the encoder is exceeded	Cause: Velocity too high for the encoder. In the case of BISS, the reason may also be a detected encoder communication error. Remedy:
762A Incremental encoder initialization failed	Cause: Encoder is not connected or the communication is disturbed, EMC. Remedy: Please check the cable connection. Please check the cable specifications, shield connection and EMC.
762B Incremental encoder initialization failed: The motor rotates when powered on	Cause: The motor rotates when the drive is powered on, which results in the failure of initial position identification. Remedy: Stop and perform the power-on again.
762C Motor velocity detected by incremental encoder exceeds maximum threshold	Cause: Encoder signal is disturbed, velocity is too high for the encoder. Remedy: Reduce encoder signal interference, verify shield connection. Reduce motor velocity.
A061 Position change in reference value for operating mode Electronic Gear too high	Cause: Position reference change is too high. Error detected at signal input for reference value. Remedy: Reduce the resolution of the master. Verify signal input for reference value signal.
A065 Parameter cannot be written	Cause: A data set is still active. Remedy: Wait until the currently active data set has been terminated.
A068 Offset positioning not possible	Cause: Operating mode Electronic Gear inactive or no gear method selected. Remedy: Start operating mode Electronic Gear and/or select a gear method.
A069 Setting the offset position is not possible	Cause: If offset positioning is active, it is not possible to set the position offset. Remedy: Wait until ongoing offset positioning has finished.
A06B Position deviation in operating mode Electronic Gear too high	Cause: The position deviation has become excessively high due to a velocity limitation or the release of direction. Remedy: Verify the velocity of the external reference values and the velocity limitation. Verify release of direction.
A300 Deceleration after HALT request still running	Cause: HALT was removed too soon. New command was sent before motor standstill was reached after a HALT request. Remedy: Wait for complete stop before removing HALT signal. Wait until motor has come to a complete standstill.
A301 Drive in operating state Quick Stop Active	Cause: Error with error class 1 detected. Drive stopped with Quick Stop. Remedy:
A302 Stop by positive limit switch	Cause: The positive limit switch was activated because movement range was exceeded, incorrect operation of limit switch or signal disturbance. Remedy: Verify application. Verify limit switch function and connection.
A303 Stop by negative limit switch	Cause: The negative limit switch was activated because movement range was exceeded, incorrect operation of limit switch or signal disturbance. Remedy: Verify application. Verify limit switch function and connection.
A306 Stop by user-initiated software stop	Cause: Drive is in operating state Quick Stop Active due to a software stop request. The activation of a new operating mode is not possible, the error code is sent as the response to the activation command. Remedy: Clear break condition with command Fault Reset.
A307 Interruption by internal software stop	Cause: In the operating modes Homing and Jog, the movement is internally interrupted by an internal software stop. The activation of a new operating mode is not possible. Remedy: Perform a Fault Reset.
A308 Drive is in operating state Fault or Fault Reaction Active	Cause: Error with error class 2 or higher detected. Remedy: Verify the error code (HMI or commissioning software), remove the cause and perform a Fault Reset.
A309 Drive not in operating state Operation Enabled	Cause: A command was sent that requires the drive to be in the operating state Operation Enabled (for example, a command to change the operating mode). Remedy: Set drive to operating state Operation Enabled and repeat the command.
A310 Power stage not enabled	Cause: Command cannot be used because the power stage is not enabled (operating state Operation Enabled or Quick Stop Active). Remedy: Set drive to an operating state in which the power stage is enabled, see state diagram.
A311 Operating mode change active	Cause: A start request for an operating mode has been received while a change of the operating mode was active. Remedy:
A313 Position overflow, zero point is therefore no longer valid	Cause: The movement range limits were exceeded and the zero point is no longer valid. An absolute movement requires a valid zero point. Remedy: Define a valid zero point by means of the operating mode Homing.
A317 Motor is not at a standstill	Cause: Command sent which is not permissible when the motor is not at a standstill. (e.g., Change of software limit switches, monitoring signals, reference point). Remedy: Wait until the motor has come to a standstill (x_end = 1).
A318 Operating mode active (x_end=0)	Cause: Activation of a new operating mode is not possible while another operating mode is still active. Remedy: Wait until the command in the operating mode has finished (x_end=1) or terminate active operating mode with HALT command.
A319 Manual tuning/Autotuning: Movement out of range	Cause: The movement exceeds the parameterized maximum movement range. Remedy: Verify permissible movement range value and time interval.
A31A Manual tuning/Autotuning: Amplitude/offset too high	Cause: Amplitude plus offset for tuning exceed internal velocity or current limitation. Remedy: Choose lower amplitude and offset values.
A31B Halt requested	Cause: Command not permissible while Halt is requested. Remedy: Clear Halt request and repeat command.
A31C Invalid position setting with software limit switch	Cause: Value for negative (positive) software limit switch is greater (less) than value for positive (negative) software limit switch. Remedy: Set correct position values.
A31D Velocity range exceeded parameter P4-07	Cause: The velocity was set to a value greater than the maximum permissible velocity in parameter P4-07 or current motor maximum velocity. Remedy: Reduce the velocity value.
A31E Stop by positive software limit switch	Cause: Not possible to execute command because positive software limit switch was triggered. Remedy: Return to the permissible movement range.
A31F Stop by negative software limit switch	Cause: Not possible to execute command because negative software limit switch was triggered. Remedy: Return to the permissible movement range.
A320 Permissible position deviation exceeded	Cause: External load or acceleration are too high. Remedy: Reduce external load or acceleration. Use a differently rated drive, if necessary. Error response can be adjusted via parameter P0-20.
A324 Error detected during homing	Cause: Homing movement was stopped in response to a detected error. Remedy: Possible sub-error codes: E A325, E A326, E A327, EA328 or E A329.
A325 Limit switch to be approached not enabled	Cause: Homing to positive limit switch or negative limit switch is disabled. Remedy: Enable limit switch via ‘IOsigLimP’ or ‘IOsigLimN’.
A326 Reference switch not found between positive limit switch and negative limit switch	Cause: Reference switch inoperative or not correctly connected. Remedy: Verify the function and wiring of the Reference switch.
A329 More than one signal positive limit switch/negative limit switch/reference switch active	Cause: Reference switch or limit switch not connected correctly or supply voltage for switches too low. Remedy: Verify the wiring and 24 VDC supply voltage.
A32A Positive limit switch triggered with negative direction of movement	Cause: Start reference movement with negative direction and activate the positive limit switch (switch in opposite direction of movement). Remedy: Verify correct connection and function of limit switch. Activate a jog movement with negative direction of movement.
A32B Negative limit switch triggered with positive direction of movement	Cause: Start reference movement with positive direction and activate the negative limit switch (switch in opposite direction of movement). Remedy: Verify correct connection and function of limit switch. Activate a jog movement with positive direction of movement.
A32C Reference switch error detected (switch signal briefly enabled or switch overtraveled)	Cause: Switch signal disturbance. Motor subjected to vibration or shock when stopped after activation of the switch signal. Remedy: Verify supply voltage, cabling and function of switch. Verify motor response after stopping and optimize control loop settings.
A32D Positive limit switch error detected (switch signal briefly enabled or switch overtraveled)	Cause: Switch signal disturbance. Motor subjected to vibration or shock when stopped after activation of the switch signal. Remedy: Verify supply voltage, cabling and function of switch. Verify motor response after stopping and optimize control loop settings.
A32E Negative limit switch error detected (switch signal briefly enabled or switch overtraveled)	Cause: Switch signal disturbance. Motor subjected to vibration or shock when stopped after activation of the switch signal. Remedy: Verify supply voltage, cabling and function of switch. Verify motor response after stopping and optimize control loop settings.
A32F Index pulse not found	Cause: Index pulse signal not connected or not working properly. Remedy: Verify index pulse signal and connection.
A330 Reference movement to index pulse cannot be Reproduced	Cause: The position difference between the index pulse and the switching point is insufficient. Remedy: Increase the distance between the index pulse and the switching point. If possible, the distance between the index pulse and the switching point should be a half motor revolution.
A332 Jog error detected (additional info = detailed error code)	Cause: Jog movement was stopped in response to a detected error. Remedy: For additional info, verify the detailed error code in the error memory.
A334 Timeout Standstill Window monitoring	Cause: Position deviation after movement greater than standstill window. This may have been caused by an external load. Remedy: Verify load. Verify settings for standstill window (parameter P6-15, P6-16 and P6-17). Optimize control loop settings.
A336 System error detected: Jerk limitation with position offset after end of movement	Cause: Remedy:
A338 Operating mode unavailable	Cause: The selected operating mode is not available. Remedy:
A33A No valid zero point (ref_ok=0)	Cause: No zero point defined by means of operating mode Homing. Zero point no longer valid due to movement beyond permissible movement range. Remedy: Use operating mode Homing to define a valid zero point. Use a motor with an absolute encoder.
A33C Function not available in this operating mode	Cause: Activation of a function which is not available in the active operating mode. Example: Start of backlash compensation while autotuning/manual tuning is active. Remedy:
A347 Permissible position deviation exceeded	Cause: External load or acceleration are too high. Remedy: Reduce external load or acceleration. Threshold value can be adjusted via the parameter P0-20.
A349 Position setting exceeds system limits	Cause: Position scaling of P5-01 and P5-02 results in a scaling factor that is too small. Remedy: Change P5-01 and P5-02 in such a way as to increase the resulting scaling factor.
A350 Change for jerk filter input position too great	Cause: Operating mode Electronic Gear with processing method ‘Position synchronization with compensation movement’ has been activated which resulted in a position change greater than 0.25 revolutions. Remedy: Deactivate jerk filter processing for Electronic Gear or use processing method ‘Position synchronization without compensation movement’.
A351 Function cannot be executed with this position scaling factor	Cause: The positions scaling factor is set to a value less than 1rev/131072usr_p, which is less than the internal resolution. Remedy: Use a different position scaling factor or deactivate the selected function.
A35C The triggered limit switch fails to move to the new reference position	Cause: The limit switch trigger signal holds, and the motor fails to move any more. Remedy: Remove the limit switch signal.
B100 RS485/Modbus: Indeterminable service	Cause: Unsupported Modbus service was received. Remedy: Verify application on the Modbus master.
B101 Incorrect I/O data configuration	Cause: The I/O data configuration or the Modbus I/O scanning configuration contains an invalid parameter. Remedy: Verify the configuration of the I/O data.
B200 RS485/Modbus: Protocol error detected	Cause: Logical protocol error detected: Incorrect length or unsupported subfunction. Remedy: Verify application on the Modbus master.
B201 RS485/Modbus: Interruption of the connection	Cause: Connection monitoring has detected an interruption of the connection. Remedy: Verify all connections and cables used for data exchange. Verify that the device is on.
B202 RS485/Modbus: Interruption of the connection	Cause: Connection monitoring has detected an interruption of the connection. Remedy: Verify all connections and cables used for data exchange. Verify that the device is on.
B203 RS485/Modbus: Incorrect number of monitor objects	Cause: Remedy:
C200 One of the MD index exceeds border	Cause: One of the MD index exceed border. Available MD index is between 0 … 47. Remedy: Please check script content.
C201 Error when loading script from EEPROM	Cause: Error when loading script from EEPROM. Remedy: Power-on servo drive again. Perform factory restore to device. Contact Technical Support or replace the device.
C202 No script available	Cause: No script available. Remedy: Download script to servo drive again. Contact Technical Support or replace the device.
C203 Script operation cycletime is exceeded	Cause: Too much script content, script can not be finished within cycletime defined in parameter P7-00. Remedy: Increase value of parameter P7-00 or set P7-00 to 0.
C204 Insufficient RAM when saving script to EEPROM	Cause: Insufficient RAM when saving script to EEPROM. Remedy: Try to simplify script content. Contact Technical Support or replace the device.
C205 Illegal operation of divided by 0 found in script	Cause: Illegal operation of divided by 0 found in script. Remedy: Check script content.
C206 One of the timer base exceeds border	Cause: One of the timer base exceeds border. Available timer base is between 1 … 20000 ms. Remedy: Check script content.
Exxx User defined error in DYC mode	Cause: Remedy: