Schneider ATV312 Drive Fault Codes

Complete reference list of Schneider Altivar 312 (ATV312) fault codes. Learn to interpret LED errors like nSt (Freewheel), OCF, and SCF on this popular general-purpose drive.

Schneider ATV312 Fault Codes Reference Table

Schneider ATV312 Fault Codes Reference Table

Schneider ATV312 Fault Codes Reference Table

Fault Code and Meaning Cause and Remedy
bLF

[BRAKE CONTROL FAULT]
Cause:
  • Brake release current not reached.
  • Brake engage frequency threshold [Brake engage freq] (bEn) = [No] (nO) whereas the brake control [Brake assignment] (bLC) is assigned.
  • Loss of one phase at drive output.
  • Output contactor open.

Remedy:
  • Check the drive/motor connection.
  • Check the motor windings.
  • Check the [Brake release I FW] (Ibr) setting in the [APPLICATION FUNCT.] (FUn-) menu.
  • Apply the recommended settings for [Brake engage freq] (bEn).
CrF

[PRECHARGE FAULT]
Cause:
Precharge relay control or damaged precharge resistor.

Remedy:
Replace the drive.
EEF

[EEPROM FAULT]
Cause:
Internal memory issue.

Remedy:
  • Check the environment (electromagnetic compatibility).
  • Replace the drive.
IF1

[INTERNAL FAULT]
Cause:
Unknown rating.

Remedy:
  • Replace the drive.
  • Restart the drive.
  • Contact a Schneider Electric representative.
IF2

[INTERNAL FAULT]
Cause:
  • HMI card not recognized.
  • HMI card incompatible.
  • No display present.

Remedy:
  • Replace the drive.
  • Restart the drive.
  • Contact a Schneider Electric representative.
IF3

[INTERNAL FAULT]
Cause:
EEPROM issue.

Remedy:
  • Replace the drive.
  • Restart the drive.
  • Contact a Schneider Electric representative.
IF4

[INTERNAL FAULT]
Cause:
Industrial EEPROM issue.

Remedy:
  • Replace the drive.
  • Restart the drive.
  • Contact a Schneider Electric representative.
OCF / o.CF / OC.F

[OVERCURRENT]
Cause:
  • Parameters in the [SETTINGS] (SEt-) and [MOTOR CONTROL] (drC-) menus are incorrect.
  • Inertia or load too high.
  • Mechanical locking.
  • Phase/Ground Motor short-circuit.
  • Impedant short-circuit.

Remedy:
  • Check the parameters in [SETTINGS] (SEt-) and [MOTOR CONTROL] (drC-).
  • Check the size of the motor/drive/load.
  • Check the state of the mechanism.
SCF

[MOTOR SHORT CIRCUIT]
Cause:
  • Short-circuit at the drive output.
  • Significant ground leakage current at the drive output if several motors are connected in parallel.
  • 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.
SoF

[OVERSPEED]
Cause:
  • Instability.
  • Driving load too high.

Remedy:
  • Check the motor, gain and stability parameters.
  • Add a braking resistor.
  • Check the size of the motor/drive/load.
CnF

[NETWORK FAULT]
Cause:
Communication detected fault on the communication card.

Remedy:
  • Check the environment (electromagnetic compatibility).
  • Check the wiring.
  • Check the time out.
  • Replace the option card.
  • See the [CANopen fault mgt] (COL) parameter to define the stop mode.
CoF

[CANopen FAULT]
Cause:
Interruption in communication on the CANopen bus.

Remedy:
  • Check the communication bus.
  • Refer to the relevant product documentation.
EPF

[EXTERNAL FAULT]
Cause:
Depending on user.

Remedy:
Depending on user.
ILF

[INTERNAL LINK FAULT]
Cause:
Identification detected fault of the communication card by the drive.

Remedy:
  • Check that the option card is compatible with the drive.
  • Replace the option card.
LFF

[4-20mA LOSS]
Cause:
Loss of the 4-20 mA reference on input AI3.

Remedy:
Check the connection on input AI3.
ObF

[OVERBRAKING]
Cause:
Braking too sudden or driving load.

Remedy:
  • Increase the deceleration time.
  • Install a braking resistor if necessary.
  • Activate the [Dec ramp adapt.] (bra) function if compatible with the application.
OHF

[DRIVE OVERHEAT]
Cause:
Drive temperature too high.

Remedy:
Check the motor load, the drive ventilation and the environment. Wait for the drive to cool before restarting.
OLF

[MOTOR OVERLOAD]
Cause:
  • Triggered by excessive motor current.
  • [Cold stator resist.] (rSC) parameter value incorrect.

Remedy:
  • Check the [Mot. therm. current] (ItH) setting of the motor thermal protection, check the motor load. Wait for the drive to cool before restarting.
  • Remeasure [Cold stator resist.] (rSC).
OPF

[MOTOR PHASE LOSS]
Cause:
  • Loss of one phase at drive output.
  • Output contactor open.
  • Motor not connected or motor power too low.
  • 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 output phase loss detection is active. To check the drive in a test or maintenance environment without having to switch to a motor with the same rating as the drive, deactivate motor phase loss detection ([Output Phase Loss] (OPL) = [No] (nO)).
  • Check and optimize the [IR compensation] (UFr), [Rated motor volt.] (UnS), and [Rated mot. current] (nCr) parameters, and perform an [Auto tuning] (tUn) operation.
OSF

[MAINS OVERVOLTAGE]
Cause:
  • Line voltage is too high.
  • Disturbed line supply.

Remedy:
Check the line voltage.
PHF

[INPUT PHASE LOSS]
Cause:
  • Drive incorrectly supplied or a fuse blown.
  • Failure of one phase.
  • Three-phase ATV312 used on a single-phase line supply.
  • Unbalanced load (protection only operates with the drive on load).

Remedy:
  • Check the power connection and the fuses.
  • Reset.
  • Use a three-phase line supply.
  • Disable the detection by setting [Input phase loss] (IPL) = [No] (nO).
SLF

[MODBUS FAULT]
Cause:
  • Interruption in communication on the Modbus bus.
  • Remote display terminal enabled ([HMI command] (LCC) = [Yes]) and terminal disconnected.

Remedy:
  • Check the communication bus.
  • Refer to the relevant product documentation.
  • Check the link with the remote display terminal.
tnF

[AUTO TUNING FAULT]
Cause:
  • Special motor or motor whose power is not suitable for the drive.
  • Motor not connected to the drive.

Remedy:
  • Use the L ratio or the [Var. torque] (P) ratio (see [U/F mot 1 selected] (UFt)).
  • Check that the motor is present during auto-tuning.
  • If an output contactor is being used, close it during auto-tuning.
CFF

[INCORRECT CONFIG.]
Cause:
  • The current configuration is inconsistent.
  • Addition or removal of an option.

Remedy:
  • Return to factory settings or retrieve the backup configuration, if it is valid. See the [Restore config.] (FCS) parameter.
CFI

[INVALID CONFIG]
Cause:
  • Invalid configuration.
  • The configuration loaded in the drive via the serial link is inconsistent.

Remedy:
  • Check the configuration loaded previously.
  • Load a consistent configuration.
USF

[UNDERVOLTAGE]
Cause:
  • Insufficient line supply.
  • Transient voltage dip.
  • Damaged precharge resistor.

Remedy:
  • Check the voltage and the voltage parameter.
  • Tripping threshold in [UNDERVOLTAGE] (USF):
    ATV312....M2: 160 V
    ATV312....M3: 160 V
    ATV312....N4: 300 V
    ATV312....S6: 430 V
  • Replace the drive.
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.
A-17 (Flashing)

Alarm button
Cause:
  • A button has been held down for more than 10 seconds.
  • The keypad is disconnected.
  • The "keypad" wakes up when a button is pressed.

Remedy:
Release the button or check keypad connection.
cLr (Flashing)

Confirmation of detected fault reset
Cause:
This is displayed when the STOP button is pressed once during a remote terminal detected fault.

Remedy:
None required (informational).
dEU.E (Flashing)

Drive disparity
Cause:
The drive brand does not match that of the remote terminal.

Remedy:
Use a compatible remote terminal.
rOM.E (Flashing)

ROM anomaly
Cause:
The remote terminal detects a ROM anomaly on the basis of checksum calculation.

Remedy:
Replace remote terminal.
rAM.E (Flashing)

RAM anomaly
Cause:
The remote terminal detects a RAM anomaly.

Remedy:
Replace remote terminal.
CPU.E (Flashing)

Other detected faults
Cause:
Other detected faults.

Remedy:
Check drive diagnostics.
 

How to Read ATV312 Faults & History

The ATV312 is navigated using the central “Jog Dial”. Understanding the difference between a “Blocking” fault and a “Status” code is critical.

  • Status vs. Faults: The ATV312 display often confuses new users.
    • rdY: Ready (Healthy, waiting for command).
    • nSt: Freewheel Stop (Healthy, but the motor is coasting or logic is preventing start).
    • OCF/SCF/InF: These are actual faults that stop operation and require a reset.
  • Fault History (LFt): To view the most recent fault, navigate to the SUP- (Monitoring) menu and find the LFt (Last Fault) parameter. It stores the code of the last trip even after power is cycled.
  • Auto-Tuning (tUn): Many performance faults (like SLF or OCF) can be resolved by performing an Auto-Tune. Navigate to drC- → tUn and set it to YES while the motor is cold and stopped.

Frequently Asked Questions (FAQ)

Q: Why does the screen say “nSt” and the motor won’t start?

A: nSt stands for Freewheel Stop. It is a status, not a failure.
Common Causes:
1. 2-Wire Control safety: You turned the power on while the Run Switch (LI1) was already closed. Cycle the switch Off and On.
2. Stop Input: A digital input configured as “Free Stop” (NST) is active (open circuit).
3. Local Mode: You pressed the red STOP button on the keypad, overriding the terminal commands.

Q: What is “CFF” (Configuration Fault)?

A: This often happens after replacing a drive or swapping the control board.
Meaning: The configuration parameters do not match the hardware options.
Fix: You usually need to perform a Factory Reset. Go to drC- → FCS and change it to InI (Initialize). Hold the enter button for 2 seconds.

Q: How do I distinguish between “OCF” and “SCF”?

A:
OCF (Overcurrent): The motor is drawing too much current (Mechanical load too high, ramp too short). This is a “Soft” fault.
SCF (Short Circuit): This is a “Hard” electrical fault.
SCF1: Short circuit at the motor output.
SCF3: Ground fault (Motor wire touching earth). Do not reset repeatedly; check cables with a megohmmeter.

Comments

Popular posts from this blog

Allen Bradley Kinetix 5500 Drive Fault Codes List

Danfoss VACON 100 FLOW Drive Fault Codes List

ABB ACH580 Drive Fault Codes List