Schneider Lexium LXM05 Drive Fault Codes

Complete reference list of Schneider Lexium 05 (LXM05) servo drive fault codes. Learn to troubleshoot legacy E-codes like E100 (Overcurrent), E205 (Encoder), and E300.

Schneider LXM05 Fault Codes Reference Table

Schneider LXM05 Fault Codes Reference Table

Schneider LXM05 Fault Codes Reference Table

Fault Code and Meaning Cause and Remedy
E 1100
Parameter out of permissible range		 Cause: Value entered is outside the valid range.

Remedy:
Check the parameter value and permissible range.
E 1101
Parameter does not exist		 Cause: Fault signaled by parameter management: parameter (index) does not exist.

Remedy:
Check parameter index.
E 1102
Parameter does not exist		 Cause: Fault signaled by parameter management: parameter (subindex) does not exist.

Remedy:
Check parameter subindex.
E 1103
Parameter write not permissible (READ only)		 Cause: Write access attempted to a read-only parameter.

Remedy:
Do not attempt to write to this parameter.
E 1104
Write access denied (no access authorisation)		 Cause: Parameter only accessible at expert level.

Remedy:
The write access level expert is required.
E 1106
Command not allowed while power amplifier is active		 Cause: Command not allowed while the power amplifier is enabled (status "OperationEnable" or "QuickStopActive").

Remedy:
Disable the power amplifier and repeat the command.
E 1107
Access via other interface blocked		 Cause: Access occupied by another channel (e.g.: commissioning tool is active and fieldbus access was tried at the same time).

Remedy:
Check the channel that blocks the access.
E 110B
Initialisation error (additional info=Modbus register address)		 Cause: Error detected at power enable parameter check e.g. reference speed value for profile position is greater than max. allowed speed of drive. Value in additional error info shows the Modbus register address of the parameter where the initialisation error was detected.

Remedy:
Check parameters associated with the specific Modbus address provided.
E 110D
Basic configuration of controller required after factory setting		 Cause: The "First Setup" (FSU) was not run at all or not completed.

Remedy:
Run the First Setup (FSU).
E 110E
Parameter changed that requires a restart of the drive		 Cause: Only displayed by the commissioning tool. A parameter modification requires the drive to be switched off and on.

Remedy:
  • Restart the drive to activate the parameter functionality.
  • Check the parameter chapter for the parameter that required a restart of the drive.
E 1300
Power Removal activated (PWRR_A, PWRR_B)		 Cause: The "Power Removal" safety function was activated in "Operation enable" status.

Remedy:
Reset the fault; check the wiring of the PWRR inputs.
E 1301
PWRR_A and PWRR_B different level		 Cause: The levels of the input PWRR_A or PWRR_B were different for more than 1 second.

Remedy:
The drive has to be switched off and the reason fixed (e.g.: check emergency stop active) before it is switched on.
E 1310
Reference signal frequency too high		 Cause: The frequency of the pulse signal (A/B, Pulse/Direction, CW/CCW) is higher than the allowed value.

Remedy:
Adapt the output pulse frequency of the controller to fit the input specification of the drive. Take care to also adapt the electronic gear ratio for the application requirements (position accuracy and speed).
E 1311
The selected input or output function cannot be configured		 Cause: The function configured for an Input or Output cannot be used in the selected mode (e.g. enable positive movement input function cannot be configured in jog mode).

Remedy:
Check IO configuration against selected operating mode.
E 1312
Limit or reference switch signal in I/O functions not defined		 Cause: Reference movements require limit switches. These limit switches are not assigned to inputs.

Remedy:
Assign the LIMP, LIMN and ref functions to the inputs.
E 160C
Autotuning: moment of inertia outside permissible range		 Cause: The load inertia is too high.

Remedy:
Check load inertia.
E 160D
Autotuning failed: oscillation is too high		 Cause: The value of parameter 'AT_n_tolerance' may be too low for the identified mechanical system.

Remedy:
Check mechanical system and tolerance settings.
E 160F
Autotuning: power amplifier cannot be enabled		 Cause: Autotuning was started in "Fault" status.

Remedy:
Clear faults before starting Autotuning.
E 1610
Autotuning: processing discontinued		 Cause: DC bus undervoltage, LIMP, LIMN, Stop button at remote terminal pressed, ..., but NOT caused by Autotuning process.

Remedy:
Check external interruption sources.
E 1611
System error: Autotuning internal write access		 Cause: HALT is active and an Autotuning parameter is written. Occurs when Autotuning is started.

Remedy:
Deactivate HALT before starting.
E 1613
Autotuning: max. permissible positioning range exceeded		 Cause: The motor exceeded the adjusted position range during Autotuning.

Remedy:
Monitoring can be turned off by setting 'AT_DIS' = 0.
E 1614
Autotuning: already active		 Cause: Autotuning has been started twice simultaneously OR an Autotuning parameter is modified during Autotuning ('AT_dis' and 'AT_dir').

Remedy:
Wait for current Autotuning process to complete.
E 1615
Autotuning: parameter cannot be changed while active		 Cause: 'AT_gain' or 'AT_J' are written during Autotuning.

Remedy:
Wait for Autotuning to finish before writing parameters.
E 1616
Autotuning: static friction for selected speed jump height too high		 Cause: 'AT_n_ref' is too great regarding actual friction.

Remedy:
Reduce 'AT_n_ref' or friction.
E 1617
Autotuning: friction torque or load torque too great		 Cause: The current limit has been reached ('CTRL_i_max').

Remedy:
Check load torque and current limits.
E 1618
Autotuning: optimisation aborted		 Cause: The internal Autotuning sequence has not been finished (following error?).

Remedy:
Check for following errors.
E 1619
Autotuning: speed jump height too small		 Cause: 'AT_n_ref' is too small compared to 'AT_n_tolerance'.

Remedy:
Modify 'AT_n_ref' and/or 'AT_n_tolerance' to meet the desired condition.
E 1620
Autotuning: load torque too high		 Cause: Product dimensioning is not suitable for the machine load. Detected machine inertia is too high compared to the inertia of the motor.

Remedy:
Reduce load, check dimensioning.
E 1A01
Motor has been changed		 Cause: Detected motor type is different from previously detected motor.

Remedy:
Confirm the motor change.
E 1A02
Motor has been changed		 Cause: The motor type is the same, but the motor data structure has changed.

Remedy:
Confirm the motor change.
E 1B04
ESIM resolution too high with selected 'n_max'		 Cause: ESIM resolution conflict.

Remedy:
Reduce the ESIM resolution or the maximum speed 'CTRL_n_max'.
E 2300
Power amplifier overcurrent		 Cause: Motor short circuit and deactivation of the power amplifier.

Remedy:
Check the motor power connection.
E 2301
Braking resistor overcurrent		 Cause: Braking resistor short circuit.

Remedy:
Check braking resistor wiring.
E 3100
Mains power supply phase fault		 Cause: Missing phase(s) for more than 50ms.

Remedy:
Check mains power supply.
E 3200
DC bus overvoltage		 Cause: Energy recovery during braking too high.

Remedy:
Check deceleration ramp, check dimensioning of drive and braking resistor.
E 3201
DC bus undervoltage (switch-off threshold)		 Cause: Power supply loss, poor power supply.

Remedy:
Check power supply.
E 3202
DC bus undervoltage (Quick Stop threshold)		 Cause: Power supply loss, poor power supply.

Remedy:
Check power supply.
E 3203
Motor encoder supply voltage		 Cause: Encoder power supply voltage is not consistent because of a hardware problem.

Remedy:
Replace the device.
E 3206
DC bus undervoltage, no mains phase (warning)		 Cause: Power supply loss, poor power supply.

Remedy:
Check power supply.
E 4100
Power amplifier overtemperature		 Cause: Transistors overtemperature: ambient temperature is too high, fan is faulty, dust.

Remedy:
Remove the protective foil, improve the heat dissipation in the cabinet.
E 4101
Warning power amplifier overtemperature		 Cause: Transistors overtemperature: ambient temperature is too high, fan is faulty, dust.

Remedy:
Remove the protective foil, improve the heat dissipation in the cabinet.
E 4102
Power amplifier overload (I2t) warning		 Cause: The current has exceeded the nominal value for an extended period of time.

Remedy:
Check dimensioning, reduce cycle time.
E 4200
Device overtemperature		 Cause: Control board overtemperature: ambient temperature is too high.

Remedy:
Check cabinet ventilation.
E 4300
Motor overtemperature		 Cause: Resistance of thermal sensor is too high; overload, ambient temp (see I2t); faulty encoder cable.

Remedy:
Check motor installation: the heat must be dissipated via the mounting surface. Check encoder cable.
E 4301
Warning motor overtemperature		 Cause: Resistance of thermal sensor is too high; overload, ambient temp (see I2t).

Remedy:
Check motor installation: the heat must be dissipated via the mounting surface.
E 4302
Motor overload (I2t) warning		 Cause: The current has exceeded the nominal value for an extended period of time.

Remedy:
Check load and duty cycle.
E 4402
Braking resistor overload (I2t) warning		 Cause: The braking resistor is switched on for an excessively long period of time.

Remedy:
Check braking usage and dimensioning.
E 5200
Fault in connection to motor encoder		 Cause: Communication has not been established: encoder cable is faulty or not connected, EMC.

Remedy:
Check the cable connection, shield.
E 5201
Errors in motor encoder communication		 Cause: Encoder error message: communication error detected by the encoder itself.

Remedy:
Check encoder and cable.
E 5202
Motor encoder is not supported		 Cause: Incompatible encoder type is connected.

Remedy:
Connect a supported encoder.
E 5204
Connection to motor encoder lost		 Cause: Encoder cable problems (communication has been interrupted).

Remedy:
Check the cable connection.
E 5206
Communication error in encoder		 Cause: Communication disturbed, EMC.

Remedy:
Check the connection, check the shielding on the EMC plate.
E 5600
Motor connection phase fault		 Cause: Motor phase(s) are not connected.

Remedy:
Check connection of motor phases.
E 5601
Interruption or faulty encoder signals		 Cause: Encoder is not correctly connected (SinCos analogue signals are missing).

Remedy:
Check encoder connection.
E 5602
Interruption or faulty encoder signals		 Cause: Encoder is not correctly connected (SinCos analogue signals are missing).

Remedy:
Check encoder connection.
E 5603
Commutation error		 Cause: Motor phases are inverted; EMC; the load torque is greater than the motor torque; wrong motor data into the encoder EEPROM (encoder phase offset is wrong).

Remedy:
Resize the motor so it can withstand the load torque; check motor data; contact technical support.
E 610D
Error in selection parameter		 Cause: Wrong parameter value selected.

Remedy:
Check the value to be written.
E 7100
System error: invalid power amplifier data		 Cause: Amplifier data stored in device is corrupt (wrong CRC), error in internal memory data.

Remedy:
Contact technical support or replace the device.
E 7120
Invalid motor data		 Cause: Motor data are corrupt (wrong CRC).

Remedy:
Contact technical support or replace the motor.
E 7121
System error: errors in motor encoder communication		 Cause: EMC, detailed information is included in the fault buffer that contains the error code of the encoder.

Remedy:
Contact technical support.
E 7122
Invalid motor data		 Cause: Motor data stored in motor encoder is corrupt, error in internal memory data.

Remedy:
Contact technical support or replace the motor.
E 7123
Motor current offset outside permissible range		 Cause: Motor current measurement circuit is defective.

Remedy:
Contact technical support or replace the device.
E 7124
System error: motor encoder faulty		 Cause: Encoder signals internal fault.

Remedy:
Contact technical support or replace the motor.
E 7328
Motor encoder sends: position capture errors		 Cause: Encoder signals internal position capturing fault.

Remedy:
Contact technical support or replace the motor.
E 7329
Motor encoder sends: Warning		 Cause: EMC, encoder signals internal warning.

Remedy:
Contact technical support or replace the motor.
E 7336
Offset with SinCos drift compensation too high		 Cause: HiFa analogue signal offset during calibration procedure is out of range.

Remedy:
Check encoder connection, replace device / motor.
E 7338
No valid motor absolute position		 Cause: Warning to inform you that absolute position has not not yet been determined.

Remedy:
Depending on application, fix the absolute position. Device still usable and all functions are OKAY.
E 7500
RS485/Modbus: overrun error		 Cause: EMC; cabling problem.

Remedy:
Check cables.
E 7501
RS485/Modbus: framing error		 Cause: EMC; cabling problem.

Remedy:
Check cables.
E 7502
RS485/Modbus: parity error		 Cause: EMC; cabling problem.

Remedy:
Check cables.
E 7503
RS485/Modbus: receive error		 Cause: EMC; cabling problem.

Remedy:
Check cables.
E 8110
CANopen: CAN overflow (message lost)		 Cause: Two short CAN messages have been sent too fast (at 1MBits only).

Remedy:
Check CAN bus timing.
E 8120
CANopen: CAN Controller in Error Passive		 Cause: Too many error frames have been detected.

Remedy:
Check CAN bus installation.
E 8130
CANopen: Heartbeat or Life Guard error		 Cause: The bus cycle time of the CANopen master is higher than the programmed heartbeat or nodeguard time.

Remedy:
Check CANopen configuration, increase heartbeat or nodeguard time.
E 8141
CANopen: CAN Controller in Busoff		 Cause: Too many error frames have been detected, CAN devices with different baudrates.

Remedy:
Check CAN bus installation.
E 8201
CANopen: RxPDO1 could not be processed		 Cause: Error while processing Receive PDO1: PDO1 contains invalid value.

Remedy:
Check RxPDO1 content (application).
E 8202
CANopen: RxPDO2 could not be processed		 Cause: Error while processing Receive PDO2: PDO2 contains invalid value.

Remedy:
Check RxPDO2 content (application).
E 8203
CANopen: RxPDO3 could not be processed		 Cause: Error while processing Receive PDO3: PDO3 contains invalid value.

Remedy:
Check RxPDO3 content (application).
E 8204
CANopen: RxPDO4 could not be processed		 Cause: Error while processing Receive PDO4: PDO4 contains invalid value.

Remedy:
Check RxPDO4 content (application).
E A060
Calculated speed in electronic gear/pulse control too high		 Cause: Gear ratio or speed reference value too high.

Remedy:
Reduce the gear ratio or speed reference value.
E A061
Position change in reference value with electronic gear/pulse control too high		 Cause: Position reference change is too high. Reference value input signal disturbance.

Remedy:
  • Reduce the resolution of the master.
  • Check reference value input signal.
E A300
Braking procedure after HALT request still active		 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.
E A301
Drive in status "Quick Stop active"		 Cause: Error with error class 1 occurred. Drive stopped with Quick Stop command.

Remedy:
  • Check for previous errors.
  • Acknowledge/Reset the Quick Stop condition.
E A302
Interruption by LIMP		 Cause: LIMP was activated because working range was exceeded, malfunction of limit switch or signal disturbance.

Remedy:
  • Check application.
  • Check limit switch function and connection.
E A303
Interruption by LIMN		 Cause: LIMN was activated because working range was exceeded, malfunction of limit switch or signal disturbance.

Remedy:
  • Check application.
  • Check limit switch function and connection.
E A305
Power amplifier cannot be activated in the current operating status		 Cause: Fieldbus: trying to enable the amplifier in status "Not ready to switch on".

Remedy:
  • Refer to the status diagram in the operation chapter of the manual.
E A306
Interruption by user-initiated software stop		 Cause: Drive is in status "Quick Stop active" due to a software stop request. The activation of a new operating mode is not possible.

Remedy:
  • Clear break condition with command Fault Reset.
E A307
Interruption by internal software stop		 Cause: In homing and jog modes, the movement is internally interrupted using an internal software stop.

Remedy:
  • Clear break condition with command Fault Reset.
E A308
Drive in "Fault" status		 Cause: Error with error class 2 or higher occurred.

Remedy:
  • Check error code (HMI or PS2).
  • Remove error condition and clear error status with command Fault Reset.
E A309
Drive not in status "Operation Enable"		 Cause: A command which requires the status "Operation enable" was sent (e.g.: opmode change).

Remedy:
  • Set drive to status "OperationEnable" and repeat the command.
E A310
Power amplifier not active		 Cause: Command is not possible because the power amplifier is not enabled (status "Operation Enabled" or "Quick Stop").

Remedy:
  • Set drive to a status with the amplifier enabled.
  • Refer to the status diagram in the operation chapter of the manual.
E A313
Position overrun, reference point no longer defined		 Cause: The position range limits were exceeded which resulted in a loss of the reference point.

Remedy:
  • Define a new reference point by means of homing mode.
E A314
No reference position		 Cause: Command needs a defined reference point (ref_ok=1).

Remedy:
  • Define a new reference point by means of homing mode.
E A315
Homing active		 Cause: Command not possible if homing status is active.

Remedy:
  • Wait until homing movement is finished.
E A317
Drive is not at standstill		 Cause: Command sent which is not allowed while the motor is not in standstill (e.g., change of softwarelimits, teach in data).

Remedy:
  • Wait until drive has come to a standstill (x_end = 1).
E A318
Operating mode active		 Cause: Activation of a new operating mode is not possible while the current operating mode is still active.

Remedy:
  • Wait until the command in the operating mode has finished (x_end=1).
  • Or terminate current operating mode with HALT command.
E A319
Manual/Autotuning: distance range overflow		 Cause: The motor exceeds the parameterised limit ('MT_dismax') of manual tuning.

Remedy:
  • Check reference value and time interval for manual tuning.
E A31A
Manual/Autotuning: amplitude/offset set too high		 Cause: Amplitude plus offset for tuning exceed internal speed or current limitation.

Remedy:
  • Choose lower amplitude and offset values.
E A31B
HALT requested		 Cause: Command not allowed while a HALT is requested.

Remedy:
  • Clear HALT request and repeat command.
E A31C
Invalid position setting with software limit switch		 Cause: Value for negative/positive software limit is incorrect. Homing position value is set outside the range of the software limits.

Remedy:
  • Set correct position values.
E A31D
Speed range overflow ('CTRL_n_max')		 Cause: The reference speed value was set to a value greater than the max. speed defined in 'CTRL_n_max'.

Remedy:
  • Increase the value of 'CTRL_n_max'.
  • Or reduce the reference speed value.
E A31E
Interruption by positive software limit switch		 Cause: Command not possible because of overrun of positive software limit switch.

Remedy:
  • Move back to software limit range by means of manual movement.
E A31F
Interruption by negative software limit switch		 Cause: Command not possible because of overrun of negative software limit switch.

Remedy:
  • Move back to software limit range by means of manual movement.
E A320
Position tracking error		 Cause: External load or acceleration are too high.

Remedy:
  • Reduce external load or acceleration.
  • Error response is adjustable via 'Flt_pDiff'.
E A321
RS422 position interface is not defined as input signal		 Cause: RS422 interface is defined as output (e.g. ESIM) at start of electronic gear mode.

Remedy:
  • Define RS422 interface as input via 'IOposInterfac' parameter.
E A324
Error during homing		 Cause: Homing movement was stopped by an error. See additional info in error buffer (Sub-codes: EA325-EA329).

Remedy:
  • Check detailed reason in the error buffer.
E A325
Limit switch to be approached not enabled		 Cause: Homing to LIMP or LIMN and limit switches are disabled.

Remedy:
  • Enable limit switch via 'IOsigLimP' or 'IOsigLimN'.
E A326
REF switch not found between LIMP and LIMN		 Cause: REF input switch defective or not correctly connected.

Remedy:
  • Check the function and wiring of the REF switch.
E A327
Reference movement to REF without direction reversal		 Cause: Improper enabling of limit switch LIM. Search of REF without direction reversal in positive (negative) direction with LIMP (LIMN) activated.

Remedy:
  • Check the function and wiring of the LIMP (LIMN) switch.
E A328
Overrun of LIM or REF not permissible		 Cause: Search of REF without direction reversal and REF or LIM overrun.

Remedy:
  • Reduce homing speed ('HMn') or increase deceleration ('RAMPdecel').
  • Check the function and wiring of LIMP, LIMN and REF switch.
E A329
More than one signal LIMP/LIMN/REF active		 Cause: REF or LIM not connected correctly or supply voltage for switches too low.

Remedy:
  • Check the wiring and 24VDC supply voltage.
E A32A
Ext. monitoring signal LIMP with neg. direction of rotation		 Cause: Start reference movement with neg. direction of rotation and activate the LIMP switch.

Remedy:
  • Check correct connection and function of limit switch.
  • Activate a jog movement with negative direction of rotation (target limit switch must be connected to the inputs LIMN).
E A32B
Ext. monitoring signal LIMN with pos. direction of rotation		 Cause: Start reference movement with pos. direction of rotation and activate the LIMN switch.

Remedy:
  • Check correct connection and function of limit switch.
  • Activate a jog movement with positive rotation (target limit switch must be connected to the inputs LIMP).
E A32C
Error with REF (switch signal briefly enabled or switch overrun)		 Cause: Switch signal disturbance. Motor subjected to vibration or shock when stopped.

Remedy:
  • Check supply voltage, cabling and function of switch.
  • Check motor reaction after stopping and optimise controller settings.
E A32D
Error with LIMP (switch signal briefly enabled or switch overrun)		 Cause: Switch signal disturbance. Motor subjected to vibration or shock when stopped.

Remedy:
  • Check supply voltage, cabling and function of switch.
  • Check motor reaction after stopping and optimise controller settings.
E A32E
Error with LIMN (switch signal briefly enabled or switch overrun)		 Cause: Switch signal disturbance. Motor subjected to vibration or shock when stopped.

Remedy:
  • Check supply voltage, cabling and function of switch.
  • Check motor reaction after stopping and optimise controller settings.
E A330
Reproducibility of the index pulse movement uncertain		 Cause: Index pulse too close to the switch. The position difference between the change of the switch signal and the occurrence of the index pulse is too low.

Remedy:
  • Change mounting point of limit switch (optim. to the point at half a motor revolution away from the current mechanical position).
E A332
Error with jog (additional info = detailed error number)		 Cause: Jog movement was stopped by error.

Remedy:
  • For additional info, check the detailed error number in the error buffer.
E A334
Timeout at Standstill window monitor		 Cause: Position deviation after movement finished greater than standstill window, e.g. caused by an external load.

Remedy:
  • Check load.
  • Check settings for standstill window ('STANDp_win', 'STANDpwinTime' and 'STANDpwinTout').
  • Optimise controller settings.
E A335
Processing only possible in fieldbus mode		 Cause: Reference movement started in IODevice ('DEVcmdinterf' is not set to fieldbus device).

Remedy:
  • 'DEVcmdinterf' must be set to fieldbus device.
E A337
Operating mode cannot be continued		 Cause: Continuation of interrupted movement in profile position mode is not possible because another mode had been active in the meantime.

Remedy:
  • Restart the operating mode.
E A33A
Reference point is not defined (ref_ok=0)		 Cause: No homing done and no motor with absolute encoder connected. Homing position lost because the working position range was left.

Remedy:
  • Start homing.
  • Use motor with multiturn encoder if no homing is to be done.
E A33C
Function not available in current operating mode		 Cause: Activation of a function which is not available in the current operating mode.

Remedy:
  • Check compatibility of function and operating mode.
E A33D
Motion blend is already active		 Cause: Change of motion blend during the current motion blend (end position of motion blend not yet reached).

Remedy:
  • Wait for the motion blend to complete before setting the next position.
E A33E
No movement activated		 Cause: Activation of a motion blend without movement.

Remedy:
  • Start a movement before the motion blend is activated.
E A33F
Position motion blend movement not in the range of the active movement		 Cause: The position of the motion blend is outside of the current movement range.

Remedy:
  • Check the position of the motion blend and the current movement range.
E A340
Error in motion sequence mode		 Cause: The operating mode motion sequence was stopped by an error.

Remedy:
  • Check the error buffer for details on the error.
  • Verify the error by checking the additional error information.
E A341
Position of motion blend has already been passed		 Cause: The current movement has passed beyond the position of the motion blend.

Remedy:
  • Adjust timing or position parameters.
E A342
Reference velocity was not reached on switch point of motion blend		 Cause: The position of the motion blend was overrun, the reference velocity was not reached.

Remedy:
  • Reduce the ramp setting to ensure that the reference velocity is reached at the position of the motion blend.
E B100
RS485/Modbus: unknown service		 Cause: Unsupported Modbus service was received.

Remedy:
  • Check application on the Modbus master.
E B200
RS485/Modbus: Protocol error		 Cause: Logical protocol error: wrong length or unsupported subfunction.

Remedy:
  • Check application on the Modbus master.
E B201
RS485/Modbus: Nodeguard error		 Cause: Connection monitoring parameter ('MBnode_guard') is <>0ms and a nodeguard event was detected.

Remedy:
  • Check application on the Modbus master.
  • Or change (set to 0ms or increase the parameter 'MBnode_guard' monitoring time).
E B202
RS485/Modbus: Nodeguard warning		 Cause: Connection monitoring parameter ('MBnode_guard') is <>0ms and a nodeguard event was detected.

Remedy:
  • Check application on the Modbus master.
  • Or change (set to 0ms or increase the parameter 'MBnode_guard' monitoring time).
E B400
CANopen: NMT reset with power amplifier active		 Cause: NMT Reset command is received while drive is in status "Enable".

Remedy:
  • Always disable the drive before sending a NMT reset command.
E B401
CANopen: NMT reset with power amplifier active		 Cause: NMT Stop command is received while drive is in status "Enable".

Remedy:
  • Always disable the drive before sending a NMT Stop command.
E B403
Excessive Sync period deviation from ideal value		 Cause: The period time of the SYNC signals is not stable. The deviation is more than 100usec.

Remedy:
  • The SYNC signals of the motion controller (CANsync master) must be more accurate.
E B404
Sync signal failed		 Cause: SYNC signal was missing too often (more than twice).

Remedy:
  • Check CAN connection.
  • Check motion controller (CANsync master).
E B407
Drive is not synchronous with master cycle		 Cause: The cyclic synchronous operating mode cannot be activated while the drive is not synchronised.

Remedy:
  • Check motion controller (CANsync master).
  • To be synchronised, the motion controller (CANsync master) must cyclically send SYNC signals.
E 1100

Parameter out of permissible range		 Cause:
The parameter value entered is outside of the defined limits.

Remedy:
Check the permissible range of the parameter and adjust the value.
E 1101

Parameter does not exist		 Cause:
Fault signaled by parameter management: parameter (index) does not exist.

Remedy:
Check the parameter index being accessed.
E 1102

Parameter does not exist		 Cause:
Fault signaled by parameter management: parameter (subindex) does not exist.

Remedy:
Check the parameter subindex being accessed.
E 1103

Parameter write not permissible (READ only)		 Cause:
Write access was attempted on a read-only parameter.

Remedy:
Do not attempt to write to this parameter.
E 1104

Write access denied (no access authorisation)		 Cause:
Parameter only accessible at expert level. The write access level expert is required.

Remedy:
Change the access level/authorisation to expert.
E 1106

Command not allowed while power amplifier is active		 Cause:
Command not allowed while the power amplifier is enabled (status "OperationEnable" or "QuickStopActive").

Remedy:
Disable the power amplifier and repeat the command.
E 1107

Access via other interface blocked		 Cause:
Access occupied by another channel (e.g.: commissioning tool is active and fieldbus access was tried at the same time).

Remedy:
Check the channel that blocks the access.
E 110B

Initialisation error (additional info=Modbus register address)		 Cause:
Error detected at power enable parameter check e.g. reference speed value for profile position is greater than max. allowed speed of drive. Value in additional error info shows the Modbus register address where the error was detected.

Remedy:
Check the parameter values indicated by the additional info.
E 110D

Basic configuration of controller required after factory setting		 Cause:
The "First Setup" (FSU) was not run at all or not completed.

Remedy:
Perform and complete the "First Setup".
E 110E

Parameter changed that requires a restart of the drive		 Cause:
A parameter modification requires the drive to be switched off and on (Only displayed by commissioning tool).

Remedy:
  • Restart the drive to activate the parameter functionality.
  • Check the parameter chapter for the parameter that required a restart.
E 1300

Power Removal activated (PWRR_A, PWRR_B)		 Cause:
The "Power Removal" safety function was activated in "Operation enable" status.

Remedy:
Reset the fault; check the wiring of the PWRR inputs.
E 1301

PWRR_A and PWRR_B different level		 Cause:
The levels of the input PWRR_A or PWRR_B were different for more than 1 second.

Remedy:
The drive has to be switched off and the reason fixed (e.g.: check emergency stop active) before it is switched on.
E 1310

Reference signal frequency too high		 Cause:
The frequency of the pulse signal (A/B, Pulse/Direction, CW/CCW) is higher than the allowed value.

Remedy:
Adapt the output pulse frequency of the controller to fit the input specification. Adapt electronic gear ratio for application requirements.
E 1311

The selected input or output function cannot be configured		 Cause:
The function configured for an Input or Output cannot be used in the selected mode (e.g. enable positive movement input function cannot be configured in jog mode).

Remedy:
Check configuration of IO vs Operation Mode.
E 1312

Limit or reference switch signal in I/O functions not defined		 Cause:
Reference movements require limit switches. These limit switches are not assigned to inputs.

Remedy:
Assign the LIMP, LIMN and ref functions to the inputs.
E 160C

Autotuning: moment of inertia outside permissible range		 Cause:
The load inertia is too high.

Remedy:
Reduce load inertia or check drive sizing.
E 160D

Autotuning: oscillation is too high		 Cause:
The value of parameter 'AT_n_tolerance' may be too low for the identified mechanical system. First steps of Autotuning failed.

Remedy:
Adjust 'AT_n_tolerance' or mechanical system.
E 160F

Autotuning: power amplifier cannot be enabled		 Cause:
Autotuning was started in "Fault" status.

Remedy:
Clear faults before starting Autotuning.
E 1610

Autotuning: processing discontinued		 Cause:
DC bus undervoltage, LIMP, LIMN, Stop button at remote terminal pressed, etc., but NOT caused by Autotuning process.

Remedy:
Check external stop conditions and power supply.
E 1611

System error: Autotuning internal write access		 Cause:
HALT is active and an Autotuning parameter is written. Occurs when Autotuning is started.

Remedy:
Deactivate HALT before Autotuning.
E 1613

Autotuning: max. permissible positioning range exceeded		 Cause:
The motor exceeded the adjusted position range during Autotuning.

Remedy:
Monitoring can be turned off by setting 'AT_DIS' = 0.
E 1614

Autotuning: already active		 Cause:
Autotuning has been started twice simultaneously OR an Autotuning parameter is modified during Autotuning ('AT_dis' and 'AT_dir').

Remedy:
Wait for current Autotuning to finish.
E 1615

Autotuning: parameter cannot be changed while active		 Cause:
'AT_gain' or 'AT_J' are written during Autotuning.

Remedy:
Do not write these parameters during Autotuning.
E 1616

Autotuning: static friction too high		 Cause:
Static friction for selected speed jump height 'AT_n_ref' too high. 'AT_n_ref' is too great regarding actual friction.

Remedy:
Reduce 'AT_n_ref' or friction.
E 1617

Autotuning: friction torque or load torque too great		 Cause:
The current limit has been reached ('CTRL_i_max').

Remedy:
Check load torque and current limits.
E 1618

Autotuning: optimisation aborted		 Cause:
The internal Autotuning sequence has not been finished (following error?).

Remedy:
Check for following errors or mechanical issues.
E 1619

Autotuning: speed jump height too small		 Cause:
'AT_n_ref' is too small compared to 'AT_n_tolerance'.

Remedy:
Modify 'AT_n_ref' and/or 'AT_n_tolerance' to meet the desired condition.
E 1620

Autotuning: load torque too high		 Cause:
Product dimensioning is not suitable for the machine load. Detected machine inertia is too high compared to the inertia of the motor.

Remedy:
Reduce load, check dimensioning.
E 1A01

Motor has been changed		 Cause:
Detected motor type is different from previously detected motor.

Remedy:
Confirm the motor change.
E 1A02

Motor has been changed		 Cause:
The motor type is the same, but the motor data structure has changed.

Remedy:
Confirm the motor change.
E 1B04

ESIM resolution too high with selected 'n_max'		 Cause:
ESIM resolution configuration conflict.

Remedy:
Reduce the ESIM resolution or the maximum speed 'CTRL_n_max'.
E 2300

Power amplifier overcurrent		 Cause:
Motor short circuit and deactivation of the power amplifier.

Remedy:
Check the motor power connection.
E 2301

Braking resistor overcurrent		 Cause:
Braking resistor short circuit.

Remedy:
Check braking resistor wiring and condition.
E 3100

Mains power supply phase fault		 Cause:
Missing phase(s) for more than 50ms.

Remedy:
Check mains power supply and fuses.
E 3200

DC bus overvoltage		 Cause:
Energy recovery during braking too high.

Remedy:
Check deceleration ramp, check dimensioning of drive and braking resistor.
E 3201

DC bus undervoltage (switch-off threshold)		 Cause:
Power supply loss, poor power supply.

Remedy:
Check input power supply voltage.
E 3202

DC bus undervoltage (Quick Stop threshold)		 Cause:
Power supply loss, poor power supply.

Remedy:
Check input power supply voltage.
E 3203

Motor encoder supply voltage		 Cause:
Encoder power supply voltage is not consistent because of a hardware problem.

Remedy:
Replace the device.
E 3206

DC bus undervoltage, no mains phase (warning)		 Cause:
Power supply loss, poor power supply.

Remedy:
Check input power supply.
E 4100

Power amplifier overtemperature		 Cause:
Transistors overtemperature: ambient temperature is too high, fan is faulty, dust.

Remedy:
Remove the protective foil, improve the heat dissipation in the cabinet.
E 4101

Warning power amplifier overtemperature		 Cause:
Transistors overtemperature: ambient temperature is too high, fan is faulty, dust.

Remedy:
Remove the protective foil, improve the heat dissipation in the cabinet.
E 4102

Power amplifier overload (I2t) warning		 Cause:
The current has exceeded the nominal value for an extended period of time.

Remedy:
Check dimensioning, reduce cycle time.
E 4200

Device overtemperature		 Cause:
Control board overtemperature: ambient temperature is too high.

Remedy:
Check cabinet cooling/ventilation.
E 4300

Motor overtemperature		 Cause:
Resistance of thermal sensor is too high; overload, ambient temp (see I2t); faulty encoder cable.

Remedy:
Check motor installation: the heat must be dissipated via the mounting surface. Check encoder cable.
E 4301

Warning motor overtemperature		 Cause:
Resistance of thermal sensor is too high; overload, ambient temp (see I2t).

Remedy:
Check motor installation: the heat must be dissipated via the mounting surface.
E 4302

Motor overload (I2t) warning		 Cause:
The current has exceeded the nominal value for an extended period of time.

Remedy:
Check dimensioning, reduce cycle time.
E 4402

Braking resistor overload (I2t) warning		 Cause:
The braking resistor is switched on for an excessively long period of time.

Remedy:
Check braking requirements and resistor sizing.
E 5200

Fault in connection to motor encoder		 Cause:
Communication has not been established: encoder cable is faulty or not connected, EMC.

Remedy:
Check the cable connection, shield.
E 5201

Errors in motor encoder communication		 Cause:
Encoder error message: communication error detected by the encoder itself.

Remedy:
Check encoder and cable.
E 5202

Motor encoder is not supported		 Cause:
Incompatible encoder type is connected.

Remedy:
Check connected motor/encoder type.
E 5204

Connection to motor encoder lost		 Cause:
Encoder cable problems (communication has been interrupted).

Remedy:
Check the cable connection.
E 5206

Communication error in encoder		 Cause:
Communication disturbed, EMC.

Remedy:
Check the connection, check the shielding on the EMC plate.
E 5600

Motor connection phase fault		 Cause:
Motor phase(s) are not connected.

Remedy:
Check connection of motor phases.
E 5601

Interruption or faulty encoder signals		 Cause:
Encoder is not correctly connected (SinCos analogue signals are missing).

Remedy:
Check encoder connection.
E 5602

Interruption or faulty encoder signals		 Cause:
Encoder is not correctly connected (SinCos analogue signals are missing).

Remedy:
Check encoder connection.
E 5603

Commutation error		 Cause:
Motor phases are inverted; EMC; the load torque is greater than the motor torque; wrong motor data into the encoder EEPROM (encoder phase offset is wrong).

Remedy:
Resize the motor so it can withstand the load torque; check motor data; contact technical support.
E 610D

Error in selection parameter		 Cause:
Wrong parameter value selected.

Remedy:
Check the value to be written.
E 7100

System error: invalid power amplifier data		 Cause:
Amplifier data stored in device is corrupt (wrong CRC), error in internal memory data.

Remedy:
Contact technical support or replace the device.
E 7120

Invalid motor data		 Cause:
Motor data are corrupt (wrong CRC).

Remedy:
Contact technical support or replace the motor.
E 7121

System error: errors in motor encoder communication		 Cause:
EMC, detailed information is included in the fault buffer that contains the error code of the encoder.

Remedy:
Contact technical support.
E 7122

Invalid motor data		 Cause:
Motor data stored in motor encoder is corrupt, error in internal memory data.

Remedy:
Contact technical support or replace the motor.
E 7123

Motor current offset outside permissible range		 Cause:
Motor current measurement circuit is defective.

Remedy:
Contact technical support or replace the device.
E 7124

System error: motor encoder faulty		 Cause:
Encoder signals internal fault.

Remedy:
Contact technical support or replace the motor.
E 7328

Motor encoder sends: position capture errors		 Cause:
Encoder signals internal position capturing fault.

Remedy:
Contact technical support or replace the motor.
E 7329

Motor encoder sends: Warning		 Cause:
EMC, encoder signals internal warning.

Remedy:
Contact technical support or replace the motor.
E 7336

Offset with SinCos drift compensation too high		 Cause:
HiFa analogue signal offset during calibration procedure is out of range.

Remedy:
Check encoder connection, replace device / motor.
E 7338

No valid motor absolute position		 Cause:
Warning to inform you that absolute position has not not yet been determined.

Remedy:
Depending on application, fix the absolute position. Device still usable and all functions are OKAY.
E 7500

RS485/Modbus: overrun error		 Cause:
EMC; cabling problem.

Remedy:
Check cables.
E 7501

RS485/Modbus: framing error		 Cause:
EMC; cabling problem.

Remedy:
Check cables.
E 7502

RS485/Modbus: parity error		 Cause:
EMC; cabling problem.

Remedy:
Check cables.
E 7503

RS485/Modbus: receive error		 Cause:
EMC; cabling problem.

Remedy:
Check cables.
E 8110

CANopen: CAN overflow (message lost)		 Cause:
Two short CAN messages have been sent too fast (at 1MBits only).

Remedy:
Check CAN bus timing/load.
E 8120

CANopen: CAN Controller in Error Passive		 Cause:
Too many error frames have been detected.

Remedy:
Check CAN bus installation.
E 8130

CANopen: Heartbeat or Life Guard error		 Cause:
The bus cycle time of the CANopen master is higher than the programmed heartbeat or nodeguard time.

Remedy:
Check CANopen configuration, increase heartbeat or nodeguard time.
E 8141

CANopen: CAN Controller in Busoff		 Cause:
Too many error frames have been detected, CAN devices with different baudrates.

Remedy:
Check CAN bus installation.
E 8201

CANopen: RxPDO1 could not be processed		 Cause:
Error while processing Receive PDO1: PDO1 contains invalid value.

Remedy:
Check RxPDO1 content (application).
E 8202

CANopen: RxPDO2 could not be processed		 Cause:
Error while processing Receive PDO2: PDO2 contains invalid value.

Remedy:
Check RxPDO2 content (application).
E 8203

CANopen: RxPDO3 could not be processed		 Cause:
Error while processing Receive PDO3: PDO3 contains invalid value.

Remedy:
Check RxPDO3 content (application).
E 8204

CANopen: RxPDO4 could not be processed		 Cause:
Error while processing Receive PDO4: PDO4 contains invalid value.

Remedy:
Check RxPDO4 content (application).
E A060

Calculated speed in electronic gear/pulse control too high		 Cause:
Gear ratio or speed reference value too high.

Remedy:
Reduce the gear ratio or speed reference value.
E A061
Position change in reference value with electronic gear/pulse control too high		 Cause:
Position reference change is too high. Reference value input signal disturbance.

Remedy:
  • Reduce the resolution of the master.
  • Check reference value input signal.
E A300
Braking procedure after HALT request still active		 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.
E A301
Drive in status "Quick Stop active"		 Cause:
Error with error class 1 occurred. Drive stopped with Quick Stop command.

Remedy:
  • Check for other error codes causing the stop.
E A302
Interruption by LIMP		 Cause:
LIMP was activated because working range was exceeded, malfunction of limit switch or signal disturbance.

Remedy:
  • Check application.
  • Check limit switch function and connection.
E A303
Interruption by LIMN		 Cause:
LIMN was activated because working range was exceeded, malfunction of limit switch or signal disturbance.

Remedy:
  • Check application.
  • Check limit switch function and connection.
E A305
Power amplifier cannot be activated in the current operating status		 Cause:
Fieldbus: trying to enable the amplifier in status "Not ready to switch on".

Remedy:
  • Refer to the status diagram in the operation chapter of the manual.
E A306
Interruption by user-initiated software stop		 Cause:
Drive is in status "Quick Stop active" due to a software stop request. The activation of a new operating mode is not possible.

Remedy:
  • Clear break condition with command Fault Reset.
E A307
Interruption by internal software stop		 Cause:
In homing and jog modes, the movement is internally interrupted using an internal software stop.

Remedy:
  • Clear break condition with command Fault Reset.
E A308
Drive in "Fault" status		 Cause:
Error with error class 2 or higher occurred.

Remedy:
  • Check error code (HMI or PS2).
  • Remove error condition.
  • Clear error status with command Fault Reset.
E A309
Drive not in status "Operation Enable"		 Cause:
A command which requires the status "Operation enable" was sent (e.g.: opmode change).

Remedy:
  • Set drive to status "OperationEnable" and repeat the command.
E A310
Power amplifier not active		 Cause:
Command is not possible because the power amplifier is not enabled (status "Operation Enabled" or "Quick Stop").

Remedy:
  • Set drive to a status with the amplifier enabled.
  • Refer to the status diagram in the operation chapter of the manual.
E A313
Position overrun, reference point is therefore no longer defined		 Cause:
The position range limits were exceeded which resulted in a loss of the reference point. An absolute movement cannot be made until the definition of a new reference point.

Remedy:
  • Define a new reference point by means of homing mode.
E A314
No reference position		 Cause:
Command needs a defined reference point (ref_ok=1).

Remedy:
  • Define a new reference point by means of homing mode.
E A315
Homing active		 Cause:
Command not possible if homing status is active.

Remedy:
  • Wait until homing movement is finished.
E A317
Drive is not at standstill		 Cause:
Command sent which is not allowed while the motor is not in standstill (e.g., change of software limits, supervision signals, set reference point).

Remedy:
  • Wait until drive has come to a standstill (x_end = 1).
E A318
Operating mode active		 Cause:
Activation of a new operating mode is not possible while the current operating mode is still active.

Remedy:
  • Wait until the command in the operating mode has finished (x_end=1).
  • Or terminate current operating mode with HALT command.
E A319
Manual/Autotuning: distance range overflow		 Cause:
The motor exceeds the parameterised limit ('MT_dismax') of manual tuning.

Remedy:
  • Check reference value and time interval for manual tuning.
E A31A
Manual/Autotuning: amplitude/offset set too high		 Cause:
Amplitude plus offset for tuning exceed internal speed or current limitation.

Remedy:
  • Choose lower amplitude and offset values.
E A31B
HALT requested		 Cause:
Command not allowed while a HALT is requested.

Remedy:
  • Clear HALT request and repeat command.
E A31C
Invalid position setting with software limit switch		 Cause:
Value for negative (positive) software limit is greater (less) than value for positive (negative) software limit, or homing position value is set outside the range.

Remedy:
  • Set correct position values.
E A31D
Speed range overflow ('CTRL_n_max')		 Cause:
The reference speed value was set to a value greater than the max. speed defined in 'CTRL_n_max'.

Remedy:
  • Increase the value of 'CTRL_n_max'.
  • Or reduce the reference speed value.
E A31E
Interruption by positive software limit switch		 Cause:
Command not possible because of overrun of positive software limit switch.

Remedy:
  • Move back to software limit range by means of manual movement.
E A31F
Interruption by negative software limit switch		 Cause:
Command not possible because of overrun of negative software limit switch.

Remedy:
  • Move back to software limit range by means of manual movement.
E A320
Position tracking error		 Cause:
External load or acceleration are too high.

Remedy:
  • Reduce external load or acceleration.
  • Error response is adjustable via 'Flt_pDiff'.
E A321
RS422 position interface is not defined as input signal		 Cause:
RS422 interface is defined as output (e.g. ESIM) at start of electronic gear mode.

Remedy:
  • Define RS422 interface as input via 'IOposInterfac' parameter.
E A324
Error during homing		 Cause:
Homing movement was stopped by an error. Possible sub error codes: EA325, EA326, EA327, EA328, EA329.

Remedy:
  • Check the detailed error reason in the error buffer.
E A325
Limit switch to be approached not enabled		 Cause:
Homing to LIMP or LIMN and limit switches are disabled.

Remedy:
  • Enable limit switch via 'IOsigLimP' or 'IOsigLimN'.
E A326
REF switch not found between LIMP and LIMN		 Cause:
REF input switch defective or not correctly connected.

Remedy:
  • Check the function and wiring of the REF switch.
E A327
Reference movement to REF without direction reversal, improper enabling of limit switch LIM		 Cause:
Search of REF without direction reversal in positive (negative) direction with LIMP (LIMN) activated.

Remedy:
  • Check the function and wiring of the LIMP (LIMN) switch.
E A328
Reference movement to REF without direction reversal, overrun of LIM or REF not permissible		 Cause:
Search of REF without direction reversal and REF or LIM overrun.

Remedy:
  • Reduce homing speed ('HMn') or increase deceleration ('RAMPdecel').
  • Check the function and wiring of LIMP, LIMN and REF switch.
E A329
More than one signal LIMP/LIMN/REF active		 Cause:
REF or LIM not connected correctly or supply voltage for switches too low.

Remedy:
  • Check the wiring and 24VDC supply voltage.
E A32A
Ext. monitoring signal LIMP with neg. direction of rotation		 Cause:
Start reference movement with neg. direction of rotation and activate the LIMP switch (switch in opposite direction).

Remedy:
  • Check correct connection and function of limit switch.
  • Activate a jog movement with negative direction of rotation (target limit switch must be connected to inputs LIMN).
E A32B
Ext. monitoring signal LIMN with pos. direction of rotation		 Cause:
Start reference movement with pos. direction of rotation and activate the LIMN switch (switch in opposite direction).

Remedy:
  • Check correct connection and function of limit switch.
  • Activate a jog movement with positive rotation (target limit switch must be connected to inputs LIMP).
E A32C
Error with REF (switch signal briefly enabled or switch overrun)		 Cause:
Switch signal disturbance. Motor subjected to vibration or shock.

Remedy:
  • Check supply voltage, cabling and function of switch.
  • Check motor reaction after stopping and optimise controller settings.
E A32D
Error with LIMP (switch signal briefly enabled or switch overrun)		 Cause:
Switch signal disturbance. Motor subjected to vibration or shock.

Remedy:
  • Check supply voltage, cabling and function of switch.
  • Check motor reaction after stopping and optimise controller settings.
E A32E
Error with LIMN (switch signal briefly enabled or switch overrun)		 Cause:
Switch signal disturbance. Motor subjected to vibration or shock.

Remedy:
  • Check supply voltage, cabling and function of switch.
  • Check motor reaction after stopping and optimise controller settings.
E A330
Reproducibility of the index pulse movement uncertain		 Cause:
The position difference between the change of the switch signal and the occurrence of the index pulse is too low.

Remedy:
  • Change mounting point of limit switch (optim. to the point at half a motor revolution away from the current mechanical position).
E A332
Error with jog (additional info = detailed error number)		 Cause:
Jog movement was stopped by error.

Remedy:
  • Check the detailed error number in the error buffer.
E A334
Timeout at Standstill window monitor		 Cause:
Position deviation after movement finished greater than standstill window, e.g. caused by an external load.

Remedy:
  • Check load.
  • Check settings for standstill window ('STANDp_win', 'STANDpwinTime' and 'STANDpwinTout').
  • Optimise controller settings.
E A335
Processing only possible in fieldbus mode		 Cause:
Reference movement started in IODevice (homing not possible if 'DEVcmdinterf' is not set to fieldbus device, no limit switches).

Remedy:
  • 'DEVcmdinterf' must be set to fieldbus device.
E A337
Operating mode cannot be continued		 Cause:
Continuation of interrupted movement in profile position mode is not possible because another mode had been active in the meantime. In Motion Sequence mode, motion blend interrupted.

Remedy:
  • Restart the operation or sequence.
E A33A
Reference point is not defined (ref_ok=0)		 Cause:
No homing done and no motor with absolute encoder connected. Homing position lost because the working position range was left.

Remedy:
  • Start homing.
  • Use motor with multiturn encoder if no homing is to be done.
E A33C
Function not available in current operating mode		 Cause:
Activation of a function which is not available in the current operating mode.

Remedy:
  • Check operating mode requirements.
E A33D
Motion blend is already active		 Cause:
Change of motion blend during the current motion blend (end position of motion blend not yet reached).

Remedy:
  • Wait for the motion blend to complete before setting the next position.
E A33E
No movement activated		 Cause:
Activation of a motion blend without movement.

Remedy:
  • Start a movement before the motion blend is activated.
E A33F
Position motion blend movement not in the range of the active movement		 Cause:
The position of the motion blend is outside of the current movement range.

Remedy:
  • Check the position of the motion blend and the current movement range.
E A340
Error in motion sequence mode		 Cause:
The operating mode motion sequence was stopped by an error.

Remedy:
  • Check the error buffer for details on the error.
  • Verify the error by checking the additional error information.
E A341
Position of motion blend has already been passed		 Cause:
The current movement has passed beyond the position of the motion blend.

Remedy:
  • Adjust timing or position parameters.
E A342
Reference velocity was not reached on switch point of motion blend		 Cause:
The position of the motion blend was overrun, the reference velocity was not reached.

Remedy:
  • Reduce the ramp setting to ensure that the reference velocity is reached at the position of the motion blend.
E B100
RS485/Modbus: unknown service		 Cause:
Unsupported Modbus service was received.

Remedy:
  • Check application on the Modbus master.
E B200
RS485/Modbus: Protocol error		 Cause:
Logical protocol error: wrong length or unsupported subfunction.

Remedy:
  • Check application on the Modbus master.
E B201
RS485/Modbus: Nodeguard error		 Cause:
Modbus is defined as command interface: connection monitoring parameter ('MBnode_guard') is <>0ms and a nodeguard event was detected.

Remedy:
  • Check application on the Modbus master.
  • Change (set to 0ms or increase) the parameter 'MBnode_guard' monitoring time.
E B202
RS485/Modbus: Nodeguard warning		 Cause:
Modbus is not defined as command interface: connection monitoring parameter ('MBnode_guard') is <>0ms and a nodeguard event was detected.

Remedy:
  • Check application on the Modbus master.
  • Change (set to 0ms or increase) the parameter 'MBnode_guard' monitoring time.
E B400
CANopen: NMT reset with power amplifier active		 Cause:
NMT Reset command is received while drive is in status "Enable".

Remedy:
  • Always disable the drive before sending a NMT reset command.
E B401
CANopen: NMT reset with power amplifier active (Stop)		 Cause:
NMT Stop command is received while drive is in status "Enable".

Remedy:
  • Always disable the drive before sending a NMT Stop command.
E B403
Excessive Sync period deviation from ideal value		 Cause:
The period time of the SYNC signals is not stable. The deviation is more than 100usec.

Remedy:
  • The SYNC signals of the motion controller (CANsync master) must be more accurate.
E B404
Sync signal failed		 Cause:
SYNC signal was missing too often (more than twice).

Remedy:
  • Check CAN connection.
  • Check motion controller (CANsync master).
E B407
Drive is not synchronous with master cycle		 Cause:
The cyclic synchronous operating mode cannot be activated while the drive is not synchronised.

Remedy:
  • Check motion controller (CANsync master).
  • To be synchronised, the motion controller (CANsync master) must cyclically send SYNC signals.
 

How to Read LXM05 “E” Codes

The Lexium 05 diagnostics are structured into error classes. Understanding the first digit helps identify the source of the problem immediately.

  • E 1xx (Power Stage): Faults starting with ‘1’ (e.g., E 100, E 101) indicate issues with the power supply, short circuits, or ground faults.
  • E 2xx (Motor/Encoder): Faults starting with ‘2’ (e.g., E 205) relate to the motor connection, Hyperface encoder feedback, or thermal overload.
  • E 3xx & E 4xx (Communication/Data): These relate to fieldbus errors (CANopen, Profibus) or internal memory corruption.
  • Software: While the legacy PowerSuite software is discontinued, you can often view the error history using the integrated HMI keypad by navigating to the FLt (Fault) menu.

Frequently Asked Questions (FAQ)

Q: What does “E 205” (Encoder Error) mean?

A: This is the most common fault on aging LXM05 systems.
Meaning: The drive has lost communication with the motor’s SinCos (Hyperface) encoder.
Fix:
1. Check the encoder cable (green cable usually) for breaks, especially in cable chains.
2. Clean the contacts on the DB15 connector.
3. Verify the encoder has not been mechanically decoupled from the motor shaft.

Q: How do I reset the LXM05?

A:
1. Fault Reset Input: Toggle the digital input configured as “Fault Reset” (typically DI 0 or DI 1).
2. Power Cycle: Turn off the 24V control power and the mains power. Wait for the display to turn off completely before restarting.
3. HMI: If the drive is in “Local Mode,” press the reset button on the integrated display.

Q: The drive shows “E 101” (Short Circuit). Can I fix this?

A: E 101 indicates a hard short circuit at the motor output.
Action: Disconnect the motor cable from the drive. Reset the drive.
1. If E 101 returns without the motor connected, the internal IGBT bridge is blown, and the drive must be replaced.
2. If E 101 clears, the short is in your motor cable or motor windings.

Comments

Post a Comment

Popular posts from this blog

Allen Bradley Kinetix 5500 Drive Fault Codes List

Complete guide to Allen Bradley Kinetix 5500 fault codes. Troubleshoot FLT codes, Single-Cable (DSL) feedback errors, shared bus faults, and perform diagnostics via Studio 5000. Kinetix 5500 Fault Codes Reference Table Kinetix 5500 Fault Codes Reference Table Kinetix 5500 Fault Codes Reference Table Fault Code and Meaning Cause and Remedy FLT S03 – MTR OVERSPEED FL Motor Overspeed Factory Limit Fault Cause: Motor speed has exceeded 125% of its maximum speed. Remedy: Check control loop tuning. FLT S04 – MTR OVERSPEED UL Motor Overspeed User Limit Fault Cause: Motor speed has exceeded motor overspeed user limit. Remedy: Check control loop tuning. Increase the Motor Overspeed UL attribute value. FLT S05 – MTR OVERTEMP FL Motor Overtemperature Factory Limit Fault Cause: Calculations based ...
Read more

Danfoss VACON 100 FLOW Drive Fault Codes List

Access the complete reference guide for Danfoss VACON 100 FLOW drive fault codes. Learn to diagnose Multipump communication errors, dry run faults, and use Vacon Live software. VACON 100 FLOW Fault Codes Reference Table VACON 100 FLOW Faults and Alarms VACON 100 FLOW - Fault Tracing Fault Code and Meaning Cause and Remedy Fault Code 1, ID 1 Overcurrent (Hardware Fault) Cause: There is too high a current (> 4 × IH) in the motor cable. a sudden heavy load increase a short circuit in the motor cables the motor is not the correct type the parameter settings are not properly made Remedy: Check the loading. Check the motor. Check the cables and connections. Make an identification run. Set the acceleration time longer (P3.4.1.2 and P3.4.2.2). Fault Code 1, ID 2 Overcurrent (Software Fault...
Read more

ABB ACH580 Drive Fault Codes List

Access the complete reference guide for ABB ACH580 HVAC drive fault codes. Learn to diagnose issues via the Hand-Off-Auto panel, BACnet integration, and Fireman’s Override. The ABB ACH580 is the industry-standard flagship drive for HVACR applications. Designed to control air handling units, cooling towers, and chillers, it ensures critical comfort and safety in buildings. When a malfunction occurs, the dedicated Hand-Off-Auto (HOA) control panel displays a 4-digit code alongside plain-text diagnostics, often integrated directly into the Building Management System (BMS). This guide provides the most updated reference to help you interpret these codes and maintain building environmental standards. ACH580 Fault Codes Reference Table Use the search bar below or browse the table to identify your specific error code: ABB ACH580 Drive Fault Codes List ABB ACH580 Drive Fault Codes List Fault Code and Meaning Cause and Remedy A2B1...
Read more