Schneider ATV32 Drives

Schneider ATV32 Drives Fault Codes:

Fault Code and MeaningCause and Remedy
AnF
[Load slipping]
Cause: The difference between the output frequency and the speed feedback is not correct.



Remedy:

  • Check the motor, gain and stability parameters.

  • Add a braking resistor.

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

  • Check the encoder’s mechanical coupling and its wiring.

  • Check the setting of parameters.
ASF
[Angle Error]
Cause: This occurs during the phase-shift angle measurement, if the motor phase is disconnected or if the motor inductance is too high.



Remedy:

  • Check the motor phases and the maximum current allowed by the drive.
brF
[Brake feedback]
Cause:

  • The brake feedback contact does not match the brake logic control.

  • The brake does not stop the motor quickly enough (detected by measuring the speed on the “Pulse input” input).




Remedy:

  • Check the feedback circuit and the brake logic control circuit.

  • Check the mechanical state of the brake.

  • Check the brake linings.
CrF1
[Precharge]
Cause: Charging relay control detected fault or charging resistor damaged.



Remedy:

  • Turn the drive off and then turn on again.

  • Check the internal connections.

  • Contact Schneider Electric Product Support.
EEF1
[Control Eeprom]
Cause: Internal memory detected fault, control block.



Remedy:

  • Check the environment (electromagnetic compatibility).

  • Turn off, reset, return to factory settings.

  • Contact Schneider Electric Product Support.
EEF2
[Power Eeprom]
Cause: Internal memory detected fault, power card.



Remedy:

  • Contact Schneider Electric Product Support.
FCF1
[Out. contact. stuck]
Cause: The output contactor remains closed although the opening conditions have been met.



Remedy:

  • Check the contactor and its wiring.

  • Check the feedback circuit.
HdF
[IGBT desaturation]
Cause: Short-circuit or grounding at the drive output.



Remedy:

  • Check the cables connecting the drive to the motor, and the motor insulation.
ILF
[internal com. link]
Cause: Communication interruption between option card and drive.



Remedy:

  • Check the environment (electromagnetic compatibility).

  • Check the connections.

  • Replace the option card.

  • Contact Schneider Electric Product Support.
InF1
[Rating error]
Cause: The power card is different from the card stored.



Remedy:

  • Check the reference of the power card.
InF2
[Incompatible PB]
Cause: The power card is incompatible with the control block.



Remedy:

  • Check the reference of the power card and its compatibility.
InF3
[Internal serial link]
Cause: Communication interruption between the internal cards.



Remedy:

  • Check the internal connections.

  • Contact Schneider Electric Product Support.
InF4
[Internal-mftg zone]
Cause: Internal data inconsistent.



Remedy:

  • Recalibrate the drive (performed by Schneider Electric Product Support).
InF6
[Internal – fault option]
Cause: The option installed in the drive is not recognized.



Remedy:

  • Check the reference and compatibility of the option.

  • Check that the option is well inserted into the ATV32.
InF9
[Internal- I measure]
Cause: The current measurements are incorrect.



Remedy:

  • Replace the current sensors or the power card.

  • Contact Schneider Electric Product Support.
InFA
[Internal-mains circuit]
Cause: The input stage is not operating correctly.



Remedy:

  • Contact Schneider Electric Product Support.
InFb
[Internal- th. sensor]
Cause: The drive temperature sensor is not operating correctly.



Remedy:

  • Replace the drive temperature sensor.

  • Contact Schneider Electric Product Support.
InFE
[internal- CPU]
Cause: Internal microprocessor detected fault.



Remedy:

  • Turn off and reset.

  • Contact Schneider Electric Product Support.
SAFF
[Safety fault]
Cause:

  • Debounce time exceeded.

  • SS1 trip threshold exceeded.

  • Wrong configuration.

  • SLS type trip overspeed detected.




Remedy:

  • Check the safety functions configuration.

  • Check the ATV32 Integrated safety Functions Manual (S1A45606).

  • Contact Schneider Electric Product Support.
SOF
[Overspeed]
Cause: Instability or driving load too high.



Remedy:

  • Check the motor, gain and stability parameters.

  • Add a braking resistor.

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

  • Check the parameters settings for the [FREQUENCY METER] (FqF-) function.
SPF
[Speed fdback loss]
Cause:

  • Signal on “Pulse input” missing, if the input is used for speed measurement.

  • Encoder feedback signal missing.




Remedy:

  • Check the wiring of the input cable and the detector used.

  • Check the configuration parameters of the encoder.

  • Check the wiring between the encoder and the drive.

  • Check the encoder.
bLF
[Brake control]
Cause:

  • Brake release current not reached.

  • Brake engage frequency threshold [Brake engage freq] (bEn) only regulated when brake logic control is assigned.




Remedy:

  • Check the drive/motor connection.

  • Check the motor windings.

  • Check the [Brake release I FW] (Ibr) and [Brake release I Rev] (Ird) settings.

  • Apply the recommended settings for [Brake engage freq] (bEn).
CnF
[Com. network]
Cause: Communication interruption on communication card.



Remedy:

  • Check the environment (electromagnetic compatibility).

  • Check the wiring.

  • Check the time-out.

  • Replace the option card.

  • Contact Schneider Electric Product Support.
COF
[CANopen com.]
Cause: Communication interruption on the CANopen® bus.



Remedy:

  • Check the communication bus.

  • Check the time-out.

  • Refer to the CANopen® User’s manual.
EPF1
[External flt-LI/Bit]
Cause: Event triggered by an external device, depending on user.



Remedy:

  • Check the device which caused the trip and reset.
EPF2
[External fault com.]
Cause: Event triggered by a communication network.



Remedy:

  • Check for the cause of the trip and reset.
FbES
[FB stop flt.]
Cause: Function blocks have been stopped while motor was running.



Remedy:

  • Check [Stop FB Stop motor] (FbSM) configuration.
FCF2
[Out. contact. open.]
Cause: The output contactor remains open although the closing conditions have been met.



Remedy:

  • Check the contactor and its wiring.

  • Check the feedback circuit.
LCF
[input contactor]
Cause: The drive is not turned on even though [Mains V. time out ] (LCt) has elapsed.



Remedy:

  • Check the contactor and its wiring.

  • Check the time-out.

  • Check the line/contactor/drive connection.
LFF3
[AI3 4-20mA loss]
Cause: Loss of the 4-20 mA reference on analog input AI3.



Remedy:

  • Check the connection on the analog inputs.
ObF
[Overbraking]
Cause:

  • Braking too sudden or driving load.

  • Line voltage too high.




Remedy:

  • Increase the deceleration time.

  • Install a braking resistor if necessary.

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

  • Check the line voltage.
OCF
[Overcurrent]
Cause:

  • Parameters in the [SETTINGS] and [MOTOR CONTROL] menus are not correct.

  • Inertia or load too high.

  • Mechanical locking.




Remedy:

  • Check the parameters.

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

  • Check the state of the mechanism.

  • Decrease [Current limitation] (CLI).

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



Remedy:

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



Remedy:

  • Check and remove the cause of the overload.

  • Check the parameters of the [PROCESS OVERLOAD] (OLd-) function.
OLF
[Motor overload]
Cause: Triggered by excessive motor current.



Remedy:

  • Check the setting of the motor thermal protection, check the motor load. Wait for the motor to cool down before restarting.
OPF1
[1 output phase loss]
Cause: Loss of one phase at drive output.



Remedy:

  • Check the connections from the drive to the motor.

OPF2



[3 motor phase loss]

Cause:

Motor not connected or motor power too low.

Output contactor open.

Instantaneous instability in the motor current.



Remedy:

  • Check the connections from the drive to the motor.

  • If an output contactor is being used, set [Output Phase Loss] (OPL) to [Output cut] (OAC).

  • Test on a low power motor or without a motor: In factory settings mode, motor phase loss detection is active [Output Phase Loss] (OPL) = [Yes] (YES). To check the drive in a test or maintenance environment, without having to use a motor with the same rating as the drive (in particular for high power drives), deactivate motor phase loss detection [Output Phase Loss] (OPL) = [No] (nO).

  • Check and optimize the following parameters: [IR compensation] (UFr), [Rated motor volt.] (UnS) and [Rated mot. current] (nCr) and perform [Auto tuning] (tUn).

OSF



[Mains overvoltage]

Cause:

Line voltage too high.

Disturbed mains supply.



Remedy:

  • Check the line voltage.

OtFL



[LI6=PTC overheat]

Cause:

Overheating of PTC probes detected on input LI6.



Remedy:

  • Check the motor load and motor size.

  • Check the motor ventilation.

  • Wait for the motor to cool before restarting.

  • Check the type and state of the PTC probes.

PtFL



[LI6=PTC probe]

Cause:

PTC probe on input LI6 open or short-circuited.



Remedy:

  • Check the PTC probe and the wiring between it and the motor/drive.

SCF1



[Motor short circuit]

Cause:

Short-circuit or grounding at the drive output.



Remedy:

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

  • Reduce the switching frequency.

  • Connect chokes in series with the motor.

  • Check the adjustment of speed loop and brake.

  • Increase the [Time to restart] (ttr).

  • Increase the switching frequency.

SCF3



[Ground short circuit]

Cause:

Significant earth leakage current at the drive output if several motors are connected in parallel.



Remedy:

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

  • Reduce the switching frequency.

  • Connect chokes in series with the motor.

  • Check the adjustment of speed loop and brake.

  • Increase the [Time to restart] (ttr).

  • Reduce the switching frequency.

SCF4



[IGBT short circuit]

Cause:

Power component detected fault.



Remedy:

  • Contact Schneider Electric Product Support.

SCF5



[Motor short circuit]

Cause:

Short-circuit at drive output.



Remedy:

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

  • Contact Schneider Electric Product Support.

SLF1



[Modbus com.]

Cause:

Communication interruption on the Modbus bus.



Remedy:

  • Check the communication bus.

  • Check the time-out.

  • Refer to the Modbus User’s manual.

SLF2



[PC com.]

Cause:

Communication interruption with PC Software.



Remedy:

  • Check the PC Software connecting cable.

  • Check the time-out.

SLF3



[HMI com.]

Cause:

Communication interruption with the graphic display terminal or remote display terminal.



Remedy:

  • Check the terminal connection.

  • Check the time-out.

SSF



[Torque/current lim]

Cause:

Switch to torque or current limitation.



Remedy:

  • Check if there are any mechanical problems.

  • Check the parameters of [TORQUE LIMITATION] (tOL-) and the parameters of the [TORQUE OR I LIM. DETECT.] (tId-).

tJF



[IGBT overheat]

Cause:

Drive overheated.



Remedy:

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

  • Reduce the switching frequency.

  • Wait for the motor to cool before restarting.

tnF



[Auto-tuning]

Cause:

Special motor or motor whose power is not suitable for the drive.

Motor not connected to the drive.

Motor not stopped.



Remedy:

  • Check that the motor/drive are compatible.

  • Check that the motor is present during auto-tuning.

  • If an output contactor is being used, close it during auto-tuning.

  • Check that the motor is stopped during tune operation.

ULF



[Proc. underload Flt]

Cause:

Process underload.



Remedy:

  • Check and remove the cause of the underload.

  • Check the parameters of the [PROCESS UNDERLOAD] (Uld-) function.
CFF
[Incorrect config.]
Cause:

  • Option card changed or removed.

  • Control block replaced by a control block configured on a drive with a different rating.

  • The current configuration is inconsistent.




Remedy:

  • Check that there are no card errors.

  • In the event of the option card being changed/removed deliberately, see manual remarks.

  • Check that there are no card errors.

  • In the event of the control block being changed deliberately, see manual remarks.

  • Return to factory settings or retrieve the backup configuration, if it is valid.
CFI / CFI2
[Invalid config.]
Cause:

  • Invalid configuration.

  • The configuration loaded in the drive via the bus or communication network is inconsistent.




Remedy:

  • Check the configuration loaded previously.

  • Load a compatible configuration.
CSF
[Ch. Sw. fault]
Cause:

  • Switch to not valid channels.




Remedy:

  • Check the function parameters.
dLF
[Dynamic load fault]
Cause:

  • Abnormal load variation.




Remedy:

  • Check that the load is not blocked by an obstacle.

  • Removal of a run command causes a reset.
FbE
[FB fault]
Cause:

  • Function blocks error.




Remedy:

  • See [FB Fault] (FbFt) for more details.
HCF
[Cards pairing]
Cause:

  • The [CARDS PAIRING] (PPI-) function has been configured and a drive card has been changed.




Remedy:

  • In the event of a card error, reinsert the original card.

  • Confirm the configuration by entering the [Pairing password] (PPI) if the card was changed deliberately.
PHF
[Input phase loss]
Cause:

  • Drive incorrectly supplied or a fuse blown.

  • One phase missing.

  • 3-phase ATV32 used on a single-phase line supply.

  • Unbalanced load.

  • This protection only operates with the drive on load.




Remedy:

  • Check the power connection and the fuses.

  • Use a 3-phase line supply.

  • Disable the detected fault by [Input phase loss] (IPL) = [No] (nO).
USF
[Undervoltage]
Cause:

  • Line supply too low.

  • Transient voltage dip.




Remedy:

  • Check the voltage and the parameters of [UNDERVOLTAGE MGT] (USb-).
InIt
[Initialization in progress]
Cause:

  • The microcontroller is initializing.

  • Search underway for communication configuration.




Remedy:

  • Wait for initialization to complete.
COM.E (Flashing)
[Communication error]
Cause:

  • Time out detected fault (50 ms).

  • This message is displayed after 20 attempts at communication.




Remedy:

  • Check communication connections and parameters.
A-17 (Flashing)
[Alarm button]
Cause:

  • A key has been held down for more than 10 seconds.

  • The keypad is disconnected.

  • The keypad wakes up when a key is pressed.




Remedy:

  • Release the key.

  • Check keypad connection.
CLr (Flashing)
[Confirmation of detected fault reset]
Cause:

  • This is displayed when the STOP key is pressed once if the active command channel is the remote display terminal.




Remedy:

  • Informational message; no specific remedy required.
dEU.E (Flashing)
[Drive disparity]
Cause:

  • The drive brand does not match that of the remote display terminal.




Remedy:

  • Ensure the remote display is compatible with the drive.
rOM.E (Flashing)
[ROM anomaly]
Cause:

  • The remote display terminal detects a ROM anomaly on the basis of checksum calculation.




Remedy:

  • Replace the remote display terminal.
rAM.E (Flashing)
[RAM anomaly]
Cause:

  • The remote display terminal detects a RAM anomaly.




Remedy:

  • Replace the remote display terminal.
CPU.E (Flashing)
[Other detected faults]
Cause:

  • Other detected faults.




Remedy:

  • Check for other fault codes on the drive.