Schneider Lexium LXM32 Servo Drive

Schneider Lexium LXM32 Servo Drive Fault Codes:

Fault Code and MeaningCause 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 (index) 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 (subindex).
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: –



Remedy:



–
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 interface 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: –



Remedy:



–
1109

Data stored after a power outage is invalid
Cause: –



Remedy:



–
110A

System error detected: No bootloader available
Cause: –



Remedy:



–
110B

Configuration error detected.
Parameter _SigLatched Bit 30
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 section 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:



–
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:



–
1113

System not locked for configuration transfer
Cause: An external tool has tried to transfer the configuration without locking the drive.



Remedy:



–
1114

Configuration download aborted
Parameter _SigLatched Bit 5
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
Parameter _WarnLatched Bit 5
Cause: An external tool has downloaded a configuration which has an incorrect format.



Remedy:



–
1116

Request is processed asynchronously
Cause: –



Remedy:



–
1117

Asynchronous request blocked
Cause: Request to a module is blocked because the module is currently processing another request.



Remedy:



–
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: –



Remedy:



–
111A

Incorrect data length, insufficient number of bytes
Cause: –



Remedy:



–
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.
111E

Not possible to recalculate data set
Cause: A data set of the operating mode Motion Sequence could not be recalculated.



Remedy:



The address of the parameter and the number of the data set that caused this condition can be read via the parameter _PAR_ScalingError.
111F

Recalculation not possible
Cause: Invalid scaling factor.



Remedy:



Verify that you really want the selected scaling factor. Try a different scaling factor. Before triggering scaling, reset the parameters with user-defined units.
1120

Recalculation for scaling not possible
Cause: A parameter could not be recalculated.



Remedy:



The address of the parameter that caused this condition can be read via the parameter _PAR_ScalingError.
1121

Incorrect sequence of steps for scaling (fieldbus)
Cause: The recalculation has been started prior to the initialization.



Remedy:



The recalculation must be started after the initialization.
1122

Recalculation for scaling not possible
Cause: Recalculation for scaling is already running.



Remedy:



Wait for the running recalculation for scaling to finish.
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: –



Remedy:



Close other access channel (for example, other instance of commissioning software).
1127

Invalid key received
Cause: –



Remedy:



–
1128

Special login is required for Manufacturing Test Firmware
Cause: –



Remedy:



–
1129

Test step not yet started
Cause: –



Remedy:



–
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”.
112F

Time filter settings cannot be changed
Cause: Position capture is already active with a time filter. The filter settings cannot be changed.



Remedy:



Deactivate position capture.
1130

Incorrect parameter setting
Cause: The parameter ENC_ModeOfMaEnc is set to “Velocity And Position”. The parameter ErrorResp_PDiffEncM is set to “Error Class 1” or “Error Class 2”. The combination of these settings is invalid.



Remedy:



Set parameter ErrorResp_PDiffEncM to “Error Class 3”.
1131

Function not available
Cause: Function not available



Remedy:



–
1132

Incorrect size of configuration file (odd number of bytes)
Cause: Incorrect number of bytes.



Remedy:



Retry. If the condition persists, contact your Schneider Electric service representative.
1140

File transfer over fieldbus: Read or write access to file denied
Cause: Invalid access channel used. The String field (for the file name) does not contain “Config” or “config”.



Remedy:



Use a valid access channel (fieldbus main channel or Modbus RTU). Use “Config” or “config” in the String field (for the file name).
1141

File transfer over fieldbus: Insufficient memory space
Cause: –



Remedy:



–
1142

File transfer over fieldbus: Invalid password
Cause: No password has been set (password = 0). The password used does not match the password set.



Remedy:



Set a password not equal to 0 to enable the EtherCAT function File Access over EtherCAT. Use the correct password.
1143

File transfer over fieldbus: Error detected with indeterminable error cause
Cause: –



Remedy:



–
1144

File transfer over fieldbus: Incorrect checksum
Cause: –



Remedy:



–
1145

File transfer over fieldbus: Hardware version does not support file transfer over fieldbus
Cause: The hardware version of the drive does not support the EtherCAT function File Access over EtherCAT.



Remedy:



Use a drive with the hardware version ≥RS03.
1146

File transfer over fieldbus: Invalid file header
Cause: –



Remedy:



–
1147

File transfer over fieldbus: File cannot be stored or file already exists
Cause: No memory available for the configuration file or the configuration file already exists.



Remedy:



Power cycle the drive.
1300

Safety-related function STO activated (STO_A, STO_B)
Parameter _SigLatched Bit 10
Cause: The safety-related function STO was activated in the operating state Operation Enabled.



Remedy:



Verify correct wiring of the inputs of the safety-related function STO and perform a Fault Reset.
1301

STO_A and STO_B different level
Parameter _SigLatched Bit 11
Cause: The levels of the inputs STO_A and STO_B were different for more than 1 second.



Remedy:



Verify correct wiring of the inputs of the safety-related function STO.
1302

Safety-related function STO activated (STO_A, STO_B)
Parameter _WarnLatched Bit 10
Cause: Safety-related function STO was activated while the power stage was disabled.



Remedy:



Verify correct wiring of the inputs of the safety-related function STO.
1310

Frequency of the external reference value signal too high
Parameter _SigLatched Bit 28
Cause: The frequency of the external reference value 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 or signal output 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 for signal input function
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.
Parameter _WarnLatched Bit 28
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).
1316

Position capture via signal input currently not possible
Parameter _SigLatched Bit 28
Cause: Position capture is already being used.



Remedy:



–
1317

Interference at PTI input
Parameter _WarnLatched Bit 28
Cause: Interfering pulses or impermissible edge transitions (A and B signal simultaneously) have been detected.



Remedy:



Verify cable specifications, shield connection and EMC.
1318

The selected type of usage of the analog inputs is not possible.
Cause: At least two analog inputs are configured with the same type of usage.



Remedy:



Reconfigure the analog inputs.
1501

System error detected: DriveCom state machine indeterminable state
Cause: –



Remedy:



–
1502

System error detected: HWL low-level state machine indeterminable state
Cause: –



Remedy:



–
1503

Quick Stop triggered via fieldbus
Cause: A Quick Stop has been triggered via the fieldbus. The Quick Stop option code has been set to -1 or -2 which causes the drive to transition to the operating state 9 Fault instead of the operating state 7 Quick Stop Active.



Remedy:



–
1600

Oscilloscope: No additional data available
Cause: –



Remedy:



–
1601

Oscilloscope: Parameterization incomplete
Cause: –



Remedy:



–
1602

Oscilloscope: Trigger variable not defined
Cause: –



Remedy:



–
1606

Logging still active
Cause: –



Remedy:



–
1607

Logging: No trigger defined
Cause: –



Remedy:



–
1608

Logging: Invalid trigger option
Cause: –



Remedy:



–
1609

Logging: No channel selected
Cause: –



Remedy:



–
160A

Logging: No data available
Cause: –



Remedy:



–
160B

Parameter cannot be logged
Cause: –



Remedy:



–
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: –



Remedy:



–
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: Additional information in the error memory indicates the Modbus register address.



Remedy:



–
1612

System error detected: Parameter could not be read during Autotuning
Cause: –



Remedy:



–
1613

Autotuning: Maximum permissible movement range exceeded
Parameter _SigLatched Bit 2
Cause: The movement exceeded the adjusted movement range during Autotuning.



Remedy:



Increase the movement range value or disable movement range monitoring by setting AT_DIS = 0.
1614

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



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 CTRL_I_max).



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: –



Remedy:



–
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.
1A00

System error detected: FIFO memory overflow
Cause: –



Remedy:



–
1A01

Motor has been changed (different type of motor)
Parameter _SigLatched Bit 16
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: –



Remedy:



–
1B00

System error detected: Incorrect parameters for motor and power stage
Parameter _SigLatched Bit 30
Cause: Incorrect manufacturer parameter value (data) nonvolatile memory of device.



Remedy:



Replace device.
1B02

Target value too high
Parameter _SigLatched Bit 30
Cause: –



Remedy:



–
1B04

Product of encoder simulation resolution and the maximum velocity is too high
Parameter _SigLatched Bit 30
Cause: Value in parameter CTRL_v_max or resolution or the encoder simulation ESIM_scale are too high.



Remedy:



Reduce the resolution of the encoder simulation or the maximum velocity in parameter CTRL_v_max.
1B05

Error detected during parameter switching
Parameter _SigLatched Bit 30
Cause: –



Remedy:



–
1B06

Wake & shake cannot be started
Parameter _SigLatched Bit 30
Cause: Motor velocity is too high at the beginning of the wake and shake procedure.



Remedy:



Verify that the motor is at a standstill at the beginning wake and shake procedure.
1B07

Motor velocity is too high at the end of the wake and shake sequence
Cause: Motor was not at a standstill at the end of the wake and shake sequence. Depending on the mechanical system, the commutation offset calculated during wake and shake might be incorrect.



Remedy:



Verify the mechanical system.
1B08

Position difference during the wake and shake procedure is too high
Cause: Incorrect motor data entered by user (especially motor resistance, motor inertia (in case of rotary motors) or motor mass (in case of linear motors)). Incorrect setting for parameter WakeAndShakeGain.



Remedy:



Verify motor data. Verify setting of parameter WakeAndShakeGain.
1B09

The reference current during the wake and shake procedure is reduced as a result of I2t monitoring
Cause: The current used during wake and shake is too high.



Remedy:



–
1B0A

Reference current during wake and shake might be too high for the power stage used
Cause: The wake and shake procedure is performed with the nominal motor current. If the nominal motor current is greater than the nominal power stage current, power stage I2t monitoring might reduce the current used during wake and shake.



Remedy:



–
1B0B

The operating state at the beginning of the commutation offset identification must be Ready To Switch On
Cause: –



Remedy:



Set the operating state to Ready To Switch On and restart commutation offset identification.
1B0C

Motor velocity too high
Cause: –



Remedy:



–
1B0D

Velocity value determined by velocity observer is incorrect
Cause: Incorrect system inertia for velocity observer calculations. Incorrect velocity observer dynamics. System inertia changes during operation. In this case, operation with velocity observer is not possible and the velocity observer must be deactivated.



Remedy:



Change the velocity observer dynamics via the parameter CTRL_SpdObsDyn. Change the system inertia used for velocity observer calculations via the parameter CTRL_SpdObsInert. If the detected error persists, deactivate the velocity observer.
1B0E

Not possible to determine the commutation angle at the end of the wake and shake procedure
Cause: Incorrect motor data, for example motor resistance, motor inertia (in case of rotary motors) or motor mass (in case of linear motors). Incorrect setting for parameter WakeAndShakeGain. Holding brake (if available) not properly wired.



Remedy:



Verify correct motor data. Verify setting of parameter WakesAndShakeGain. Verify correct wiring of holding brake.
1B0F

Velocity deviation too high
Cause: –



Remedy:



–
2300

Power stage overcurrent
Parameter _SigLatched Bit 27
Cause: Motor short circuit and disabling of the power stage. Motor phases are inverted.



Remedy:



Verify the motor power connection.
2301

Braking resistor overcurrent
Parameter _SigLatched Bit 27
Cause: Braking resistor short circuit.



Remedy:



If you use the internal braking resistor, contact your Schneider Electric service representative. If you use an external braking resistor, verify correct wiring and rating of the braking resistor.
3100

Missing mains supply, undervoltage mains supply or overvoltage mains supply
Parameter _SigLatched Bit 15
Cause: Missing phase(s) for more than 50 ms. Mains voltage is out of range. Mains frequency is out of range.



Remedy:



Verify that the values of the mains power supply network comply with the technical data.
3200

DC bus overvoltage
Parameter _SigLatched Bit 14
Cause: Excessive regeneration during deceleration.



Remedy:



Verify correct deceleration ramp, rating of drive and braking resistor.
3201

DC bus undervoltage (shutdown threshold)
Parameter _SigLatched Bit 13
Cause: Power supply outage, insufficient power supply.



Remedy:



Verify mains supply.
3202

DC bus undervoltage (Quick Stop threshold)
Parameter _SigLatched Bit 13
Cause: Power supply outage, insufficient power supply.



Remedy:



Verify mains supply.
3206

Undervoltage DC bus, missing mains supply, undervoltage mains supply or overvoltage mains supply
Parameter _WarnLatched Bit 13
Cause: Missing phase(s) for more than 50 ms. Mains voltage is out of range. Mains frequency is out of range. Mains voltage and setting of parameter MON_MainsVolt do not match (for example, mains voltage is 230 V and MON_MainsVolt is set to 115 V).



Remedy:



Verify that the values of the mains power supply network comply with the technical data. Verify the settings of the parameter for reduced mains voltage.
3300

The winding voltage of the motor is lower than the nominal supply voltage of the drive
Cause: If the winding voltage of the motor is lower than the nominal supply voltage of the drive, this may result in motor overtemperature due to high current ripple.



Remedy:



Verify the motor temperature. In the case of overtemperature, use a motor with a higher winding voltage or use a drive with a lower nominal supply voltage.
4100

Power stage overtemperature
Parameter _SigLatched Bit 18
Cause: Excessively high ambient temperature due to, for example, dust.



Remedy:



Improve heat dissipation. If a fan is installed, verify correct operation of the fan.
4101

Power stage overtemperature
Parameter _WarnLatched Bit 18
Cause: Excessively high ambient temperature due to, for example, dust.



Remedy:



Improve heat dissipation. If a fan is installed, verify correct operation of the fan.
4102

Power stage overload (I2t)
Parameter _WarnLatched Bit 30
Cause: The current has exceeded the nominal value for an extended period of time.



Remedy:



Verify rating, reduce cycle time.
4200

Device overtemperature
Parameter _SigLatched Bit 18
Cause: Excessively high ambient temperature due to, for example, dust.



Remedy:



Improve heat dissipation. If a fan is installed, verify correct operation of the fan.
4300

Motor overtemperature
Parameter _SigLatched Bit 17
Cause: Ambient temperature is too high. Duty cycle is too high. Motor not properly mounted (thermal isolation). Motor overload.



Remedy:



Verify motor installation: The heat must be dissipated via the mounting surface. Reduce ambient temperature. Provide ventilation.
4301

Motor overtemperature
Parameter _WarnLatched Bit 17
Cause: Ambient temperature is too high. Duty cycle is too high. Motor not properly mounted (thermal isolation). Motor overload.



Remedy:



Verify motor installation: The heat must be dissipated via the mounting surface. Reduce ambient temperature. Provide ventilation.
4302

Motor overload (I2t)
Parameter _WarnLatched Bit 31
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.
4303

No motor temperature monitoring
Cause: The temperature parameters (in electronic nameplate of motor, nonvolatile memory of encoder) are unavailable or invalid; parameter A12 is equal to 0.



Remedy:



Contact your Schneider Electric service representative. Replace motor.
4304

The encoder does not support motor temperature monitoring
Cause: –



Remedy:



–
4402

Braking resistor overload (I2t > 75%)
Parameter _WarnLatched Bit 29
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 (I2t > 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.
4404

Overload of transistor for braking resistor
Parameter _WarnLatched Bit 28
Cause: Regeneration energy too high. External loads too high. Deceleration too fast.



Remedy:



Reduce load and/or deceleration.
5101

Modbus power supply missing
Cause: –



Remedy:



–
5102

Motor encoder supply voltage
Parameter _SigLatched Bit 16
Cause: Encoder power supply is not within permissible range of 8 V to 12 V.



Remedy:



Replace the device. Contact your Schneider Electric service representative.
5200

Error detected at connection to motor encoder
Parameter _SigLatched Bit 16
Cause: Encoder not properly connected, EMI



Remedy:



–
5201

Error detected in motor encoder communication
Parameter _SigLatched Bit 16
Cause: Encoder not properly connected, EMI



Remedy:



–
5202

Motor encoder is not supported
Parameter _SigLatched Bit 16
Cause: Incompatible encoder connected.



Remedy:



–
5203

Error detected in connection motor encoder
Parameter _SigLatched Bit 16
Cause: Encoder not properly connected



Remedy:



–
5204

Connection to motor encoder lost
Parameter _SigLatched Bit 16
Cause: Encoder not properly connected



Remedy:



–
5206

Communication error detected in encoder
Parameter _WarnLatched Bit 16
Cause: Communication channel to encoder is subject to interference.



Remedy:

  • Verify EMC measures.
5207

Function is not supported
Cause: The hardware revision does not support the function.



Remedy: –
5302

The motor requires a PWM frequency (16kHz) which the power stage does not support.
Cause: The motor only works with a PWM frequency of 16 kHz (motor nameplate entry). However, the power stage does not support this PWM frequency.



Remedy:

  • Use a motor that works with a PWM frequency of 8 kHz.

  • Contact your Schneider Electric service representative.
5430

System error detected: Nonvolatile memory read error
Parameter _SigLatched Bit 29
Cause: –



Remedy: –
5431 – 543E

System error: Nonvolatile memory errors (write, address, data, checksums)
Parameter _SigLatched Bit 29
Cause: –



Remedy: –
5446

System error detected: Nonvolatile memory checksum error (for power outage data)
Parameter _SigLatched Bit 29
Cause: Internal nonvolatile memory not operative.



Remedy:

  • Restart the drive.

  • If the detected error persists, contact your Schneider Electric service representative.
544D

System error detected: Memory card
Parameter _SigLatched Bit 20
Cause: The last saving procedure may not have been successful; the memory card may be inoperative.



Remedy:

  • Retry saving the data.

  • Replace the memory card.
544E

System error detected: Memory card
Parameter _SigLatched Bit 20
Cause: The last saving procedure may not have been successful; the memory card may be inoperative.



Remedy:

  • Retry saving the data.

  • Replace the memory card.
544F

System error detected: Memory card
Parameter _SigLatched Bit 20
Cause: The last saving procedure may not have been successful; the memory card may be inoperative.



Remedy:

  • Retry saving the data.

  • Replace the memory card.
5451

System error detected: No memory card available
Parameter _WarnLatched Bit 20
Cause: –



Remedy: –
5452

System error detected: Data on memory card and device do not match
Parameter _SigLatched Bit 20
Cause: Different type of device. Different type of power stage. Data on memory card does not match firmware version of device.



Remedy: –
5455

System error detected: Memory card not formatted properly
Parameter _SigLatched Bit 20
Cause: –



Remedy:

  • Format memory card or copy data from drive to memory card.
5456

System error detected: Memory card is write-protected
Parameter _SigLatched Bit 20
Cause: The memory card has been write-protected.



Remedy:

  • Remove memory card or disable write protection.
5457

System error detected: Incompatible memory card
Parameter _SigLatched Bit 20
Cause: Memory card capacity is insufficient.



Remedy:

  • Replace memory card.
5462

Memory card implicitly written by the device
Parameter _WarnLatched Bit 20
Cause: The content of the memory card and the content of the nonvolatile memory are not identical.



Remedy: –
5501

System error detected: Received toggle bit does not match
Cause: Software watchdog safety module eSM (CPU_A).



Remedy: –
5507

A Fault Reset was not processed by the safety module eSM
Cause: The safety module eSM was unable to execute the Fault Reset, for example, because it was still processing an error response.



Remedy:

  • Trigger the Fault Reset again.
5600

Motor connection phase error detected
Parameter _SigLatched Bit 26
Cause: Missing motor phase.



Remedy: –
5603

Commutation error detected. Additional information in the error memory indicates Internal_DeltaQuep.
Parameter _SigLatched Bit 26
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 nonvolatile memory contains incorrect data (encoder phase offset is incorrect).

  • Motor is not adjusted.





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 your Schneider Electric service representative.
610D

Error detected in selection parameter
Cause: Incorrect parameter value selected.



Remedy:

  • Verify the value to be written.
6117

Holding brake cannot be released manually.
Cause: The holding brake cannot be released manually because it is still applied manually.



Remedy:

  • First, switch from applying the holding brake manually to Automatic, then to releasing the holding brake manually.
7100

System error detected: Invalid power stage data
Parameter _SigLatched Bit 30
Cause: Error detected in power stage data stored in device (incorrect CRC), error detected in internal memory data.



Remedy:

  • Contact your Schneider Electric service representative or replace the device.
7110

System error detected: Internal braking resistor
Cause: Internal braking resistor is inoperative or not connected.



Remedy:

  • Contact your Schneider Electric service representative.
7111

Parameter cannot be changed because the external braking resistor is active.
Cause: An attempt is made to change one of the parameters RESext_ton, RESext_P or RESext_R even though the external braking resistor is active.



Remedy:

  • Verify that the external braking resistor is not active if one of the parameters RESext_ton, RESext_P or RESext_R has to be changed.
7112

No external braking resistor connected
Cause: External braking resistor activated (Parameter RESint_ext), but no external resistor is detected.



Remedy:

  • Verify wiring of the external braking resistor. Verify correct resistance.
7120

Invalid motor data
Parameter _SigLatched Bit 16
Cause: Motor data is incorrect (incorrect CRC).



Remedy:

  • Contact your Schneider Electric service representative or replace the motor.
7121

System error detected: Error in motor encoder communication
Parameter _SigLatched Bit 16
Cause: EMI, detailed information can be found in the error memory that contains the error code of the encoder.



Remedy:

  • Contact your Schneider Electric service representative.
712D

Electronic motor nameplate not found
Parameter _SigLatched Bit 16
Cause: Incorrect motor data (incorrect CRC). Motor without electronic motor nameplate (for example, SER motor).



Remedy:

  • Contact your Schneider Electric service representative or replace the motor.
7320

System error detected: Invalid encoder parameter
Parameter _SigLatched Bit 16
Cause: Communication channel (Hiperface) to encoder is subject to interference, motor encoder has not been factory-parameterized.



Remedy:

  • Contact your Schneider Electric service representative.
7321

Timeout reading the absolute position from the encoder
Parameter _SigLatched Bit 16
Cause: Communication channel (Hiperface) to encoder is subject to interference or motor encoder is inoperative.



Remedy:

  • Verify EMC measures.
7327

Error bit set in Hiperface answer
Parameter _WarnLatched Bit 16
Cause: EMI.



Remedy:

  • Verify wiring (shield).
7328

Motor encoder: Position evaluation error detected
Parameter _SigLatched Bit 16
Cause: Encoder has detected incorrect position evaluation.



Remedy:

  • Contact your Schneider Electric service representative or replace the motor.
7330

System error detected: Motor encoder (Hiperface)
Parameter _SigLatched Bit 16
Cause: –



Remedy:

  • Verify EMC measures.

  • Contact your Schneider Electric service representative.
7335

Communication with motor encoder active
Parameter _WarnLatched Bit 16
Cause: Command is being processed or communication may be disturbed (EMI).



Remedy:

  • Verify EMC measures.

  • Contact your Schneider Electric service representative.
733F

Amplitude of encoder analog signals too low
Parameter _SigLatched Bit 16
Cause: Incorrect encoder wiring. Encoder not connected. Encoder signals subject to EMI.



Remedy:

  • Verify EMC measures.

  • Contact your Schneider Electric service representative.
7340

Reading of absolute position aborted
Parameter _SigLatched Bit 16
Cause: Communication channel (Hiperface) to encoder is subject to interference. Encoder (in motor) is inoperative.



Remedy:

  • Verify EMC measures.

  • Contact your Schneider Electric service representative.
7341

Encoder overtemperature
Parameter _WarnLatched Bit 16
Cause:

  • The maximum permissible duty cycle is exceeded.

  • The motor was not mounted properly (e.g., thermally isolated).

  • The motor is blocked so that more current is used than under normal conditions.

  • The ambient temperature is too high.





Remedy:

  • Reduce the duty cycle, for example, reduce acceleration.

  • Supply additional cooling, for example, use a fan.

  • Mount the motor in such a way as to increase thermal conductivity.

  • Use a differently rated drive or motor.

  • Replace the motor.
7343 – 7344

Absolute position is different from incremental position
Cause: Encoder is subject to EMI. Motor encoder is inoperative.



Remedy:

  • Verify EMC measures.

  • Contact your Schneider Electric service representative.
7345

Amplitude of analog signals too high, limit of AD conversion exceeded
Cause: Encoder signals subject to EMI (shield connection, wiring, etc.). Encoder inoperative.



Remedy:

  • Verify EMC measures.

  • Contact your Schneider Electric service representative.
7347

System error detected: Position initialization not possible
Cause: Analog and digital encoder signals subject to massive interference.



Remedy:

  • Verify EMC measures.

  • Contact your Schneider Electric service representative.
7349

Discrepancy between absolute and analog encoder phases
Cause: Analog encoder signals are subject to interference. Encoder inoperative.



Remedy:

  • Verify EMC measures.

  • Contact your Schneider Electric service representative.
734C

Error detected with quasi absolute position
Parameter _SigLatched Bit 16
Cause: The motor shaft may have been moved while the drive was powered down. A quasi absolute position has been detected that is not within the permissible motor shaft deviation range.



Remedy:

  • If the quasi absolute function is active, only power down the drive if the motor is at a standstill and do not move the motor shaft when the drive is off.
734E

Error in analog signals from encoder detected. Additional information in the error memory indicates Internal_DeltaQuep.
Parameter _SigLatched Bit 16
Cause: Encoder cable not properly connected. Encoder signals subject to EMI. Mechanical issue.



Remedy:

  • Verify EMC measures.

  • Contact your Schneider Electric service representative.
7500 – 7503

RS485/Modbus Errors (Overrun, Framing, Parity, Receive)
Parameter _WarnLatched Bit 5
Cause: EMI; incorrect cabling.



Remedy:

  • Verify cables.
7607

Encoder module cannot be identified
Parameter _SigLatched Bit 22
Cause: The encoder module is indeterminable.



Remedy:

  • Use correct encoder module.
7608

Encoder module power supply overcurrent
Parameter _SigLatched Bit 22
Cause: Short circuit at connector or encoder cable. Incorrect or inoperative encoder.



Remedy: –
7609

Encoder not connected to encoder module
Parameter _SigLatched Bit 22
Cause: Connector not connected to module or not connected to motor/encoder. Incorrect or inoperative encoder cable.



Remedy: –
760A

Encoder module in slot 2 missing
Parameter _SigLatched Bit 22
Cause: Module has been removed or module is inoperative.



Remedy: –
760C

Maximum encoder frequency exceeded
Parameter _SigLatched Bit 22
Cause: Velocity too high for the encoder.



Remedy: –
760D

Configuration error detected: Incorrect use of encoder module
Parameter _SigLatched Bit 22
Cause: Incorrect value in parameter ENC2_usage.



Remedy: –
760E

Position evaluation error detected (signal tracking error detected)
Parameter _SigLatched Bit 22
Cause: Encoder signals subject to EMI.



Remedy: Verify wiring and cable shield.
760F

Incorrect position evaluation (interference detected)
Parameter _WarnLatched Bit 22
Cause: Encoder signals subject to EMI.



Remedy: Verify wiring, cable shield.
7610

Resolver: Loss of position tracking, position is inaccurate
Parameter _WarnLatched Bit 22
Cause: Motor velocity is too high. Motor acceleration is too fast.



Remedy:

  • Reduce velocity.

  • Reduce acceleration.

  • Reduce resolver resolution.

  • Adapt resolver excitation frequency.
7611

Resolver: Signal degradation, position is inaccurate
Parameter _SigLatched Bit 22
Cause: Resolver is inoperative. Resolver signals are subject to interference. Resolver cable is too long.



Remedy:

  • Replace resolver.

  • Verify resolver cable: wiring and shield connection.

  • Additional info bits: D5: Sine/cosine inputs exceed DOS out of range threshold. D4: Sine/cosine inputs exceed DOS mismatch threshold.
7612

Resolver: Loss of signal, position unreliable
Parameter _SigLatched Bit 22
Cause: Resolver is inoperative. Resolver wiring is incorrect. Resolver signals are subject to excessive interference. Resolver is unsuitable for drive. Incorrect parameter transformation ratio.



Remedy:

  • Verify resolver cable: wiring and shield connection.

  • Replace resolver.

  • Additional info bits: D7: Sine/cosine inputs clipped. D6: Sine/cosine inputs below LOS threshold.
7613

Resolver: Signal communication subject to interference
Parameter _SigLatched Bit 22
Cause: Resolver signals are subject to interference.



Remedy: Verify resolver cable: wiring and shield connection.
7614

Error detected at resolver power supply
Parameter _SigLatched Bit 22
Cause: Resolver is not properly connected.



Remedy: Verify resolver cable.
7615

System error detected: Encoder module RES is not ready for position evaluation
Parameter _SigLatched Bit 22
Cause: EMI.



Remedy: Verify resolver cable.
7616

System error detected: Resolver timeout
Parameter _SigLatched Bit 22
Cause: –



Remedy: Replace encoder module.
7617

Resolver velocity is too high
Parameter _SigLatched Bit 22
Cause: Motor velocity is too high.



Remedy: Reduce motor velocity.
7618

Encoder 2 Hall sensor error detected
Parameter _SigLatched Bit 22
Cause: Incorrect wiring or inoperative cable for Hall signals of encoder 2.



Remedy: Verify encoder cable.
7619

Incorrect communication between module and encoder
Parameter _SigLatched Bit 22
Cause: Incorrect encoder wiring/adjustment or incorrect encoder parameter settings (example: parameter ENCDigSSICoding is set for SSI encoder).



Remedy: Verify encoder cable: wiring and shield connection. Verify encoder parameter settings. Verify encoder adjustment.
761A

Incorrect communication between module and encoder
Parameter _WarnLatched Bit 22
Cause: Incorrect encoder wiring.



Remedy: Verify encoder cable: wiring and shield connection.
761B

Connected type of EnDat encoder is not supported
Parameter _SigLatched Bit 22
Cause: –



Remedy: Use a supported EnDat encoder.
761C

Configuration error detected: Invalid SSI encoder parameter setting
Parameter _SigLatched Bit 22
Cause: Incorrect values in parameter ENCDigSSIResSgl or ENCDigSSIResMult.



Remedy: –
761D

Maximum velocity of the encoder is exceeded
Parameter _SigLatched Bit 22
Cause: Velocity too high for the encoder. In the case of SSI or EnDat2.2, the reason may also be a detected encoder communication error.



Remedy: –
761E

Encoder module overtemperature
Parameter _SigLatched Bit 22
Cause: The ambient temperature is too high.



Remedy: Improve the heat dissipation in the control cabinet.
761F

Position evaluation error detected (AB encoder signals)
Parameter _SigLatched Bit 22
Cause: No sync signal available.



Remedy: –
7620

Checksum error detected in EnDat encoder data
Parameter _SigLatched Bit 22
Cause: –



Remedy: –
7621

Runtime compensation was not successful
Parameter _SigLatched Bit 22
Cause: –



Remedy: Verify encoder cable: wiring and shield connection.
7622

Resolver timeout
Parameter _WarnLatched Bit 22
Cause: System error detected.



Remedy: Replace encoder module.
7623

Absolute encoder signal is not available
Parameter _WarnLatched Bit 22
Cause: There is no encoder available at the input specified via the parameter ENC_abs_source.



Remedy: Verify wiring, verify encoder. Change the value of the parameter ENC_abs_source.
7624

Absolute position for encoder 2 cannot be set
Parameter _WarnLatched Bit 22
Cause: No encoder connected or encoder does not support setting of absolute positions.



Remedy: Use an encoder that supports direct setting of the absolute position via ENC2_setpabs.
7625

Not possible to set the absolute position for encoder 1
Parameter _WarnLatched Bit 22
Cause: There is no encoder connected to the input for encoder 1.



Remedy: Connect an encoder to the input for encoder 1 before trying to set the absolute position directly via ENC1_abs_pos.
7626

Overflow error detected during encoder scaling
Parameter _SigLatched Bit 22
Cause: The multiturn resolution of the machine encoder with reference to the motor shaft exceeds the system limits, for example, due to the mechanical gear ratio between machine encoder and motor encoder.



Remedy: Reduce the number of bits of the multiturn resolution that are used for position evaluation via the parameter ENCDigResMulUsed.
7627

Configuration error detected: Invalid BiSS encoder parameter setting
Parameter _SigLatched Bit 22
Cause: Incorrect values in parameters ENCDigBISSResSgl or ENCDigBISSResMult.



Remedy: –
7628

BiSS encoder bits ‘War’ or ‘Err’ are set
Parameter _WarnLatched Bit 22
Cause: The bits are used for diverse types of monitoring such as:

  • Encoder temperature is too high.

  • Service life of LED inside encoder exceeded.

  • Position is not reliable.





Remedy: Replace encoder.
7629

BiSS initialization error detected
Parameter _SigLatched Bit 22
Cause: –



Remedy: –
7701

System error detected: Timeout during connection to power stage
Parameter _SigLatched Bit 31
Cause: –



Remedy: Contact your Schneider Electric service representative.
7702

System error detected: Invalid data received from power stage
Parameter _SigLatched Bit 31
Cause: –



Remedy: Contact your Schneider Electric service representative.
7703

System error detected: Data exchange with power stage lost
Parameter _SigLatched Bit 31
Cause: –



Remedy: Contact your Schneider Electric service representative.
7704

System error detected: Exchange of identification data from power stage not successful
Parameter _SigLatched Bit 31
Cause: –



Remedy: Contact your Schneider Electric service representative.
7705

System error detected: Checksum identification data from power stage incorrect
Parameter _SigLatched Bit 31
Cause: –



Remedy: Contact your Schneider Electric service representative.
7706

System error detected: No identification frame received from power stage
Parameter _SigLatched Bit 31
Cause: –



Remedy: Contact your Schneider Electric service representative.
7707

System error detected: Type of power stage and manufacture data do not match
Cause: –



Remedy: Contact your Schneider Electric service representative.
7708

PIC voltage supply too low
Parameter _SigLatched Bit 31
Cause: –



Remedy: Contact your Schneider Electric service representative.
7709

System error detected: Invalid numbers of data received
Parameter _SigLatched Bit 31
Cause: –



Remedy: Contact your Schneider Electric service representative.
770A

PIC received data with incorrect parity
Parameter _SigLatched Bit 31
Cause: –



Remedy: Contact your Schneider Electric service representative.
7800

eSM module: System error detected: Error of class 1 forced
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7801

eSM module: System error detected: Error of class 2 forced
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7802

eSM module: System error detected: Error of class 3 forced
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7803

eSM module: System error detected: Error of class 4 forced
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7804

eSM module: Insufficient deceleration for Quick Stop
Parameter _SigLatched Bit 23
Cause: Quick Stop ramp of drive lower than Quick Stop ramp configured for eSM.



Remedy: Change ramp in eSM or drive.
7805

eSM module: Error detected during Safe Operating Stop (SOS)
Parameter _SigLatched Bit 23
Cause: Motor movement during Safe Operating Stop (SOS).



Remedy: Keep motor from moving while Safe Operating Stop is active (external forces, loads).
7806

eSM module: Safely Limited Speed (SLS) exceeded in machine operating mode Setup Mode
Parameter _SigLatched Bit 23
Cause: Delay for reaching Safely Limited Speed (SLS) too low or eSM deceleration ramp too high.



Remedy: Increase delay for eSM control of Safely Limited Speed (SLS) or decrease eSM deceleration ramp for reaching Safely Limited Speed (SLS).
780A

eSM module: /ESTOP signal for EMERGENCY STOP triggered
Parameter _SigLatched Bit 23
Cause: EMERGENCY STOP is active.



Remedy: Reset EMERGENCY STOP.
780B

eSM module: Not ready for Fault Reset
Parameter _WarnLatched Bit 23
Cause: eSM is in state Quick Stop Active or Fault Reaction Active or Fault.



Remedy: Wait until eSM is no longer in state Quick Stop Active or Fault Reaction Active or Fault or reboot the drive.
780C

eSM module: Not ready for eSM Disable
Parameter _WarnLatched Bit 23
Cause: Safety module eSM is not in operating state Operation Enabled.



Remedy: eSM Disable requires the safety module eSM to be in operating state Operation Enabled.
780F

eSM module: Parameter cannot be written in this operating state
Parameter _WarnLatched Bit 23
Cause: Parameter cannot be written in this eSM state.



Remedy: Change eSM state to write this parameter.
7810

eSM module: Incorrect password
Parameter _WarnLatched Bit 23
Cause: The password that was sent by the configuration tool is not identical to the password stored in the device.



Remedy: Send the stored password.
7811

eSM module: Timeout during parameter download (default values loaded)
Parameter _WarnLatched Bit 23
Cause: Incorrect connection or EMI.



Remedy: Verify wiring (shield).
7813

eSM module: Parameter checksum cannot be written in this operating state
Parameter _WarnLatched Bit 23
Cause: eSM is not ready to be configured.



Remedy: Use correct password. Reconfigure safety module eSM. Contact your Schneider Electric service representative.
7814

eSM module: Parameter checksum incorrect (default values loaded)
Parameter _WarnLatched Bit 23
Cause: EMI. The commissioning software is outdated and not compatible with the safety module eSM.



Remedy: Verify wiring (shield). Install latest commissioning software version.
7815

eSM module: Undertemperature
Parameter _WarnLatched Bit 23
Cause: Temperature too low.



Remedy: –
7816

eSM module: Overtemperature
Parameter _WarnLatched Bit 23
Cause: Temperature too high.



Remedy: Verify the ambient conditions. Verify that the flow of air is sufficient (pollution, objects).
7818

eSM module: System error detected: ESM5VDC undervoltage
Parameter _SigLatched Bit 23
Cause: Error detected in eSM 5V supply.



Remedy: –
7819

eSM module: Overload outputs channel A
Parameter _SigLatched Bit 23
Cause: Short circuit or overload.



Remedy: Verify wiring and connected devices.
781A

eSM module: System error detected: 5V overvoltage
Parameter _SigLatched Bit 23
Cause: eSM internal power supply error detected.



Remedy: –
781B

eSM module: System error detected: 5V undervoltage
Parameter _SigLatched Bit 23
Cause: eSM internal power supply error detected.



Remedy: –
781D

eSM module: ESMSTART: Maximum permissible pulse duration exceeded
Parameter _SigLatched Bit 23
Cause: Pulse duration longer than 4 seconds.



Remedy: Pulse duration must be less than 4 seconds.
781E

eSM module: System error detected: RAM
Parameter _SigLatched Bit 23
Cause: eSM RAM error detected.



Remedy: –
781F

eSM module: System error detected: Stack overflow
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7820

eSM module: System error detected: Program sequence control (communication)
Parameter _SigLatched Bit 23
Cause: Software watchdog eSM (CPU_B).



Remedy: –
7821

eSM module: System error detected: Program sequence control (Idle task)
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7825

eSM module: System error detected: Firmware checksum
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7826

eSM module: Parameter outside of permissible value range
Parameter _WarnLatched Bit 23
Cause: Parameter outside of permissible value range.



Remedy: Verify parameter value.
7827

eSM module: Parameter checksum error detected
Parameter _SigLatched Bit 23
Cause: Saved parameter values are invalid.



Remedy: Reconfigure the eSM. Contact your Schneider Electric service representative.
7828

eSM module: System error detected: SPI framing error detected
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7829

eSM module: Input states channel A and channel B are not identical
Parameter _SigLatched Bit 23
Cause: Wire break or connected devices are inoperable.



Remedy: Verify wiring and connected devices.
782A

eSM module: Output states channel A and channel B are not identical
Parameter _SigLatched Bit 23
Cause: Short circuit to 24V DC. System error detected.



Remedy: Verify wiring and connected devices. Verify connection of STO_A and STO_B. Contact your Schneider Electric service representative.
782B

eSM module: System error detected: Position evaluation error detected (values not identical)
Parameter _SigLatched Bit 23
Cause: CPU_A and CPU_B have different position values. This condition may have been caused by the encoder.



Remedy: –
782C

eSM module: System error detected: Velocity evaluation error detected (values not identical)
Parameter _SigLatched Bit 23
Cause: CPU_A and CPU_B have different velocity values. This condition may have been caused by the encoder.



Remedy: –
782F

eSM module: System error detected: Error detected during dynamization of STO signal
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7833

eSM module: System error detected: Nonvolatile memory incorrect checksum (default values loaded)
Parameter _WarnLatched Bit 23
Cause: Nonvolatile memory inoperative.



Remedy: –
7834

eSM module: Safety module replaced (default values loaded)
Parameter _WarnLatched Bit 23
Cause: This safety module has not been configured with this drive. The parameters have been reset to the default values.



Remedy: Reconfigure the safety module.
7835

eSM module: Commutation position
Parameter _SigLatched Bit 23
Cause: Encoder error or error in internal communication with the drive detected (for example, EMI).



Remedy: Verify EMC. Verify encoder connection. Contact your Schneider Electric service representative.
7836

eSM module: Parameter checksums not identical
Parameter _SigLatched Bit 23
Cause: Parameter of CPU_A is not identical to parameter of CPU_B. Not possible to load parameters into safety module eSM.



Remedy: Retry loading the parameters into the safety module eSM. If the condition persists, contact your Schneider Electric service representative.
7837

eSM module: System error detected: Boot program: Invalid address
Parameter _WarnLatched Bit 23
Cause: Invalid write access of bootloader to flash memory range.



Remedy: –
7838

eSM module: Safely Limited Speed (SLS) exceeded in machine operating mode Automatic Mode
Parameter _SigLatched Bit 23
Cause: Drive velocity greater than configured eSM speed limit.



Remedy: Reduce velocity of the drive or verify eSM speed limit for machine operating mode Automatic Mode.
7839

eSM module: Input ESMSTART low instead of high (automatic start)
Parameter _SigLatched Bit 23
Cause: ESMSTART is configured for automatic start and must be high at start.



Remedy: Verify parameter configuration of ESMSTART. Verify wiring of ESMSTART.
783A

eSM module: Input ESMSTART high instead of low (manual start)
Parameter _SigLatched Bit 23
Cause: ESMSTART is configured for manual start and must be low at start.



Remedy: Verify parameter configuration of ESMSTART. Verify wiring of ESMSTART.
783B

eSM module: Guard door acknowledgment: The acknowledgement signal is available for too long a time.
Parameter _SigLatched Bit 23
Cause: The acknowledgement signal is available for more than 6 seconds.



Remedy: The acknowledgement signal must be available for less than 6 seconds.
783C

eSM module: System error detected: States of eSM state machines not identical
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
783F

eSM module: Output AUXOUT1 (cross fault to another output detected)
Parameter _SigLatched Bit 23
Cause: Cross fault detection detected a cross fault to another output.



Remedy: Verify wiring and connected devices.
7840

eSM module: Output /INTERLOCK_OUT (cross fault to another output detected)
Parameter _SigLatched Bit 23
Cause: Cross fault detection detected a cross fault to another output.



Remedy: Verify wiring and connected devices.
7841

eSM module: Output RELAY_OUT_A (cross fault to another output detected)
Parameter _SigLatched Bit 23
Cause: Cross fault detection detected a cross fault to another output.



Remedy: Verify wiring and connected devices.
7842

eSM module: Output CCM24V_OUT_A (cross fault to another output detected)
Parameter _SigLatched Bit 23
Cause: Cross fault detection detected a cross fault to another output.



Remedy: Verify wiring and connected devices.
7843

eSM module: Output AUXOUT1 (cross fault to 24 V detected)
Parameter _SigLatched Bit 23
Cause: Cross fault detection detected a cross fault to 24 V.



Remedy: Verify wiring and connected devices.
7844

eSM module: Output /INTERLOCK_OUT (cross fault to 24 V detected)
Parameter _SigLatched Bit 23
Cause: Cross fault detection detected a cross fault to 24 V.



Remedy: Verify wiring and connected devices.
7845

eSM module: Output RELAY_OUT_A (cross fault to 24 V detected)
Parameter _SigLatched Bit 23
Cause: Cross fault detection detected a cross fault to 24 V.



Remedy: Verify wiring and connected devices.
7846

eSM module: Output CCM24V_OUT_A (cross fault to 24 V detected)
Parameter _SigLatched Bit 23
Cause: Cross fault detection detected a cross fault to 24 V.



Remedy: –
7848

eSM module: System error detected: Input ESMSTART_A
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7849

eSM module: System error detected: Input SETUPENABLE_A
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
784A

eSM module: System error detected: Input SETUPMODE_A
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
784B

eSM module: System error detected: Input GUARD_A
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
784C

eSM module: System error detected: Input GUARD_ACK
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
784D

eSM module: System error detected: Input /INTERLOCK_IN_A
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
784E

eSM module: System error detected: Input /ESTOP_A
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
784F

eSM module: System error detected: Input NOTUSED_A
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7850

eSM module: Overload outputs channel B
Parameter _SigLatched Bit 23
Cause: Short circuit or overload.



Remedy: Verify wiring and connected devices.
7851

eSM module: System error detected: UART overrun/framing error
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7852

eSM module: System error detected: ResEnc (encoder resolution) is set to 0
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7853

eSM module: System error detected: CPU synchronization
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7854

eSM module: No motor movement for 36 hours
Parameter _SigLatched Bit 23
Cause: There has not been a minimum motor movement for the last 36 hours.



Remedy: There must be a minimum motor movement at least once every 36 hours.
7855

eSM module: System error detected: Timeout high-priority tests (5 sec)
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7856

eSM module: System error detected: Timeout low-priority tests
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7857

eSM module: Parameter dec_Qstop (minimum deceleration) is set to 0
Parameter _SigLatched Bit 23
Cause: Module is not configured.



Remedy: Download a configuration.
7858

eSM module: Output AUXOUT2 (cross fault to another output detected)
Parameter _SigLatched Bit 23
Cause: Cross fault detection detected a cross fault to another output.



Remedy: Verify wiring and connected devices.
7859

eSM module: Output /INTERLOCK_OUT (cross fault to another output detected)
Parameter _SigLatched Bit 23
Cause: Cross fault detection detected a cross fault to another output.



Remedy: Verify wiring and connected devices.
785A

eSM module: Output RELAY_OUT_B (cross fault to another output detected)
Parameter _SigLatched Bit 23
Cause: Cross fault detection detected a cross fault to another output.



Remedy: Verify wiring and connected devices.
785B

eSM module: Output CCM24V_OUT_B (cross fault to another output detected)
Parameter _SigLatched Bit 23
Cause: Cross fault detection detected a cross fault to another output.



Remedy: Verify wiring and connected devices.
785C

eSM module: Output AUXOUT2 (cross fault to 24 V detected)
Parameter _SigLatched Bit 23
Cause: Cross fault detection detected a cross fault to 24 V.



Remedy: Verify wiring and connected devices.
785D

eSM module: Output /INTERLOCK_OUT (cross fault to 24 V detected)
Parameter _SigLatched Bit 23
Cause: Cross fault detection detected a cross fault to 24 V.



Remedy: Verify wiring and connected devices.
785E

eSM module: Output RELAY_OUT_B (cross fault to 24 V detected)
Parameter _SigLatched Bit 23
Cause: Cross fault detection detected a cross fault to 24 V.



Remedy: Verify wiring and connected devices.
785F

eSM module: Output CCM24V_OUT_B (cross fault to 24 V detected)
Parameter _SigLatched Bit 23
Cause: Cross fault detection detected a cross fault to 24 V.



Remedy: Verify wiring and connected devices.
7861

eSM module: System error detected: Input ESMSTART_B
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7862

eSM module: System error detected: Input SETUPENABLE_B
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7863

eSM module: System error detected: Input SETUPMODE_B
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7864

eSM module: System error detected: Input GUARD_B
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7865

eSM module: System error detected: Input GUARD_ACK
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7866

eSM module: System error detected: Input /INTERLOCK_IN_B
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7867

eSM module: System error detected: Input /ESTOP_B
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
786A

eSM module: Undertemperature
Parameter _SigLatched Bit 23
Cause: Temperature of the eSM too low.



Remedy: Verify ambient conditions.
786C

eSM module: Overvoltage ESM24VDC
Parameter _SigLatched Bit 23
Cause: Voltage too high at the ESM24VDC.



Remedy: Verify power supply.
786D

eSM module: Overtemperature
Parameter _SigLatched Bit 23
Cause: Temperature too high.



Remedy: Verify the ambient conditions. Verify that the flow of air is sufficient (pollution, objects).
786E

eSM module: System error detected: Operating states not identical
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7870

eSM module: System error detected: Software versions not identical
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7871

eSM module: Error detected during Safe Operating Stop (SOS) after detected error
Parameter _SigLatched Bit 23
Cause: Motor movement during Safe Operating Stop (SOS).



Remedy: –
7872

eSM module: System error detected: Software incompatible with hardware
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7873

eSM module: Error detected during deceleration to Safely Limited Speed (SLS)
Parameter _SigLatched Bit 23
Cause: Velocity of drive greater than speed limit configured for eSM Safely Limited Speed (SLS).



Remedy: Verify speed limit and delay time for eSM Safely Limited Speed (SLS). Adapt the drive values for ramp and velocity, if necessary.
7874

eSM module: Repeated error detected during Safe Operating Stop (SOS)
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7875

eSM module: Repeated error detected during deceleration for Quick Stop
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7876

eSM module: /INTERLOCK_IN not high (timeout if t_Relay = 2)
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7877

eSM module: Input /INTERLOCK_IN is high even though Ignore has been configured
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7878

eSM module: Speed limit for machine operating mode Setup Mode higher than speed limit for machine operating mode Automatic Mode
Parameter _SigLatched Bit 23
Cause: Speed limit for machine operating mode Setup Mode must not be greater than speed limit for machine operating mode Automatic Mode.



Remedy: Verify the speed limits for machine operating modes Automatic Mode and Setup Mode and change them as required.
7879

eSM module: System error detected: Indeterminable state of eSM state machine
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
787A

eSM module: ESM24VDC undervoltage
Parameter _SigLatched Bit 23
Cause: Voltage at the ESM24VDC connector to low.



Remedy: Verify power supply.
787D

eSM module: System error detected: Asynchronous communication (UART/SPI)
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
787E

eSM module: System error detected: RAM (bit)
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
787F

eSM module: Encoder signal error detected
Parameter _SigLatched Bit 23
Cause: Encoder or encoder cable inoperative. Incorrect signal evaluation in drive.



Remedy: –
7880

eSM module: Indeterminable service
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7881

eSM module: Parameter does not exist
Parameter _SigLatched Bit 23
Cause: Parameter does not exist.



Remedy: Verify the parameter number.
7882

eSM module: System error detected: 3_3V overvoltage
Parameter _SigLatched Bit 23
Cause: Overvoltage in internal eSM power supply.



Remedy: –
7883

eSM module: System error detected: 3_3V undervoltage
Parameter _SigLatched Bit 23
Cause: Undervoltage in internal eSM power supply.



Remedy: –
7884

eSM module: System error detected: Temperature sensor
Parameter _SigLatched Bit 23
Cause: Temperature sensor for CPU_A or CPU_B does not work properly.



Remedy: –
7886

eSM module: No speed limit for negative direction set for direction-dependent SLS
Parameter _SigLatched Bit 23
Cause: Direction-dependent SLS is active, but no speed limit greater than 0 RPM has been specified in the parameter eSM_v_maxSetup or in parameter eSM_SLSnegDirS.



Remedy: Set a speed limit for direction-dependent SLS greater than 0 RPM in the parameter _eSM_v_maxSetup or in the parameter eSM_SLSnegDirS or deactivate direction-dependent SLS via the parameter eSM_FuncSwitches.
7887

eSM module: Speed limit for SLS in negative direction has been specified, but direction-dependant SLS has not been activated
Parameter _SigLatched Bit 23
Cause: Direction-dependent SLS is not active, but a speed limit for direction-dependent SLS in negative direction has been specified.



Remedy: Set the speed limit for direction-dependent SLS in negative direction in parameter eSM_SLSnegDirS to 0 RPM or activate direction-dependent SLS via the parameter eSM_FuncSwitches.
7889

eSM module: Order of speed limits for multiple SLS in positive direction is incorrect
Parameter _SigLatched Bit 23
Cause: The values for the speed limits for multiple SLS are not in ascending order.



Remedy: Set correct speed limits for multiple SLS.
788A

eSM module: Order of speed limits for multiple SLS in negative direction is incorrect
Parameter _SigLatched Bit 23
Cause: The values for the speed limits for multiple SLS are not in ascending order.



Remedy: Set correct speed limits for multiple SLS.
788B

eSM module: Invalid speed limit for multiple SLS in positive direction
Parameter _SigLatched Bit 23
Cause: Speed limit for multiple SLS in positive direction has a value of zero.



Remedy: Set a speed limit not equal to zero for multiple SLS.
788C

eSM module: Invalid speed limit for multiple SLS in negative direction has a value of zero
Parameter _SigLatched Bit 23
Cause: Speed limit for multiple SLS in negative direction has a value of zero.



Remedy: Set a speed limit not equal to zero for multiple SLS.
788D

eSM module: Two types of multiple SLS selected at the same time
Parameter _SigLatched Bit 23
Cause: eSM module: Two types of multiple SLS selected at the same time.



Remedy: Select a single type of multiple SLS.
7900

Module in fieldbus slot not correctly detected
Parameter _SigLatched Bit 21
Cause: Fieldbus module not correctly mounted in the slot.
Unsupported fieldbus module inserted.
Fieldbus module inoperative.
EMI.



Remedy: Replace fieldbus module.
Improve EMC.
7901

Indeterminable type of fieldbus module detected in fieldbus slot
Parameter _SigLatched Bit 21
Cause: The type of module detected in fieldbus slot is not supported by the drive.



Remedy: Use supported type of fieldbus module. Refer to manual or catalog.
7903

Fieldbus module in slot 3 missing
Parameter _SigLatched Bit 21
Cause: Fieldbus module has been removed or fieldbus module is inoperative.



Remedy: Confirm or cancel HMI dialog box for fieldbus module replacement.
Install a new fieldbus module.
7904

Parameter access error detected in fieldbus module
Cause: Fieldbus module parameter does not exist or cannot be written.



Remedy: –
7905

Fieldbus module in slot 3 has been changed
Parameter _SigLatched Bit 21
Cause: The fieldbus module has been replaced by another type of fieldbus module.



Remedy: Confirm the new fieldbus module via the HMI dialog.
7906

Internal timeout in communication with fieldbus module
Cause: Internal communication with fieldbus module not correct.
Fieldbus module inoperative.
EMI.



Remedy: Replace fieldbus module.
Improve EMC.
7907

The module detected in the slot for fieldbus modules slot is not supported.
Parameter _SigLatched Bit 21
Cause: The module detected in the slot for fieldbus modules is not supported by older drive hardware revisions.



Remedy: –
7A05

Module IOM1: System error detected: Calibration analog/digital converter during manufacturing
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7A06

Module IOM1: System error detected: Initialization
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7A07

Module IOM1: System error detected: Nonvolatile memory read error detected, CRC does not match
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7A08

Module IOM1: System error detected: Nonvolatile memory write error detected
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7A09

Module IOM1: System error detected: Nonvolatile memory erase error detected
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7A0A

Module IOM1: System error detected: Incorrect flash API implemented
Parameter _SigLatched Bit 23
Cause: –



Remedy: –
7A0B

Module IOM1: Overtemperature
Parameter _WarnLatched Bit 23
Cause: Device cooling not sufficient.
Cooling fan inoperative.
Ambient temperature too high.



Remedy: Verify fan and ambient temperature.
7A0C

Module IOM1: Overtemperature
Parameter _SigLatched Bit 23
Cause: Device cooling not sufficient.
Cooling fan inoperative.
Ambient temperature too high.



Remedy: Verify fan and ambient temperature.
7A0D

Module IOM1: Module not available
Parameter _SigLatched Bit 23
Cause: The module IOM1 was not detected when the operating mode Profile Velocity or Profile Torque with reference value via analog input was activated.
The module IOM1 has been removed when the device was off.



Remedy: Insert the module IOM1.
7A0E

Module IOM1: Inoperative
Parameter _SigLatched Bit 23
Cause: Module IOM1 inoperative.
Hardware interface to the module IOM1 inoperative.



Remedy: –
7A0F

Module IOM1: Inoperative
Parameter _SigLatched Bit 23
Cause: Module IOM1 inoperative.
Hardware interface to the module IOM1 inoperative.



Remedy: –
7A10

Module IOM1: Inoperative
Parameter _SigLatched Bit 23
Cause: Module IOM1 inoperative.
Hardware interface to the module IOM1 inoperative.



Remedy: –
7A11

Module IOM1: Inoperative
Parameter _SigLatched Bit 23
Cause: Module IOM1 inoperative.
Hardware interface to the module IOM1 inoperative.



Remedy: –
7A12

Module IOM1: Module IOM1 required for velocity or torque limitation via analog input
Parameter _SigLatched Bit 23
Cause: Velocity or torque limitation via analog input has been activated, but the module IOM1 has not been inserted.



Remedy: Insert the module IOM1 or deactivate the velocity or torque limitation setting via the analog input.
7A13

Module IOM1: Overload or short circuit at analog output
Parameter _SigLatched Bit 23
Cause: Overload or shot circuit at one of the analog outputs.



Remedy: Verify wiring and connected load.
7A14

Module IOM1: Module IOM1 not supported in combination with PROFINET fieldbus module
Parameter _SigLatched Bit 23
Cause: The module IOM1 is not supported if the PROFINET fieldbus module is used.



Remedy: –
8110

CANopen: Overflow internal receive queue (message lost)
Parameter _WarnLatched Bit 21
Cause: Two short CAN messages have been sent too fast (at 1 Mbits only).



Remedy: –
8120

CANopen: CAN Controller in state Error Passive
Parameter _WarnLatched Bit 21
Cause: Too many error frames have been detected.



Remedy: Verify CAN bus installation.
8130

CANopen: Detected Heartbeat or Life Guard error
Parameter _SigLatched Bit 21
Cause: The bus cycle time of the CANopen master is longer than the programmed heartbeat or node guarding time.



Remedy: Verify the CANopen configuration, increase the heartbeat or node guarding time.
8131

CANopen: Detected Heartbeat or Life Guard error
Parameter _WarnLatched Bit 21
Cause: –



Remedy: –
8140

CANopen: CAN controller was in state ‘bus-off’, communication is possible again
Parameter _WarnLatched Bit 21
Cause: –



Remedy: –
8141

CANopen: CAN controller is in state ‘bus-off’
Parameter _SigLatched Bit 21
Cause: Too many error frames have been detected, CAN devices with different baud rates.



Remedy: Verify CAN bus installation.
8142

CANopen: CAN controller is in state ‘bus-off’
Parameter _WarnLatched Bit 21
Cause: Too many error frames have been detected, CAN devices with different baud rates.



Remedy: Verify CAN bus installation.
8281

CANopen: RxPDO1 could not be processed
Parameter _WarnLatched Bit 21
Cause: Error detected while processing Receive PDO1: PDO1 contains invalid value.



Remedy: Verify RxPDO1 content (application).
8282

CANopen: RxPDO2 could not be processed
Parameter _WarnLatched Bit 21
Cause: Error detected while processing Receive PDO2: PDO2 contains invalid value.



Remedy: Verify RxPDO2 content (application).
8283

CANopen: RxPDO3 could not be processed
Parameter _WarnLatched Bit 21
Cause: Error detected while processing Receive PDO3: PDO3 contains invalid value.



Remedy: Verify RxPDO3 content (application).
8284

CANopen: RxPDO4 could not be processed
Parameter _WarnLatched Bit 21
Cause: Error detected while processing Receive PDO4: PDO4 contains invalid value.



Remedy: Verify RxPDO4 content (application).
8291

CANopen: TxPdo could not be processed
Parameter _WarnLatched Bit 21
Cause: –



Remedy: –
8292

CANopen: TxPdo could not be processed
Parameter _WarnLatched Bit 21
Cause: –



Remedy: –
8293

CANopen: TxPdo could not be processed
Parameter _WarnLatched Bit 21
Cause: –



Remedy: –
8294

CANopen: TxPdo could not be processed
Parameter _WarnLatched Bit 21
Cause: –



Remedy: –
82A0

CANopen: Initialization CANopen stack
Parameter _WarnLatched Bit 21
Cause: –



Remedy: –
82A1

CANopen: Overflow internal transmit queue (message lost)
Parameter _WarnLatched Bit 21
Cause: –



Remedy: –
82B1

CANopen: The data tunneling protocol is not Modbus RTU
Parameter _WarnLatched Bit 21
Cause: –



Remedy: –
82B2

CANopen: Data frame is still being processed
Parameter _WarnLatched Bit 21
Cause: A new data frame was written but the previous data frame is still being processed.



Remedy: Write the data frame again later on.
A060

Calculated velocity too high for operating mode Electronic Gear
Parameter _SigLatched Bit 4
Cause: Gear ratio or reference velocity value too high.



Remedy: Reduce the gear ratio or reference velocity.
A061

Position change in reference value for operating mode Electronic Gear too high
Parameter _SigLatched Bit 4
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

Parameters cannot be written
Parameter _WarnLatched Bit 4
Cause: A data set is still active.



Remedy: Wait until the currently active data set has been terminated.
A066

Teach-in position cannot be accepted
Parameter _WarnLatched Bit 4
Cause: Data set type is not ‘MoveAbsolute’.



Remedy: Set the data set type to ‘MoveAbsolute’.
A067

Invalid value in data set. Additional information in the error memory indicates the data set number (low byte) and entry (high byte).
Parameter _SigLatched Bit 4
Cause: Value not possible in data set.



Remedy: See also parameters _MSM_error_num and _MSM_error_entry for additional information.
A068

Offset positioning not possible
Parameter _WarnLatched Bit 4
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
Parameter _WarnLatched Bit 4
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
Parameter _SigLatched Bit 4
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
Parameter _SigLatched Bit 1
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
Parameter _SigLatched Bit 1
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.
A304

Stop by reference switch
Parameter _SigLatched Bit 1
Cause: –



Remedy: –
A305

Power stage cannot be enabled in the operating state Not Ready To Switch On
Cause: Fieldbus: An attempt was made to enable the power stage in the operating state Not Ready To Switch On.



Remedy: Refer to the state diagram.
A306

Stop by user-initiated software stop
Parameter _SigLatched Bit 3
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, the error code is sent as the response to the activation command.



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, 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: Wait until the operating mode change has terminated before triggering a start request for another operating mode.
A312

Profile generation interrupted
Cause: –



Remedy: –
A313

Position overflow, zero point is therefore no longer valid (ref_ok=0)
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.
A314

No valid zero point
Cause: Command needs a valid zero point (ref_ok=1).



Remedy: Define a valid zero point by means of the operating mode Homing.
A315

Homing active
Cause: Command cannot be used while the operating mode Homing is active.



Remedy: Wait until reference movement is finished.
A316

Overflow during calculation of acceleration
Cause: –



Remedy: –
A317

Motor is not at a standstill
Cause: Command sent which is not permissible when the motor is not at a standstill. For example: Change of software limit switches, Change of handling of monitoring signals, Setting of reference point, Teach in of data set.



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
Parameter _SigLatched Bit 2
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 CTRL_v_max, M_n_max)
Cause: The velocity was set to a value greater than the maximum permissible velocity in parameter CTRL_v_max or M_n_max, whichever is lower.



Remedy: If the value of parameter M_n_max is greater than the value of parameter CTRL_v_max, increase the value of parameter CTRL_v_max or reduce the velocity value.
A31E

Stop by positive software limit switch
Parameter _SigLatched Bit 2
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
Parameter _SigLatched Bit 2
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
Parameter _SigLatched Bit 8
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 ErrorResp_p_dif.
A321

Invalid setting for RS422 position interface
Cause: –



Remedy: –
A322

Error detected in ramp calculation
Cause: –



Remedy: –
A323

System error detected: Processing error detected during generation of profile
Cause: –



Remedy: –
A324

Error detected during homing. Additional information in the error memory indicates the detailed error code.
Parameter _SigLatched Bit 4
Cause: Homing movement was stopped in response to a detected error, the detailed reason is indicated by the additional info in the error memory.



Remedy: Possible sub-error codes: A325, A326, A327, A328 or A329.
A325

Limit switch to be approached not enabled
Parameter _SigLatched Bit 4
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
Parameter _SigLatched Bit 4
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
Parameter _SigLatched Bit 4
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
Parameter _SigLatched Bit 4
Cause: Start reference movement with negative direction (for example, reference movement to negative limit switch) 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 (target limit switch must be connected to the negative limit switch).
A32B

Negative limit switch triggered with positive direction of movement
Parameter _SigLatched Bit 4
Cause: Start reference movement with positive direction (for example, reference movement to positive limit switch) 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 (target limit switch must be connected to the positive limit switch).
A32C
Reference switch error detected (switch signal briefly enabled or switch overtraveled)
Parameter _SigLatched Bit 4
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)
Parameter _SigLatched Bit 4
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)
Parameter _SigLatched Bit 4
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
Parameter _SigLatched Bit 4
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. Index pulse is too close to the switch
Parameter _WarnLatched Bit 4
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 information in the error memory indicates the detailed error code.
Parameter _SigLatched Bit 4
Cause: Jog movement was stopped in response to a detected error.



Remedy:

  • For additional info, verify the detailed error code in the error memory.
A333
System error detected: Invalid internal selection
Cause: –



Remedy:

  • –
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 MON_p_win, MON_p_winTime and MON_p_winTout).

  • Optimize control loop settings.
A336
System error detected: Jerk limitation with position offset after end of movement.
Additional information in the error memory indicates the offset in Increments.
Cause: –



Remedy:

  • –
A337
Operating mode cannot be continued
Parameter _WarnLatched Bit 4
Cause: Continuation of interrupted movement in operating mode Profile Position is not possible because another operating mode had been active in the meantime. In the operating mode Motion Sequence, continuation is not possible if a motion blend was interrupted.



Remedy:

  • Restart the operating mode.
A338
Operating mode unavailable
Parameter _WarnLatched Bit 4
Cause: The selected operating mode is not available.



Remedy:

  • –
A339
No processing of motor encoder selected or position capture of motor index pulse active
Parameter _WarnLatched Bit 4
Cause: –



Remedy:

  • –
A33A
No valid zero point (ref_ok=0)
Parameter _WarnLatched Bit 4
Cause: No zero point defined by means of operating mode Homing. Zero point no longer valid due to movement beyond permissible movement range. Motor does not have an absolute encoder.



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
Parameter _WarnLatched Bit 4
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:

  • –
A33D
Motion blend is already active
Parameter _WarnLatched Bit 4
Cause: Change of motion blend during the ongoing motion blend (end position of motion blend not yet reached).



Remedy:

  • Wait for the motion blend to complete before setting the next position.
A33E
No movement activated
Parameter _WarnLatched Bit 4
Cause: Activation of a motion blend without movement.



Remedy:

  • Start a movement before the motion blend is activated.
A33F
Position of motion blend movement not in the range of the ongoing movement
Parameter _WarnLatched Bit 4
Cause: The position of the motion blend is outside of the movement range.



Remedy:

  • Verify the position of the motion blend and the movement range.
A340
Error detected in operating mode Motion Sequence
Parameter _SigLatched Bit 4
Cause: The operating mode Motion Sequence was stopped in response to a detected error. Verify the error memory for details on the detected error.



Remedy:

  • See the additional error information.
A341
Position of motion blend has already been passed
Parameter _WarnLatched Bit 4
Cause: The movement has passed beyond the position of the motion blend.



Remedy:

  • –
A342
Target velocity was not reached at motion blend position
Parameter _SigLatched Bit 4
Cause: The position of the motion blend was overtraveled, the target velocity was not reached.



Remedy:

  • Reduce the ramp velocity so that the target velocity is reached at the position of the motion blend.
A343
Processing only possible with linear ramp
Parameter _WarnLatched Bit 4
Cause: Motion blend position was set with a non-linear ramp.



Remedy:

  • Set a linear ramp.
A344
Maximum position deviation between motor encoder and machine encoder exceeded
Parameter _SigLatched Bit 8
Cause: Incorrect or inoperative encoder cable. Machine encoder not connected or not supplied correctly. Different counting directions of motor encoder and machine encoder. Incorrect setting of resolution factors (numerator or denominator) of machine encoder.



Remedy:

  • Verify encoder connection.

  • Verify parameterization of machine encoder.
A347
Permissible position deviation exceeded
Parameter _WarnLatched Bit 8
Cause: External load or acceleration are too high.



Remedy:

  • Reduce external load or acceleration.

  • Threshold value can be adjusted via the parameter MON_p_dif_warn.
A348
No analog reference value source selected
Parameter _SigLatched Bit 4
Cause: No analog reference value selected.



Remedy:

  • Select an analog reference value source.
A349
Position setting exceeds system limits
Cause: Position scaling of POSscaleDenom and POSscaleNum results in a scaling factor that is too small.



Remedy:

  • Change POSscaleDenom and POSscaleNum in such a way as to increase the resulting scaling factor.
A34A
Velocity setting exceeds system limits
Cause: The velocity scaling of ‘VELscaleDenom’ and ‘VELscaleNum’ results in a scaling factor that is too small. The velocity has been set to a value greater than the maximum possible velocity (the maximum velocity is 13200 RPM).



Remedy:

  • Change ‘VELscaleDenom’ and ‘VELscaleNum’ in such a way as to increase the resulting scaling factor.
A34B
Ramp setting exceeds system limits
Cause: The ramp scaling of ‘RAMPscaleDenom’ and ‘RAMPscaleNum’ results in a scaling factor that is too small.



Remedy:

  • Change of ‘RAMPscaleDenom’ and ‘RAMPscaleNum’ in such a way as to increase the resulting scaling factor.
A34C
Resolution of scaling too high (range exceeded)
Cause: –



Remedy:

  • –
A34D
Function not available when Modulo is active
Cause: The function cannot be executed when Modulo is active.



Remedy:

  • Deactivate Modulo to use the function.
A34E
Target value for absolute movement not possible with defined modulo range and modulo handling
Cause: If parameter ‘MOD_Absolute’ is set to: Shortest Distance: Target value is not in defined modulo range. Positive Direction: Target value is less than parameter ‘MOD_Min’. Negative Direction: Target value is greater than parameter ‘MOD_Max’.



Remedy:

  • Set a correct target value for absolute movement.
A34F
Target position outside of modulo range. Corresponding movement within range performed instead.
Cause: The setting of parameter ‘MOD_AbsMultiRng’ only allows for a movement within the modulo range.



Remedy:

  • Change the parameter ‘MOD_AbsMultiRng’ to allow for movements beyond the modulo range.
A350
Change for jerk filter input position too great
Parameter _SigLatched Bit 4
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
Parameter _SigLatched Bit 4
Cause: The positions scaling factor is set to a value less than 1rev/131072usr_p, which is less than the internal resolution. In the operating mode Cyclic Synchronous Position, the resolution is not set to 1rev/131072usr_p.



Remedy:

  • Use a different position scaling factor or deactivate the selected function.
A352
Position list active
Cause: –



Remedy:

  • –
A353
Position list not sorted
Cause: –



Remedy:

  • –
A354
Position list does not match the configuration of the Modulo range
Cause: –



Remedy:

  • –
A355
Error detected during relative movement after capture
Parameter _SigLatched Bit 4
Cause: Movement was stopped by error.



Remedy:

  • Verify the error memory.
A356
Function Relative Movement After Capture not assigned to a digital input
Cause: –



Remedy:

  • Assign the function Relative Movement After Capture to a digital input.
A357
Deceleration still running
Cause: Command is not permissible during deceleration.



Remedy:

  • Wait until motor has come to a complete standstill.
A358
Target position overtraveled with function Relative Movement After Capture
Parameter _SigLatched Bit 4
Cause: Stopping distance too small or velocity too high at the point in time of the capture event.



Remedy:

  • Reduce the velocity.
A359
Request cannot be processed since the relative movement after capture is still active
Cause: –



Remedy:

  • –
A35A
Selected data set cannot be started
Parameter _SigLatched Bit 4
Cause: The data set with the selected number is not available.



Remedy:

  • Verify the number of the data set.
A35B
Modulo cannot be activated
Parameter _WarnLatched Bit 4
Cause: The set operating mode does not support Modulo.



Remedy:

  • –
A35D
Permissible velocity deviation exceeded
Parameter _SigLatched Bit 8
Cause: Load or acceleration too high.



Remedy:

  • Reduce load or acceleration.
A35E
The selected velocity scaling factor reduces the accuracy of the velocity scaling.
Cause: –



Remedy:

  • Increase or decrease the value of the numerator and/or denominator of the scaling factor.

  • If the condition persists, contact your Schneider Electric service representative.
A35F
The selected ramp scaling factor reduces the accuracy of the ramp scaling.
Cause: –



Remedy:

  • Increase or decrease the value of the numerator and/or denominator of the scaling factor.

  • If the condition persists, contact your Schneider Electric service representative.
B100
RS485/Modbus: Indeterminable service
Parameter _WarnLatched Bit 5
Cause: Unsupported Modbus service was received.



Remedy:

  • Verify application on the Modbus master.
B101
Incorrect I/O data configuration
Parameter _SigLatched Bit 21
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.
B102
Fieldbus module: General error detected
Parameter _SigLatched Bit 21
Cause: –



Remedy:

  • –
B103
Fieldbus module: Controlling communication channel has been closed
Parameter _SigLatched Bit 21
Cause: –



Remedy:

  • –
B104
Fieldbus module: Internal communication error detected
Parameter _SigLatched Bit 21
Cause: –



Remedy:

  • –
B105
Fieldbus module: I/O data timeout
Parameter _SigLatched Bit 21
Cause: –



Remedy:

  • –
B106
Fieldbus module: I/O data mapping error detected
Parameter _SigLatched Bit 21
Cause: –



Remedy:

  • –
B107
Fieldbus module: Nonvolatile memory error detected in module
Parameter _SigLatched Bit 21
Cause: –



Remedy:

  • –
B108
Fieldbus module: Active IOC physical layer does not match the IOC physical layer of the detected fieldbus module
Parameter _SigLatched Bit 21
Cause: The manufacturer data has been stored with a physical layer different from the physical layer normally used by the module.



Remedy:

  • Contact your Schneider Electric service representative.
B120
Cyclic communication: Incorrect cycle time
Parameter _SigLatched Bit 21
Cause: The drive does not support the configured cycle time or the difference between the measured cycle time and the configured cycle time is too great.



Remedy:

  • Change the cycle time in the master controller to a cycle time supported by the drive or verify synchronization requirements.
B121
Cyclic communication: Synchronization signal missing
Parameter _SigLatched Bit 21
Cause: Two cycles have passed without a synchronization signal having been received.



Remedy:

  • Analyze the communication.
B122
Cyclic communication: Incorrect synchronization
Parameter _SigLatched Bit 21
Cause: One signal was missing and the expected second signal was received at an incorrect point in time. The master controller may be unable to provide the required synchronization signals at the set cycle time, for example, due to insufficient computing power.



Remedy:

  • Analyze the communication or increase the cycle time.
B123
Cyclic communication: The selected cycle time tolerance is too high
Parameter _SigLatched Bit 21
Cause: The cycle time tolerance may not exceed one quarter of the set cycle time.



Remedy:

  • Enter a correct value.
B124
Cyclic Communication: Drive is not synchronous with master cycle
Parameter _WarnLatched Bit 21
Cause: Operating mode has been activated but drive is not synchronized to external synchronization signal.



Remedy:

  • After having started the synchronization mechanism, wait for 120 cycles before activating the operating mode.
B200
RS485/Modbus: Protocol error detected
Parameter _WarnLatched Bit 5
Cause: Logical protocol error detected: Incorrect length or unsupported subfunction.



Remedy:

  • Verify application on the Modbus master.
B201
RS485/Modbus: Interruption of the connection
Parameter _SigLatched Bit 5
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
Parameter _WarnLatched Bit 5
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
Parameter _WarnLatched Bit 5
Cause: –



Remedy:

  • –
B312
Profibus: Clear command with error response
Parameter _SigLatched Bit 21
Cause: Clear command sent by master, detected bus error.



Remedy:

  • Verify the application.
B314
Watchdog error with error response
Parameter _SigLatched Bit 21
Cause: The bus cycle time is greater than the programmed watchdog time.



Remedy:

  • Increase watchdog time.
B316
Communication error detected with error response
Parameter _SigLatched Bit 21
Cause: Detected system or bus error, EMI.



Remedy:

  • Verify fieldbus connection, shield connection.
B400
CANopen: NMT reset with power stage enabled
Parameter _SigLatched Bit 21
Cause: NMT Reset command is received while drive is in operating state Operation Enabled.



Remedy:

  • Disable the power stage before sending a NMT reset command.
B401
CANopen: NMT stop with power stage enabled
Parameter _SigLatched Bit 21
Cause: NMT Stop command is received while drive is in operating state Operation Enabled.



Remedy:

  • Disable the power stage before sending a NMT Stop command.
B402
CAN PLL active
Parameter _WarnLatched Bit 21
Cause: An attempt has been made to start the synchronization mechanism, but the synchronization mechanism was already active.



Remedy:

  • Deactivate the synchronization mechanism.
B403
Excessive Sync period deviation
Parameter _SigLatched Bit 21
Cause: The period time of the SYNC signals is not stable. The deviation is more than 100 usec.



Remedy:

  • The SYNC signals of the motion controller must be more accurate.
B404
Sync signal error detected
Parameter _SigLatched Bit 21
Cause: SYNC signal missed more than twice.



Remedy:

  • Verify CAN connection, verify motion controller.
B405
Drive could not be adapted to master cycle
Parameter _SigLatched Bit 21
Cause: The jitter of the SYNC object is too great or the motion bus requirements are not taken into account.



Remedy:

  • Verify the timing requirements regarding interpolation time period and number of devices.
B406
Baud rate is not supported
Parameter _WarnLatched Bit 21
Cause: The configured baud rate is not supported.



Remedy:

  • Choose one of the following baud rates: 250 kB, 500 kB, 1000 kB.
B407
Drive is not synchronous with master cycle
Parameter _WarnLatched Bit 21
Cause: The operating mode ‘Cyclic Synchronous Mode’ cannot be activated as long as the drive is not synchronized.



Remedy:

  • Verify motion controller.

  • To be synchronized, the motion controller must cyclically send SYNC signals.
B500
DeviceNet: IO data could not be processed
Parameter _WarnLatched Bit 21
Cause: Error detected while processing I/O data: Output data contains invalid value.



Remedy:

  • Verify output data content (application).
B501
DeviceNet: Duplicate MAC ID
Parameter _SigLatched Bit 21
Cause: There is a device with the same MAC ID on the DeviceNet bus.



Remedy:

  • Use another MAC ID for this device or for the other device.
B502
DeviceNet: Receive queue overrun
Parameter _SigLatched Bit 21
Cause: –



Remedy:

  • –
B503
DeviceNet: Transmit queue overrun
Parameter _SigLatched Bit 21
Cause: –



Remedy:

  • –
B504
DeviceNet: Error detected while sending an I/O message
Parameter _SigLatched Bit 21
Cause: –



Remedy:

  • –
B505
DeviceNet: CAN controller in state bus-off
Parameter _SigLatched Bit 21
Cause: Too many error frames have been detected, CAN devices with different baudrates.



Remedy:

  • Verify CAN bus installation.
B506
DeviceNet: CAN overflow (message lost)
Parameter _SigLatched Bit 21
Cause: Two short DeviceNet messages have been sent too fast.



Remedy:

  • –
B507
DeviceNet: Reset request, change of baud rate or MAC ID
Parameter _SigLatched Bit 21
Cause: Master sent DeviceNet reset request while the power stage was enabled.



Remedy:

  • Reset the device only while the power stage is disabled.
B508
DeviceNet: Power supply disabled
Parameter _SigLatched Bit 21
Cause: DeviceNet bus power supply was powered off while the power stage was enabled.



Remedy:

  • Disable the power stage before powering off the DeviceNet master.
B509
DeviceNet: Timeout explicit connection
Parameter _SigLatched Bit 21
Cause: –



Remedy:

  • –
B50A
DeviceNet: Timeout I/O connection
Parameter _SigLatched Bit 21
Cause: –



Remedy:

  • –
B50B
DeviceNet: Explicit connection terminated while operating state was Operation Enabled
Parameter _SigLatched Bit 21
Cause: An explicit connection was terminated while no I/O channel was open and the power stage was enabled.



Remedy:

  • If you use explicit connections only, disable the power stage before terminating the connection.
B50C
DeviceNet: I/O connection terminated while operating state was Operation Enabled
Parameter _SigLatched Bit 21
Cause: An I/O connection was terminated while the power stage was enabled.



Remedy:

  • Disable the power stage before terminating the I/O connection.
B600
Ethernet: Network overload
Parameter _SigLatched Bit 21
Cause: –



Remedy:

  • –
B601
Ethernet: Loss of Ethernet carrier
Parameter _SigLatched Bit 21
Cause: –



Remedy:

  • –
B602
Ethernet: Duplicate IP address
Parameter _SigLatched Bit 21
Cause: –



Remedy:

  • –
B603
Ethernet: No valid IP address
Parameter _SigLatched Bit 21
Cause: –



Remedy:

  • –
B604
Ethernet: DHCP/BOOTP
Parameter _WarnLatched Bit 21
Cause: IP assignment via DHCP/BOOTP unsuccessful. Effort was given up after 2 minutes.



Remedy:

  • Set up a properly working DHCP or BOOTP server or assign the IP address manually.
B605
Ethernet FDR: Unconfigured error detected
Parameter _SigLatched Bit 21
Cause: –



Remedy:

  • –
B606
Ethernet FDR: Irrecoverable error detected
Parameter _SigLatched Bit 21
Cause: –



Remedy:

  • –
B607
Ethernet: I/O data idle
Parameter _SigLatched Bit 21
Cause: Controller has been stopped, but I/O data keeps being transmitted.



Remedy:

  • Disable power stage of connected drives before stopping the controller.
B610
EtherCAT: Fieldbus watchdog. Additional information in the error memory indicates the detailed error code.
Parameter _SigLatched Bit 21
Cause: EtherCAT frames are lost, for example, due to inoperative cables or errors caused by the master.



Remedy:

  • Verify correct cabling and shield connection.

  • Verify diagnostics info of EtherCAT master.
B611
EtherCAT: Invalid I/O data. Additional information in the error memory indicates the Modbus address.
Parameter _SigLatched Bit 21
Cause: Incorrect input data or output data (such as object length, object type).



Remedy:

  • Verify correct PDO configuration (length, objects, etc.).
B612
EtherCAT: Link lost at input and output port
Parameter _SigLatched Bit 21
Cause: EtherCAT cable. Link to connected devices lost.



Remedy:

  • Verify link LEDs.

  • Verify cables and that the devices connected to input port and output port operate.

  • Use EtherCAT master diagnostics for further troubleshooting.
B613
Ethernet: Ethernet carrier port 2 not available
Parameter _SigLatched Bit 21
Cause: –



Remedy:

  • –
B614
EtherCAT: General error detected. Additional information in the error memory indicates the detailed error code.
Parameter _SigLatched Bit 21
Cause: –



Remedy:

  • –
B700
Drive Profile Lexium: On activation of the profile, no dmControl, refA or refB has been mapped.
Cause: dmControl, refA or refB have not been mapped.



Remedy:

  • Map dmControl, refA or refB.
B702
Insufficient velocity resolution due to velocity scaling
Cause: Due to the configured velocity scaling, the velocity resolution in REFA16 is insufficient.



Remedy:

  • Change the velocity scaling.
B703
Drive Profile Lexium: Write request with incorrect data type.
Cause: –



Remedy:

  • –
init

Operating state 1 Start
Cause:

The device is in the initialization phase (Operating state 1).



Remedy:

Wait for the initialization to complete.
nrdy

Operating state 2 Not Ready To Switch On
Cause:

Device is not ready to switch on (Operating state 2).



Remedy:

Check DC bus voltage or enable signals if the state persists.
dis

Operating state 3 Switch On Disabled
Cause:

Switch on is disabled (Operating state 3).



Remedy:

Check enable inputs and safety modules if applicable.
rdy

Operating state 4 Ready To Switch On
Cause:

Device is ready to switch on (Operating state 4).



Remedy:

Command the drive to switch on.
son

Operating state 5 Switched On
Cause:

The power stage is switched on (Operating state 5).



Remedy:

None required; normal operation.
run and halt

Operating state 6 Operation Enabled
Cause:

Operation is enabled (Operating state 6).



Remedy:

None required; normal operation.
stop

Operating state 7 Quick Stop Active
Cause:

Quick Stop is currently active (Operating state 7).



Remedy:

Check the stop command source or safety inputs.
flt

Operating state 8 Fault Reaction Active and 9 Fault
Cause:

A fault has occurred and the reaction is active.



Remedy:

Check specific fault code (if available) and reset the drive.
Card

Memory Card Data Mismatch
Cause:

Data on the memory card differs from data in the product.



Remedy:

See Memory Card section (page 174) for information on how to proceed.
disp

External HMI Connected
Cause:

An external HMI is connected. The integrated HMI has no function.



Remedy:

Use the external HMI for operation.
fsu

First Setup Required
Cause:

Device requires a First Setup.



Remedy:

Perform a First Setup. See “Powering on the Device for the First Time” (page 141).
mot

New motor detected
Cause:

A new motor was detected.



Remedy:

See section “Acknowledging a Motor Change” (page 394) for replacing a motor.
prot

HMI Locked
Cause:

Parts of the integrated HMI were locked with the parameter HMIlocked.



Remedy:

Unlock the HMI using the appropriate software or parameter settings.
slt1 … slt3

Module Equipment Mismatch
Cause:

The device has detected a different equipment with modules.



Remedy:

See section “Acknowledging a Module Replacement” (page 394) for replacing modules.
ulow

24 Vdc control supply low
Cause:

24 Vdc control supply during initialization was not high enough.



Remedy:

Check the 24 Vdc power supply unit and wiring.
8888

Undervoltage 24 Vdc
Cause:

Undervoltage on the 24 Vdc control supply.



Remedy:

Verify the voltage level of the 24 Vdc control supply.
wdog

System Watchdog Error
Cause:

Undeterminable system error.



Remedy:

Contact your Schneider Electric representative.
—-

Firmware not available
Cause:

Firmware is not available or corrupted.



Remedy:

Retry to flash the firmware. If the condition persists, contact your Schneider Electric representative.