Schneider ATV340 Drives

Schneider ATV340 Drives Fault Codes:

Fault Code and MeaningCause and Remedy
NOA

[No Warning stored]
Cause: No warning stored.



Remedy:

  • No action required.
FRF

[Fallback Frequency]
Cause: Reaction on event: Fallback frequency.



Remedy:

  • Check fallback configuration settings.
RLS

[Speed Maintained]
Cause: Reaction on event: Speed maintained.



Remedy:

  • Check event reaction settings.
STT

[Type of stop]
Cause: Reaction on event: Stop following [Type of stop] STT without triggering an error.



Remedy:

  • Verify stop configuration and event triggers.
SRA

[Ref Frequency Warning]
Cause: Frequency reference reached.



Remedy:

  • Information only; verify system reference.
PEE

[PID error Warning]
Cause: PID error warning.



Remedy:

  • Check PID gain settings and feedback loop.
PFA

[PID Feedback Warn]
Cause: PID feedback warning.



Remedy:

  • Check feedback signal integrity.
PFAH

[PID High Fdbck Warn]
Cause: PID feedback high threshold reached.



Remedy:

  • Check for high feedback signal levels.
PFAL

[PID Low Fdbck Warn]
Cause: PID feedback low threshold reached.



Remedy:

  • Check for signal loss or low feedback levels.
LSA

[Limit Switch Reached]
Cause: Limit switch reached.



Remedy:

  • Check mechanical limit switch position.
RSDA

[Slack Rope Warning]
Cause: Slack rope warning.



Remedy:

  • Check rope tension and mechanics.
DLDA

[Dynamic Load Warning]
Cause: Dynamic load warning.



Remedy:

  • Check load stability and dynamics.
TP3A

[AI3 Th Warning]
Cause: AI3 Thermal warning.



Remedy:

  • Check temperature at Analog Input 3.
TP4A

[AI4 Th Warning]
Cause: AI4 Thermal warning.



Remedy:

  • Check temperature at Analog Input 4.
TP5A

[AI5 Th Warning]
Cause: AI5 Thermal warning.



Remedy:

  • Check temperature at Analog Input 5.
AP1

[AI1 4-20 Warning]
Cause: AI1 4-20 mA loss warning.



Remedy:

  • Verify 4-20mA signal on Analog Input 1.
AP3

[AI3 4-20 Warning]
Cause: AI3 4-20 mA loss warning.



Remedy:

  • Verify 4-20mA signal on Analog Input 3.
AP4

[AI4 4-20 Warning]
Cause: AI4 4-20 mA loss warning.



Remedy:

  • Verify 4-20mA signal on Analog Input 4.
AP5

[AI5 4-20 Warning]
Cause: AI5 4-20 mA loss warning.



Remedy:

  • Verify 4-20mA signal on Analog Input 5.
THA

[Device Therm Warn]
Cause: Drive overheating warning.



Remedy:

  • Check drive cooling fans and ambient temperature.
TJA

[IGBT Thermal Warning]
Cause: IGBT thermal state warning.



Remedy:

  • Reduce load or check drive sizing.
FCTA

[Fan Counter Warning]
Cause: Fan counter speed warning.



Remedy:

  • Check fan operation and service life.
FFDA

[Fan Feedback Warning]
Cause: Fan feedback warning.



Remedy:

  • Check fan feedback connections and obstructions.
BOA

[BR Thermal Warning]
Cause: Braking resistor thermal warning.



Remedy:

  • Check braking resistor cooling and duty cycle.
EFA

[Ext. Error Warning]
Cause: External error warning.



Remedy:

  • Investigate external device status.
USA

[Undervoltage Warning]
Cause: Undervoltage warning.



Remedy:

  • Check mains supply voltage stability.
UPA

[Preventive UnderV Active]
Cause: Controlled stop threshold is reached.



Remedy:

  • Check power supply capacity during load peaks.
FTA

[Mot Freq High Thd]
Cause: Motor frequency high threshold 1 reached.



Remedy:

  • Verify motor speed matches process requirements.
FTAL

[Mot Freq Low Thd]
Cause: Motor frequency low threshold 1 reached.



Remedy:

  • Check for mechanical stalling or low reference.
FQLA

[Pulse Warn Thd Reached]
Cause: Pulse warning threshold reached.



Remedy:

  • Check pulse input configuration.
F2AL

[Mot Freq Low Thd 2]
Cause: Motor frequency low threshold 2 reached.



Remedy:

  • Check secondary frequency thresholds.
FLA

[High Speed Reached]
Cause: High speed reached warning.



Remedy:

  • Check max speed parameters.
RTAH

[Ref Freq High Thd reached]
Cause: Reference frequency high threshold reached.



Remedy:

  • Check control system reference signals.
RTAL

[Ref Freq Low Thd reached]
Cause: Reference frequency low threshold reached.



Remedy:

  • Check control system reference signals.
F2A

[2nd Freq Thd Reached]
Cause: Motor frequency high threshold 2 reached.



Remedy:

  • Check secondary frequency limits.
CTA

[Current Thd Reached]
Cause: Motor current high threshold reached.



Remedy:

  • Check for mechanical overload or jamming.
CTAL

[Low Current Reached]
Cause: Motor current low threshold reached.



Remedy:

  • Check for belt breakage or dry running.
TTHA

[High Torque Warning]
Cause: High torque threshold reached.



Remedy:

  • Check process load and mechanical coupling.
TTLA

[Low Torque Warning]
Cause: Low torque threshold reached.



Remedy:

  • Check for load decoupling or fluid loss.
ULA

[Process Undld Warning]
Cause: Process underload warning.



Remedy:

  • Inspect system for underload conditions.
OLA

[Process Overload Warning]
Cause: Overload warning.



Remedy:

  • Inspect system for overload conditions.
SSA

[Torque Limit Reached]
Cause: Torque limit reached.



Remedy:

  • Check torque limit parameters and load.
RTA

[Torque Control Warning]
Cause: Torque control warning.



Remedy:

  • Verify torque control mode settings.
TAD

[Dev Thermal reached]
Cause: Drive thermal threshold reached.



Remedy:

  • Clean heatsink and check fans.
TSA

[Motor Therm Thd reached]
Cause: Motor thermal threshold reached.



Remedy:

  • Check motor cooling and duty cycle.
TS2

[Mot2 Therm Thd reached]
Cause: Motor 2 thermal threshold reached.



Remedy:

  • Check Motor 2 cooling.
TS3

[Mot3 Therm Thd reached]
Cause: Motor 3 thermal threshold reached.



Remedy:

  • Check Motor 3 cooling.
TS4

[Mot4 Therm Thd reached]
Cause: Motor 4 thermal threshold reached.



Remedy:

  • Check Motor 4 cooling.
PTHA

[Power High Threshold]
Cause: Power high threshold reached.



Remedy:

  • Monitor system power consumption.
PTHL

[Power Low Threshold]
Cause: Power low threshold reached.



Remedy:

  • Monitor system power consumption.
CAS1

[Cust Warning 1]
Cause: Customer warning 1 active.



Remedy:

  • Check user-defined logic or inputs.
CAS2

[Cust Warning 2]
Cause: Customer warning 2 active.



Remedy:

  • Check user-defined logic or inputs.
CAS3

[Cust Warning 3]
Cause: Customer warning 3 active.



Remedy:

  • Check user-defined logic or inputs.
CAS4

[Cust Warning 4]
Cause: Customer warning 4 active.



Remedy:

  • Check user-defined logic or inputs.
CAS5

[Cust Warning 5]
Cause: Customer warning 5 active.



Remedy:

  • Check user-defined logic or inputs.
POWD

[Power Cons Warning]
Cause: Power consumption warning.



Remedy:

  • Inspect efficiency and power usage.
ANA

[Slipping warn]
Cause: Slipping warning.



Remedy:

  • Check belts and mechanical coupling.
BSA

[Load Mvt Warn]
Cause: Load movement warning.



Remedy:

  • Check load movement mechanics.
BCA

[Brake Cont Warn]
Cause: Brake contact warning.



Remedy:

  • Check brake contactor state.
TP1A

[AI1 Th Warning]
Cause: AI1 Thermal warning.



Remedy:

  • Check temperature at Analog Input 1.
TLOW

[Current Reduc Warn]
Cause: Current reduction warning.



Remedy:

  • Check load or current limit settings.
MSDA

[M/S Device Warn]
Cause: Master/Slave device warning.



Remedy:

  • Verify Master/Slave communications.
BSQA

[Backlash Warn]
Cause: Backlash warning.



Remedy:

  • Check mechanical gears/coupling for backlash.
TPEA

[Encoder Thermal Warn]
Cause: Encoder module thermal warning.



Remedy:

  • Check encoder temperature and cooling.
TS1A

[Temp Sens AI1 Warn]
Cause: Temperature sensor AI1 warning (open circuit).



Remedy:

  • Check AI1 sensor wiring for breaks.
TS3A

[Temp Sens AI3 Warn]
Cause: Temperature sensor AI3 warning (open circuit).



Remedy:

  • Check AI3 sensor wiring for breaks.
TS4A

[Temp Sens AI4 Warn]
Cause: Temperature sensor AI4 warning (open circuit).



Remedy:

  • Check AI4 sensor wiring for breaks.
TS5A

[Temp Sens AI5 Warn]
Cause: Temperature sensor AI5 warning (open circuit).



Remedy:

  • Check AI5 sensor wiring for breaks.
DCRW

[DC Bus Ripple Warn]
Cause: DC Bus Ripple Warning.



Remedy:

  • Check for phase imbalance or loss.
AFFL

[Fallback Channel]
Cause: Automatic fallback behavior activated after a fieldbus communication interruption.



Remedy:

  • Check fieldbus network cables.
IWA

[MonitorCircuit A Warn]
Cause: Monitoring circuit A warning.



Remedy:

  • Check internal monitoring circuit A.
IWB

[MonitorCircuit B Warn]
Cause: Monitoring circuit B warning.



Remedy:

  • Check internal monitoring circuit B.
IWC

[MonitorCircuit C Warn]
Cause: Monitoring circuit C warning.



Remedy:

  • Check internal monitoring circuit C.
IWD

[MonitorCircuit D Warn]
Cause: Monitoring circuit D warning.



Remedy:

  • Check internal monitoring circuit D.
LKON

[ON Lock Warning]
Cause: ON lock warning resulting from an external device not ready.



Remedy:

  • Ensure external device is ready.
INFM

[Internal Error 22]
Cause: Internal error 22 (Embedded Ethernet).



Remedy:

  • Restart device or contact support if persists.
RFTA

[Pwr Backup Warn]
Cause: Power backup mode warning.



Remedy:

  • Check status of backup power supply.
SLF1

[Modbus Com Inter.]
Cause: Modbus communication interruption warning.



Remedy:

  • Check Modbus wiring and termination.
AnF

[Load slipping]
Cause: Not following the ramp. The difference between the output frequency and the speed feedback is not correct.



Remedy:

  • Confirm the drive rating according to the application (motor, load, etc).

  • Verify the motor, gain, and stability parameters.

  • Add a braking resistor.

  • Verify the mechanical coupling and wiring of the encoder.

  • If torque control is used with encoder speed feedback:

    • Set [Load slip detection] Sdd = [No].

    • Set [Positive deadband] dbP and [Negative deadband] dbn to a value less than 10% of nominal motor frequency.
ASF

[Angle error]
Cause: This error is triggered during the phase-shift angle measurement if the motor phase is disconnected or if the motor inductance is too high.



Remedy:

  • Verify the motor phases and the maximum current allowed by the drive.
bLF

[Brake Control]
Cause:

  • Brake release current not reached.

  • The torque set point is not reached.

  • The fluxing current is not stable.





Remedy:

  • Verify the drive/motor connection.

  • Verify the motor windings.

  • Verify the [Brk Release Current] Ibr and [Brake release I Rev] Ird settings.

  • (Note: This error requires a power reset).
bOF

[Brake Resistor ovld]
Cause: The braking resistor is overloaded.



Remedy:

  • Wait for the braking resistor to cool down.

  • Verify the nominal power of the braking resistor.

  • Verify the [Braking Resistor Power] brP and [Braking Resistor Value] brv parameters.
brF

[Brake Feedback]
Cause:

  • Brake feedback contact status incorrect compared to logic control.

  • Brake does not stop motor quickly enough.





Remedy:

  • Verify the brake feedback circuit.

  • Verify the brake logic control circuit.

  • Verify the brake behavior.

  • Verify settings for [Brake Release Time] brt, [Brake Engage Time] bEt, [Brake Fdbk Filter] FbC, etc.
bSqF

[Backlash Error]
Cause: The torque threshold used for backlash function cannot be reached after [BL Monit Delay] bqt.



Remedy:

  • Verify the settings.

  • Verify the coupling.
bUF

[DB unit sh. circuit]
Cause:

  • Short-circuit from braking unit.

  • Braking unit not connected (not applicable for drive system braking unit option).





Remedy:

  • Verify the wiring of the braking unit.

  • Verify that the braking unit value is not too low.

  • (Note: This error requires a power reset).
bUFo

[DB unit op. circuit]
Cause:

  • Open circuit from braking circuit and/or braking resistor.

  • Braking resistor not connected/detected.





Remedy:

  • Verify the wiring of the braking resistor.

  • Verify by measurement that the resistance of the braking resistor is not too high.

  • Verify the parameter br1.

  • (Note: This error requires a power reset).
CbF

[Circuit Breaker Error]
Cause: The DC bus voltage level is not correct compared to the circuit breaker logic control after the configured timeout.



Remedy:

  • Verify the circuit breaker logic control (pulse time for start and stop).

  • Verify the mechanical state of the circuit breaker.

  • (Note: This error requires a power reset).
CFF

[Incorrect Configuration]
Cause:

  • Option module changed or removed.

  • Control board replaced by a board configured with a different rating.

  • Current configuration is inconsistent.





Remedy:

  • Verify that there is no detected error on the option module.

  • Return to factory settings or retrieve the backup configuration if it is valid.
CFi

[Invalid Configuration]
Cause: Invalid configuration. The configuration loaded via tool or fieldbus is inconsistent.



Remedy:

  • Verify the loaded configuration.

  • Load a valid configuration.
CFi2

[Conf Transfer Error]
Cause:

  • The configuration transfer to the drive was not successful or interrupted.

  • The configuration loaded is not compatible with the drive.





Remedy:

  • Verify the configuration loaded previously.

  • Load a compatible configuration.

  • Perform a factory setting.
CFi3

[Pre-settings Transfer Error]
Cause: The configuration transfer to the drive was not successful or interrupted.



Remedy:

  • Contact your local Schneider Electric representative.
CFi4

[Empty Configuration]
Cause: The selected configuration for the [Multimotors config] has not been created previously.



Remedy:

  • Verify the configurations saved.

  • Switch to a compatible configuration.
CnF

[Fieldbus Com Interrupt]
Cause: Communication interruption on fieldbus module.



Remedy:

  • Verify the environment (electromagnetic compatibility).

  • Verify the wiring and timeout.

  • Replace the option module.
CoF

[CANopen Com Interrupt]
Cause: Communication interruption on the CANopen® fieldbus.



Remedy:

  • Verify the communication fieldbus.

  • Verify the timeout.

  • Refer to the CANopen® manual.
CrF1

[Precharge Capacitor]
Cause: Charging circuit control detected error or charging resistor damaged. Supply mains too low.



Remedy:

  • Turn off the drive and then turn on again.

  • Verify the internal connections.

  • Verify the voltage and the parameters of [Undervoltage handling].
CSF

[Channel Switch Error]
Cause: Switch to an invalid channel.



Remedy:

  • Verify the function parameters.
dCrE

[DC Bus Ripple Error]
Cause: Persistent ripple observed on the DC bus or DC bus capacitors damaged.



Remedy:

  • Turn off the drive and then turn on again.

  • Verify correct behavior of the input filter.

  • Verify the mains wirings and internal connections.

  • (Note: This error requires a power reset).
dLF

[Dynamic Load Error]
Cause: Load variation out of range.



Remedy:

  • Verify for a mechanical cause of load instability.
ECF

[Encoder Coupling]
Cause: The mechanical coupling of the encoder is broken. Detection active when [Encoder Coupling Monit] is Yes.



Remedy:

  • Verify the mechanical coupling of the encoder.
EEF1

[EEPROM Control]
Cause: An error of the internal memory of the control block has been detected.



Remedy:

  • Verify the environment (electromagnetic compatibility).

  • Switch off the product.

  • Return to factory settings.

  • (Note: This error requires a power reset).
EEF2

[EEPROM Power]
Cause: An error of the internal memory of the power board has been detected.



Remedy:

  • Verify the environment (electromagnetic compatibility).

  • Switch off the product.

  • Return to factory settings.

  • (Note: This error requires a power reset).
EnF

[Encoder]
Cause: Encoder feedback error. Difference between measured and estimated speed is > 4%.



Remedy:

  • Verify the configuration parameters for the encoder used.

  • Verify the mechanical and electrical operation of the encoder.

  • Verify consistency between encoder signals and direction of rotation.

  • If necessary, reverse rotation direction via [Output Ph rotation] PHr.

  • Verify the encoder module and supply voltage.
EPF1

[External Error]
Cause: Event triggered by an external device (depending on user settings) or Ethernet configuration file corrupted.



Remedy:

  • Remove the cause of the external error.

  • Perform a factory setting of the Ethernet configuration or modify IP Mode.
EPF2

[Fieldbus Error]
Cause: Event triggered by an external device, depending on user.



Remedy:

  • Remove the cause of the external error.
EtHF

[Embd Eth Com Interrupt]
Cause: Communication interruption on the Ethernet IP ModbusTCP bus.



Remedy:

  • Verify the communication bus.

  • Refer to the Ethernet manual.
FCF1

[Out Contact Closed Error]
Cause: The output contactor remains closed although the opening conditions have been met.



Remedy:

  • Verify the output contactor and its wiring.

  • Verify the contactor feedback wiring.

  • (Note: This error requires a power reset).
FCF2

[Out Contact Opened Error]
Cause: The output contactor remains opened although the closing conditions have been met.



Remedy:

  • Verify the output contactor and its wiring.

  • Verify the contactor feedback wiring.
Fdr1

[FDR 1 Error]
Cause:

  • Embedded Ethernet FDR error.

  • Communication interruption between drive and PLC.

  • Drive rating not consistent with configuration file.





Remedy:

  • Verify the drive and PLC connection.

  • Verify the communication workload.

  • Restart the transfer of configuration file from drive to PLC.
Fdr2

[FDR 2 Error]
Cause:

  • Ethernet fieldbus module FDR error.

  • Configuration file incompatible, empty, or corrupted.





Remedy:

  • Verify the drive and PLC connection.

  • Verify the communication workload.

  • Restart the transfer of configuration file from drive to PLC.
FWEr

[Firmware Update Error]
Cause: Firmware update function has detected an error.



Remedy:

  • Contact your local Schneider Electric representative.
HCF

[Boards Compatibility]
Cause: Hardware configuration error. [Pairing password] enabled and option module changed.



Remedy:

  • Refit the original option module.

  • Confirm the configuration by entering the [Pairing password] PPI if the module was changed deliberately.
IFA

[MonitorCircuit A Error]
Cause: The digital input assigned to [MonitorCircuit A Assign] is active for longer than delay.



Remedy:

  • Verify the connected device and its wiring.

  • Verify the parameter assignment.
IFb

MonitorCircuit B Error
Cause:

The digital input assigned to [MonitorCircuit B Assign] IFAb is active for longer than [MonitorCircuit B Delay] IFdb.



Remedy:

  • Verify the connected device and its wiring.

  • Verify the [MonitorCircuit B Assign] IFAB parameter assignment.

  • Note: This detected error can be cleared with the [Auto Fault Reset] ATR or manually with the [Fault Reset Assign] RSF parameter.
IFC

MonitorCircuit C Error
Cause:

The digital input assigned to [MonitorCircuit C Assign] IFAC is active for longer than [MonitorCircuit C Delay] IFdC.



Remedy:

  • Verify the connected device and its wiring.

  • Verify the [MonitorCircuit C Assign] IFAC parameter assignment.

  • Note: This detected error can be cleared with the [Auto Fault Reset] ATR or manually with the [Fault Reset Assign] RSF parameter.
IFd

MonitorCircuit D Error
Cause:

The digital input assigned to [MonitorCircuit D Assign] IFAd is active for longer than [MonitorCircuit D Delay] IFdd.



Remedy:

  • Verify the connected device and its wiring.

  • Verify the [MonitorCircuit D Assign] IFAd parameter assignment.

  • Note: This detected error can be cleared with the [Auto Fault Reset] ATR or manually with the [Fault Reset Assign] RSF parameter.
iHF

Input Overheating
Cause:

The AFE brick temperature is too high.



Remedy:

  • Verify the drive ventilation and the ambient temperature. Wait for the drive to cool down before restarting.

  • Note: This detected error can be cleared with the [Auto Fault Reset] ATR or manually with the [Fault Reset Assign] RSF parameter.
ILF

Internal Link Error
Cause:

Communication interruption between option module and the drive.



Remedy:

  • Verify the environment (electromagnetic compatibility).

  • Verify the connections.

  • Replace the option module.

  • Contact your local Schneider Electric representative.
InF0

Internal Error 0
Cause:

Communication interruption between microprocessors of the control board, or the power board rating is not valid.



Remedy:

  • Contact your local Schneider Electric representative.
InF1

Internal Error 1
Cause:

The power board rating is not valid.



Remedy:

  • Contact your local Schneider Electric representative.
InF2

Internal Error 2
Cause:

The power board is incompatible with the control block software.



Remedy:

  • Contact your local Schneider Electric representative.
InF3

Internal Error 3
Cause:

Internal communication detected error.



Remedy:

  • Verify the wiring on drive control terminals (internal 10V supply for analog inputs overloaded).

  • Contact your local Schneider Electric representative.
InF4

Internal Error 4
Cause:

Internal data inconsistent.



Remedy:

  • Contact your local Schneider Electric representative.
InF6

Internal Error 6
Cause:


  • The option module installed in the drive is not recognized.

  • The removable control terminal modules (if existing) are not present or not recognized.

  • The embedded Ethernet adapter is not recognized.




Remedy:

  • Verify the catalog number and compatibility of the option module.

  • Plug the removable control terminal modules after the drive has been switched off.

  • Contact your local Schneider Electric representative.
InF7

Internal Error 7
Cause:

Communication interruption with CPLD component of Control board.



Remedy:

  • Contact your local Schneider Electric representative.
InF8

Internal Error 8
Cause:

The internal power switching supply is not correct.



Remedy:

  • Contact your local Schneider Electric representative.
InF9

Internal Error 9
Cause:

An error on the current circuit measurement has been detected.



Remedy:

  • Contact your local Schneider Electric representative.
InFA

Internal Error 10
Cause:

The input stage is not operating correctly.



Remedy:

  • Contact your local Schneider Electric representative.
InFb

Internal Error 11
Cause:

The internal drive thermal sensor is not operating correctly.



Remedy:

  • Contact your local Schneider Electric representative.
InFC

Internal Error 12
Cause:

Internal current supply error.



Remedy:

  • Contact your local Schneider Electric representative.
InFd

Internal Error 13
Cause:

Differential current deviation.



Remedy:

  • Contact your local Schneider Electric representative.
InFE

Internal Error 14
Cause:

Internal microprocessor detected error.



Remedy:

  • Verify that the error code can be cleared.

  • Contact your local Schneider Electric representative.
InFF

Internal Error 15
Cause:

Serial memory flash format error.



Remedy:

  • Contact your local Schneider Electric representative.
InFG

Internal Error 16
Cause:

Communication interruption or internal error of output relays option module.



Remedy:

  • Verify that the option module is correctly connected to the slot.

  • Replace the option module.

  • Contact your local Schneider Electric representative.
InFH

Internal Error 17
Cause:

Communication interruption with the Extension module of digital & analog I/O or internal error of the Extension module of digital & analog I/O.



Remedy:

  • Verify that the option module is correctly connected to the slot.

  • Replace the option module.

  • Contact your local Schneider Electric representative.
InFi

Internal Error 18
Cause:

Safety Module Internal Error (Communication interruption or internal error).



Remedy:

  • Verify the Safety Module errors for additional information.

  • Verify that the option module is correctly inserted into the slot.

  • Replace the option module.

  • Contact your local Schneider Electric representative.
InFJ

Internal Error 19
Cause:

An error on the encoder module has been detected.



Remedy:

  • Verify if the encoder option module is connected correctly to the slot.

  • Verify the compatibility of the encoder.

  • Contact your local Schneider Electric representative.
InFk

Internal Error 20
Cause:

Option module interface board error.



Remedy:

  • Contact your local Schneider Electric representative.
InFL

Internal Error 21
Cause:

Internal Real Time Clock error. It could be a communication error between the keypad and the drive or a clock oscillator start error.



Remedy:

  • Contact your local Schneider Electric representative.
InFM

Internal Error 22
Cause:

An error on the embedded Ethernet adapter has been detected.



Remedy:

  • Verify the connection to the Ethernet port.

  • Contact your local Schneider Electric representative.
InFP

Internal Error 25
Cause:

Incompatibility between Control Board hardware version and firmware version.



Remedy:

  • Update the firmware package.

  • Contact your local Schneider Electric representative.
InFr

Internal Error 27
Cause:

Diagnostics in CPLD have detected an error.



Remedy:

  • Contact your local Schneider Electric representative.
LCF

Input Contactor
Cause:

The drive is not switched on even though [Mains V. time out] LCt timeout has elapsed.



Remedy:

  • Verify the input contactor and its wiring.

  • Verify the [Mains V. time out] LCt timeout.

  • Verify the supply mains/contactor/drive wiring.
LFF1

AI1 4-20mA loss
Cause:

Loss of the 4-20 mA on analog input AI1. This error is triggered when the measured current is below 2 mA.



Remedy:

  • Verify the connection on the analog inputs.

  • Verify the setting of [AI1 4-20mA loss] LFL1 parameter.
LFF3

AI3 4-20mA loss
Cause:

Loss of the 4-20 mA on analog input AI3. This error is triggered when the measured current is below 2 mA.



Remedy:

  • Verify the connection on the analog inputs.

  • Verify the setting of [AI3 4-20mA loss] LFL3 parameter.
LFF4

AI4 4-20mA loss
Cause:

Loss of the 4-20 mA on analog input AI4. This error is triggered when the measured current is below 2 mA.



Remedy:

  • Verify the connection on the analog inputs.

  • Verify the setting of [AI4 4-20mA loss] LFL4 parameter.
LFF5

AI5 4-20mA loss
Cause:

Loss of the 4-20 mA on analog input AI5. This error is triggered when the measured current is below 2 mA.



Remedy:

  • Verify the connection on the analog inputs.

  • Verify the setting of [AI5 4-20mA loss] LFL5 parameter.
LKon

ON Lock Error
Cause:

External device not ready.



Remedy:

  • Verify external device assigned to ON lock input.
MdCF

Load Mvt Error
Cause:

Load movement for which no command has been given.



Remedy:

  • Verify the brake command circuit. Verify the brake.

  • Note: This detected error requires a power reset.
MdLF
[MultiDrive Link Error]
Cause:

  • The communication has been interrupted while running.

  • The function has detected an inconsistency in the system configuration.




Remedy:

  • Check the communication network.

  • Check the configuration of the multi-drive link function.
MSdF
[M/S Device Error]
Cause:

  • For a master, one or more slaves are not present or not ready.

  • For a slave, the master is not present.




Remedy:

  • Verify the drive status.

  • Verify the settings of the master/slave architecture.
ObF
[DC Bus Overvoltage]
Cause:

  • Deceleration time too short or driving load too high.

  • Supply mains voltage too high.




Remedy:

  • Increase the deceleration time.

  • Configure the [Dec ramp adapt.] (brA) function if it is compatible with the application.

  • Verify the supply mains voltage.
OCF
[Overcurrent]
Cause:

  • Parameters in the [Motor data] menu are not correct.

  • Inertia or load too high.

  • Mechanical locking.




Remedy:

  • Verify the motor parameters.

  • Verify the size of the motor/drive/load.

  • Verify the state of the mechanism.

  • Decrease [Current limitation] (CLI).

  • Increase the switching frequency.
OHF
[Drive Overheating]
Cause: Drive temperature too high.



Remedy:

  • Verify the motor load, the drive ventilation, and the ambient temperature. Wait for the drive to cool down before restarting.
OLC
[Process Overload]
Cause: Process overload.



Remedy:

  • Verify and remove the cause of the overload.

  • Verify the parameters of the [Process overload] (OLd) function.
OLF
[Motor Overload]
Cause: Triggered by excessive motor current.



Remedy:

  • Verify the setting of the motor thermal monitoring.

  • Verify the motor load. Wait for the motor to cool down before restarting.

  • Verify the setting of the following parameters:

    • [Motor Th Current] (ItH)

    • [Motor Thermal Mode] (tHt)

    • [Motor Therm Thd] (ttd)

    • [MotorTemp ErrorResp] (OLL)
OPF1
[Single Output Phase Loss]
Cause: Loss of one phase at drive output.



Remedy:

  • Verify the wiring from the drive to the motor.
OPF2
[Output Phase Loss]
Cause:

  • Motor not connected or motor power too low.

  • Output contactor opened.

  • Instantaneous instability in the motor current.




Remedy:

  • Verify the wiring from the drive to the motor.

  • If an output contactor is being used, set [OutPhaseLoss Assign] (OPL) to [No Error Triggered] (OAC).

  • If the drive is connected to a low-power motor or not connected to a motor: In factory settings mode, motor phase loss detection is active [Output Phase Loss] (OPL) = [OPF Error Triggered] (YES). Deactivate motor phase loss detection [Output Phase Loss] (OPL) = [Function Inactive] (nO).

  • Verify and optimize the following parameters: [IR compensation] (UFr), [Nom Motor Voltage] (UnS) and [Rated mot. current] (nCr) and perform [Autotuning] (tUn).
OSF
[Supply Mains Overvoltage]
Cause:

  • Supply mains voltage too high.

  • Disturbed supply mains.




Remedy:

  • Verify the supply mains voltage.
PGLF
[Program Loading Error]
Cause: Verify that the error code can be cleared.



Remedy:

  • Contact your local Schneider Electric representative.
PGrF
[Program Running Error]
Cause: Verify that the error code can be cleared.



Remedy:

  • Contact your local Schneider Electric representative.
PHF
[Input phase loss]
Cause:

  • Drive incorrectly supplied or a tripped fused.

  • One phase is unavailable.

  • 3-phase Drive used on a single-phase supply mains.

  • Unbalanced load.




Remedy:

  • Verify the power connection and the fuses.

  • Use a 3-phase supply mains.

  • Disable the detected error by [Input phase loss] (IPL) = [No] (nO) if single phase supply mains or DC bus supply is used.
rAdF
[Rotation Angle Monit]
Cause: The monitoring of the rotation angle has detected a too high deviation.



Remedy:

  • Check for mechanical problems in the system.

  • Verify the settings of the monitoring function.
SAFF
[Safety Function Error]
Cause:

  • Debounce time exceeded.

  • Internal hardware error.

  • STOA and STOB have a different status (high/low) for more than 1 second.




Remedy:

  • Verify the wiring of the digital inputs STOA and STOB.

  • Contact your local Schneider Electric representative.
SAVF
[Safety Violation]
Cause:

  • Safety Module Violation Error.

  • Safety Module has detected a violation of defined limits.




Remedy:

  • Verify the Safety Module errors for additional information.

  • Contact your local Schneider Electric representative.
SCF1
[Motor short circuit]
Cause: Short-circuit or grounding at the drive output.



Remedy:

  • Verify the cables connecting the drive to the motor, and the motor insulation.

  • Adjust the switching frequency.

  • Connect chokes in series with the motor.

  • Verify the adjustment of speed loop and brake.

  • Increase the [Time to restart] (ttr).
SCF3
[Ground Short Circuit]
Cause: Significant ground leakage current at the drive output if several motors are connected in parallel.



Remedy:

  • Verify the cables connecting the drive to the motor, and the motor insulation.

  • Adjust the switching frequency.

  • Connect chokes in series with the motor.

  • If you have long cables, verify the setting of [Ground Fault Activation] (GrFL).
SCF4
[IGBT Short Circuit]
Cause:

  • Power component detected error.

  • At product power-on, the IGBTs are tested for short circuit. The time to check each transistor is between 1 and 10 µs.




Remedy:

  • Verify the setting of [Output Short Circuit Test] (Strt) parameter.

  • Contact your local Schneider Electric representative.
SCF5
[Motor Short Circuit]
Cause: Short-circuit at drive output.



Remedy:

  • Verify the cables connecting the drive to the motor, and the motor’s insulation.

  • Contact your local Schneider Electric representative.
SCFF
[Safety Config Error]
Cause:

  • Safety Module Configuration Error.

  • Incorrect configuration linked to the Safety Module has been detected.




Remedy:

  • Verify the Safety Module errors for additional information.

  • Contact your local Schneider Electric representative.
SLF1
[Modbus Com Interruption]
Cause: Communication interruption on the Modbus port.



Remedy:

  • Verify the communication bus.

  • Verify the timeout.

  • Refer to the Modbus user manual.
SLF2
[PC Com Interruption]
Cause: Communication interruption with the commissioning software.



Remedy:

  • Verify the commissioning software connecting cable.

  • Verify the timeout.
SLF3
[HMI Com Interruption]
Cause:

  • Communication interruption with the Graphic display terminal.

  • This error is triggered when the command or reference value are given using the Graphic Display Terminal and if the communication is interrupted during more than 2 seconds.




Remedy:

  • Verify the Graphic display terminal connection.

  • Verify the timeout.
SIOF
[Safety IO Error]
Cause:

  • Safety Module IO Error.

  • Error on input / output of the Safety Module.

  • Error on encoder signal.




Remedy:

  • Verify the Safety Module errors for additional information.

  • Contact your local Schneider Electric representative.
SoF
Motor Overspeed
Cause:


Instability or driving load too high. If a downstream contactor is used, the contacts between the motor and the drive have not been closed before applying a Run command. The overspeed threshold (corresponding to 110% of [Max frequency] tFr) has been reached.



Remedy:

  • Verify the motor parameter settings.

  • Verify the size of the motor/drive/load.

  • Verify and close the contacts between the motor and the drive before applying a Run command.

  • Verify the consistency between [Max frequency] tFr and [High Speed] HSP. It is recommended to have at least [Max frequency] tFr ≥ 110% * [High Speed] HSP.
SPF
Encoder Feedback Loss
Cause:


This error is triggered if: The measured speed is lower than 2% of [Nominal Motor Freq] FrS; The difference between stator speed and measured speed is > 20% of FrS; EMC perturbations; No input signal; Encoder feedback missing; Supply voltage missing; Broken wire.



Remedy:

  • Verify the error code value [Encoder Fdbck Error] EnCE.

  • Verify the wiring between the encoder and the drive.

  • Verify the encoder.

  • Verify the encoder settings.

  • Verify the wiring of the pulse input and the sensor used.

  • Use a shielded cable and ground both ends.

  • Verify the encoder power supply. Reduce [Encoder Supply Voltage] uECV value.

  • Check the supply voltage of the encoder.
SPFC
Security Files Corrupt
Cause:


Security files corrupted or missing.



Remedy:

  • Switch off the product. At next switch-on, the security file will be created again, and the information related to cybersecurity (such as channel policy and password) are set back to the default value.
SrF
Torque timeout
Cause:


The torque control function is not able to regulate the torque within the configured dead band. The drive has switched to speed control for longer than [Torque ctrl time out] rto.



Remedy:

  • Verify the settings of the [Torque control] tor – function.

  • Verify that there are no mechanical constraints.
SSF
Torque Limitation Error
Cause:


The drive was in torque limitation or current limitation state during [Trq/I Limit Timeout] Sto.



Remedy:

  • Verify the settings of the [Torque limitation] toL – function.

  • Verify that there are no mechanical constraints.
StF
Motor Stall Error
Cause:


The stall monitoring function has detected an error. Triggered if: Output frequency is smaller than [Stall Frequency] StP3; Output current is higher than [Stall Current] StP2; Duration longer than [stall Max Time] StP1.



Remedy:

  • Search for a mechanical blocking of the motor.

  • Search for a possible cause of motor overload.

  • Verify the settings of the monitoring function.
t1CF
AI1 Thermal Sensor Error
Cause:


The thermal monitoring function has detected an error of the thermal sensor connected to the analog input AI1: Open circuit or Short circuit.



Remedy:

  • Verify the sensor and its wiring.

  • Replace the sensor.
t3CF
AI3 Thermal Sensor Error
Cause:


The thermal monitoring function has detected an error of the thermal sensor connected to the analog input AI3: Open circuit or Short circuit.



Remedy:

  • Verify the sensor and its wiring.

  • Replace the sensor.

  • Verify the setting of [AI3 Type] AI3t parameter.
t4CF
AI4 Thermal Sensor Error
Cause:


The thermal monitoring function has detected an error of the thermal sensor connected to the analog input AI4: Open circuit or Short circuit.



Remedy:

  • Verify the sensor and its wiring.

  • Replace the sensor.

  • Verify the setting of [AI4 Type] AI4t parameter.
t5CF
AI5 Thermal Sensor Error
Cause:


The thermal monitoring function has detected an error of the thermal sensor connected to the analog input AI5: Open circuit or Short circuit.



Remedy:

  • Verify the sensor and its wiring.

  • Replace the sensor.

  • Verify the setting of [AI5 Type] AI5t parameter.
tECF
Encoder Th Sensor Error
Cause:


The thermal sensor monitoring function has detected a thermal sensor on the encoder module analog input: Open circuit or Short circuit.



Remedy:

  • Verify the sensor and its wiring.

  • Replace the sensor.
tH1F
AI1 Th Level Error
Cause:


The thermal sensor monitoring function has detected a high temperature on analog input AI1.



Remedy:

  • Search for a possible cause of overheating.

  • Verify the settings of the monitoring function.
tH3F
AI3 Th Level Error
Cause:


The thermal sensor monitoring function has detected a high temperature on analog input AI3.



Remedy:

  • Search for a possible cause of overheating.

  • Verify the settings of the monitoring function.
tH4F
AI4 Th Level Error
Cause:


The thermal sensor monitoring function has detected a high temperature on analog input AI4.



Remedy:

  • Search for a possible cause of overheating.

  • Verify the settings of the monitoring function.
tH5F
AI5 Th Level Error
Cause:


The thermal sensor monitoring function has detected a high temperature on analog input AI5.



Remedy:

  • Search for a possible cause of overheating.

  • Verify the settings of the monitoring function.
tHEF
Encoder Th Detected Error
Cause:


The thermal sensor monitoring function has detected a high temperature on encoder module analog input.



Remedy:

  • Search for a possible cause of overheating.

  • Verify the settings of the monitoring function.
tJF
IGBT Overheating
Cause:


Drive power stage overheating.



Remedy:

  • Verify the size of the load/motor/drive according to environment conditions.

  • Reduce the switching frequency.

  • Increase the ramp time.

  • Decrease the current limitation.
tLoF
Drive Overload
Cause:


The [Drive overload monit] obr – function has detected an error.



Remedy:

  • Verify the size of the load/motor/drive according to environment conditions.

  • Verify the settings of the [Drive Overload Monit] tLoL parameter.
tnF
Autotuning Error
Cause:


Special motor or motor whose power is not suitable for the drive. Motor not connected to the drive. Motor not stopped.



Remedy:

  • Verify that the motor/drive are compatible.

  • Verify that the motor is connected to the drive during autotuning.

  • If an output contactor is being used, verify that it is closed during autotuning.

  • Verify that the motor is present and stopped during autotuning.

  • In case of reluctance motor, reduce [PSI Align Curr Max] MCr.
ULF
Process Underload
Cause:


Process underload.



Remedy:

  • Verify and remove the cause of the underload.

  • Verify the parameters of the [Process underload] uLd – function.
USF
Supply Mains UnderV
Cause:


Supply mains too low. Transient voltage dips.



Remedy:

  • Verify the voltage and the parameters of [Undervoltage handling] uSb.