Schneider ATV303 Drives

Schneider ATV303 Drives Fault Codes:

Fault Code and MeaningCause and Remedy
F001
Precharge
Cause: Charging relay control fault or charging resistor damaged.



Remedy:

  • Turn the drive off and then back on again.

  • Check the connections.

  • Check the stability of the main supply.

  • Contact local Schneider Electric representative.
F002
Unknown drive rating
Cause: Power card and stored card versions different.



Remedy:

  • Contact local Schneider Electric representative.
F003
Unknown or incompatible power board
Cause: The power card is incompatible with the control card.



Remedy:

  • Contact local Schneider Electric representative.
F004
Internal serial link fault
Cause: Communication interruption between the internal cards.



Remedy:

  • Contact local Schneider Electric representative.
F005
Invalid industrialization zone
Cause: Internal data inconsistent.



Remedy:

  • Contact local Schneider Electric representative.
F006
Current measurement circuit
Cause: Current measurement is not correct due to hardware circuit fault.



Remedy:

  • Contact local Schneider Electric representative.
—-
Problem with application firmware
Cause: Invalid application firmware update using the Multi-Loader tool.



Remedy:

  • Re-download application firmware.
F007
Internal thermal sensor detected fault
Cause:

  • The drive temperature sensor is not operating correctly.

  • The drive is in short circuit or open.




Remedy:

  • Contact local Schneider Electric representative.
F008
Internal CPU
Cause: Internal microprocessor fault.



Remedy:

  • Turn the drive off and then back on again.

  • Contact local Schneider Electric representative.
F010
Overcurrent
Cause:

  • Parameters in the Motor control menu (300-) 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.

  • Connect line motor chokes.

  • Reduce the Switching frequency range (315).

  • Check the ground connection of drive, motor cable, and motor insulation.
F018
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.

  • Connect line motor chokes.
F019
Ground short-circuit
Cause:

  • Ground fault while in run state.

  • Motor switching while in run state.

  • Significant current leakage to ground while several motors are connected in parallel.




Remedy:

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

  • Connect line motor chokes.
F020
IGBT short circuit
Cause: Internal power component short circuit detected at power on.



Remedy:

  • Contact local Schneider Electric representative.
F025
Overspeed
Cause:

  • Instability.

  • Overspeed associated with the inertia of the application.




Remedy:

  • Check the motor.

  • If overspeed is 10% more than Top frequency (308), adjust this parameter if necessary.

  • Add a braking resistor.

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

  • Check parameters of the speed loop (gain and stability).
F028
Autotuning fault
Cause:

  • Motor not connected to the drive.

  • Motor phase loss.

  • Special motor.

  • Motor is rotating (being driven by the load, for example).




Remedy:

  • Check that the motor/drive are compatible.

  • Check that the motor is present during autotuning.

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

  • Check that the motor is completely stopped.
F033
AI1 current loss
Cause: Detected if:

  • Analog input AI1 is configured as current.

  • AI1 current scaling parameter of 0% (204.1) is greater than 3 mA.

  • Analog input current is lower than 2 mA.




Remedy:

  • Check the terminal connection.
F009
Overbraking
Cause: Sudden braking or load inertia too high.



Remedy:

  • Increase the deceleration time.

  • Install a module unit with a braking resistor if necessary.

  • Check the main supply voltage to ensure it is under the maximum acceptable (20% over maximum main supply during run status).
F011
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.

  • See Mounting and temperature conditions in manual.
F012
Process overload
Cause: Process overload.



Remedy:

  • Check that drive parameters and application processes are compatible.
F013
Motor overload
Cause: Triggered by excessive motor current.



Remedy:

  • Check configuration of motor thermal protection and motor load.
F014
1 Output phase loss
Cause: Loss of one phase on drive output.



Remedy:

  • Check the connections from the drive to the motor.

  • If using a downstream contactor, make sure the connection, cable, and contactor are right.
F015
3 Output phases loss
Cause:

  • Motor not connected.

  • Motor power too low, below 6% of the rated drive current.

  • Output contactor open.

  • Transient instability in the motor current.




Remedy:

  • Check the connections from the drive to the motor.

  • Test on a low power motor or without a motor. In factory settings mode, motor phase loss detection is active (Output Phase loss detection 605 = 01).

  • To check the drive in a test or maintenance environment, without having to use a motor with the same rating as the drive, deactivate motor phase loss detection (605 = 00).

  • Check and optimize IR compensation (310), Rated motor voltage (304/305), and perform Auto-tuning (318).
F016
Main overvoltage
Cause:

  • Line voltage too high: At drive power on, supply is 10% over maximum acceptable voltage level.

  • At power with no run command, 20% over maximal line supply.

  • Disturbed mains supply.




Remedy:

  • Turn Off the Drive. Check and adjust the line voltage.

  • After line come back to nominal voltage (within tolerance) do power On.

  • If intermittent F016 code appears, set R1 assignment (205) to 01 and it can be connected to upstream protection to avoid overvoltage in the drive.
F017
Input phase loss
Cause:

  • Drive incorrectly supplied or a fuse blown.

  • Failure of one phase.

  • 3-phase ATV310 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 reporting of this fault type by setting Input Phase loss detection (606) to 00.
F021
Load short circuit
Cause:

  • Short-circuit at drive output.

  • Short circuit detection at the run command or DC injection command if parameter IGBT Test (608) is set to 01.




Remedy:



  • Check the cables connecting the drive to the motor and the condition of motor insulation.
F022
Modbus interruption
Cause:

  • Interrupted communication on the Modbus network.




Remedy:



  • Check the connections of communication bus.

  • Check the time-out (parameter Modbus time out 704).

  • Refer to the Modbus user manual.
F024
HMI communication
Cause:

  • Communication interruption with the external display terminal.




Remedy:



  • Check the terminal connection.
F029
Process underload
Cause:

  • Process underload.

  • Time that motor current is below the Application Underload threshold 211 exceeds the Application underload time delay 210 to protect the application.




Remedy:



  • Check that drive parameters and application processes are compatible.
F027
IGBT overheat
Cause:

  • Drive overheated.

  • IGBT internal temperature is too high for the ambient temperature and load.




Remedy:



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

  • Reduce the Switching frequency (315).

  • Wait for the drive to cool down before restarting.
F031
Incorrect configuration
Cause:

  • HMI block replaced by an HMI block configured on a drive with a different rating.

  • The current configuration of customer parameters is inconsistent.




Remedy:



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

  • If the fault remains after reverting to the factory settings, contact your local Schneider Electric representative.
F032 (1)
Invalid configuration
Cause:

  • Invalid configuration.

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

  • The configuration upload has been interrupted or is not fully finished.




Remedy:



  • Check the configuration loaded previously.

  • Load a compatible configuration.
F030
Undervoltage
Cause:

  • Line supply too low.

  • Transient voltage dip.




Remedy:



  • Check the voltage and parameters on the Undervoltage phase loss menu (607).
InIt
Auto-initialization on start
Cause:

  • Macro controller initialization.

  • Searching communication configuration.




Remedy:


No specific remedy listed (Status message).
COM.E (1)
Communication error
Cause:

  • 50 ms time out error.

  • This message appears after 220 retry attempts.




Remedy:


Check communication wiring and configuration.
A-17 (1)
Key alarm
Cause:

  • Key pressed down for longer than 10 seconds.

  • Membrane switch disconnected.

  • Display terminal woken up while a key is being pressed.




Remedy:


Check keypad/membrane buttons.
cLr (1)
Confirm fault reset
Cause:

  • This message appears if the STOP key is pressed while the display terminal is displaying a fault.




Remedy:


Confirmation step.
dEU.E (1)
Drive mismatch
Cause:

  • Drive type (brand) does not match display terminal type (brand).




Remedy:


Ensure terminal and drive brands match.
rOM.E (1)
ROM abnormality
Cause:

  • ROM abnormality detected by checksum calculation.




Remedy:


Hardware check required.
rAM.E (1)
RAM abnormality
Cause:

  • Display terminal RAM abnormality detected.




Remedy:


Hardware check required.
CPU.E (1)
Other fault
Cause:

  • The other detected fault.




Remedy:


Check device general status.