Schneider ATV12 Drive Fault Codes

Complete reference list of Schneider Altivar 12 (ATV12) fault codes. Learn to interpret 7-segment LED errors like OCF, SCF, and tH1, and reset common faults.

This guide provides the most updated reference data for 2026 to help you decipher these cryptic abbreviations and get your small machinery back online.

Schneider ATV12 Fault Codes Reference Table

Use the search bar in the table below to quickly find your specific error code.

Fault Code and Meaning Cause and Remedy
CrF1
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 your local Schneider Electric representative.
InF1
Unknown drive rating		 Cause: The power card is different from the card stored.

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

Remedy:
  • Contact your local Schneider Electric representative.
InF3
Internal serial link		 Cause: Communication interruption between the internal cards.

Remedy:
  • Contact your local Schneider Electric representative.
InF4
Invalid industrialization zone		 Cause: Inconsistent internal data.

Remedy:
  • Contact your local Schneider Electric representative.
InF9
Current measurement circuit		 Cause: Current measurement is not correct due to hardware circuit.

Remedy:
  • Contact your local Schneider Electric representative.
----
Problem of application Firmware		 Cause: Invalid application firmware update using the Multi-Loader tool.

Remedy:
  • Flash again the application firmware of the product.
InFb
Internal thermal sensor detected fault		 Cause:
  • The drive temperature sensor is not operating correctly.
  • The drive is in short circuit or open.

Remedy:
  • Contact your local Schneider Electric representative.
InFE
Internal CPU		 Cause: Internal microprocessor.

Remedy:
  • Turn the drive off and then back on again.
  • Contact local Schneider Electric representative.
OCF
Overcurrent		 Cause:
  • Parameters in the Motor control menu (drC) 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 chokes.
  • Reduce the Switching frequency (SFr).
  • Check the ground connection of drive, motor cable and motor insulation.
SCF1
Motor or Ground short circuit		 Cause:
  • Short-circuit or grounding at the drive output.
  • Ground fault during running status.
  • Commutation of motors during running status.
  • Significant current leakage to ground if several motors are connected in parallel.

Remedy:
  • Check the cables connecting the drive to the motor, and the motor insulation.
  • Connect motor chokes.
SCF3
Ground short circuit		 Cause: See SCF1.

Remedy:
  • See SCF1 remedies.
SCF4
IGBT short circuit		 Cause: Internal power component short circuit detected at power-on.

Remedy:
  • Contact your local Schneider Electric representative.
SOF
Overspeed		 Cause:
  • Instability.
  • Overspeed associated with the inertia of the application.

Remedy:
  • Check the motor.
  • Overspeed is 10% more than Maximum frequency (tFr), so 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).
tnF
Auto-tuning		 Cause:
  • Motor not connected to the drive.
  • One 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 auto-tuning.
  • If an output contactor is being used, close it during auto-tuning.
  • Check that the motor is completely stopped.
LFF1
AI current lost fault		 Cause: Detection if AI1 is current, scaling > 3 mA, and input < 2 mA.

Remedy:
  • Check the terminal connection.
ObF
Overbraking		 Cause: Braking too sudden or driving load too high.

Remedy:
  • Increase the deceleration time.
  • Install a module unit with a braking resistor if necessary.
  • Check the line supply voltage.
OHF
Drive overheat		 Cause: Drive temperature too high.

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

Remedy:
  • Check the process and the parameters of the drive to be in phase.
OLF
Motor overload		 Cause: Triggered by excessive motor current.

Remedy:
  • Check the setting of the motor thermal protection, check the motor load.
OPF1
1 output phase loss		 Cause: Loss of one phase at drive output.

Remedy:
  • Check the connections from the drive to the motor.
  • In case of using downstream contactor, check the right connection, cable and contactor.
OPF2
3 output phase loss		 Cause: Motor not connected, low power, contactor open, or instability.

Remedy:
  • Check connections.
  • Test on a low-power motor (set OPL = YES).
  • To check without motor, deactivate OPL (= no).
  • Check parameters: UFr, UnS, nCr, and perform Auto-tuning.
OSF
Main overvoltage		 Cause: Line voltage too high or disturbed line supply.

Remedy:
  • Check and adjust the line voltage.
  • If intermittent, set Relay R1 to FLt and connect to upstream protection.
PHF
Input phase loss		 Cause: Incorrect supply, blown fuse, phase failure, or unbalanced load.

Remedy:
  • Check the power connection and the fuses.
  • Use a 3-phase line supply.
  • Disable the fault by setting IPL = no.
SCF5
Load short circuit		 Cause: Short-circuit at drive output or during run/DC injection.

Remedy:
  • Check the cables connecting the drive to the motor, and the motor's insulation.
SLF1
Modbus communication		 Cause: Interruption in communication on the Modbus network.

Remedy:
  • Check connections of communication bus.
  • Check time-out (ttO).
  • Refer to the Modbus user manual.
SLF2
SoMove communication		 Cause: Communication interruption with SoMove.

Remedy:
  • Check the SoMove connecting cable.
  • Check the time-out.
SLF3
HMI communication		 Cause: Communication interruption with the external display terminal.

Remedy:
  • Check the terminal connection.
SPIF
PI Feedback detected fault		 Cause: PID feedback below lower limit.

Remedy:
  • Check the PID function feedback.
  • Check supervision threshold (LPI) and time delay (tPI).
ULF
Process underload fault		 Cause: Process underload or motor current below threshold (LUL) for time (ULt).

Remedy:
  • Check the process and the parameters of the drive to be in phase.
tJF
IGBT overheat		 Cause: Drive overheated (IGBT temp too high).

Remedy:
  • Check load size.
  • Reduce Switching frequency (SFr).
  • Wait for the drive to cool.
EPF1
External detected fault		 Cause: Event triggered by an external device.

Remedy:
  • Check the device which caused the trip and reset.
CFF
Incorrect configuration		 Cause: HMI block replaced with different rating or inconsistent parameters.

Remedy:
  • Return to factory settings or retrieve valid backup.
  • Contact Schneider Electric if fault remains.
CFI
Invalid configuration		 Cause: Configuration loaded is inconsistent or upload interrupted.

Remedy:
  • Check configuration loaded previously.
  • Load a compatible configuration.
CFI2
Download invalid configuration		 Cause: Interruption of download operation (Loader/SoMove).

Remedy:
  • Check connection.
  • Restart download or restore factory setting.
USF
Undervoltage		 Cause: Line supply too low or transient dip.

Remedy:
  • Check voltage and Undervoltage Phase Loss Menu (USb) parameters.
InIt
On initializing itself		 Description:
  • Micro controller initializing.
  • Communication configuration search.
Com.E
Communication error (Flashing)		 Description:
  • 50ms time-out error.
  • Shown after 220 retry attempts.
A-17
Key alarm (Flashing)		 Description:
  • Key pressed > 10s.
  • Membrane switch disconnected.
  • Keypad woken up while key pressed.
cLr
Confirm Fault reset (Flashing)		 Description:
  • Appears if STOP key is pressed when there is a keypad fault.
dEU.E
Drive mismatch (Flashing)		 Description:
  • Drive type (brand) did not match with keypad type.
rOM.E
ROM abnormality (Flashing)		 Description:
  • Keypad ROM abnormality detected by checksum.
rAM.E
RAM abnormality (Flashing)		 Description:
  • Keypad RAM abnormality detected.
CPU.E
The other defect (Flashing)		 Description:
  • The other detected fault.
 

How to Read ATV12 Faults & History

The ATV12 navigation relies on a “Jog Dial” (Navigation Wheel). Here is how to access diagnostic data:

  • Active Faults: When the drive trips, the display flashes the mnemonic code (e.g., OCF). The drive will remain in this state until the fault is cleared.
  • Fault History (n-H): You can view the last 4 faults stored in the memory.
    Navigate to: MON (Monitoring) → M0H (Fault Detection) → nH (Fault History).
    n-1 is the most recent fault.
  • SoMove Software: For detailed analysis in 2026, connect your PC via the USB-to-RJ45 Modbus cable and use the Schneider SoMove software to view the drive status, thermal state, and operation time at the moment of failure.

Frequently Asked Questions (FAQ)

Q: What is the difference between “OCF” and “SCF”?

A: Both relate to excessive current, but the cause differs:
OCF (Overcurrent): Usually caused by mechanical load issues (jamming, inertia too high) or aggressive acceleration settings.
SCF (Short Circuit): Usually indicates a hard electrical fault. SCF1 is a short at the motor output; SCF3 is a ground fault. Check your motor cables immediately.

Q: The display shows “nSt”. Is this a fault?

A: No. nSt stands for Freewheel Stop.
This indicates that the drive has been commanded to stop, but no specific stop type (Ramp, DC Injection) is active, or a logic input assigned to “Freewheel Stop” is active. The drive is healthy but waiting for a valid run command.

Q: How do I reset the ATV12?

A:
1. Power Cycle: Turn off the main power, wait for the display to go completely dark, and turn it back on.
2. Logic Input: If you have configured a digital input (LI) to “Fault Reset” (rSF), toggle that input.
3. Automatic Restart: If the “Automatic Restart” (Atr) function is enabled, the drive may attempt to reset itself after the fault clears.

Comments

Post a Comment

Popular posts from this blog

Allen Bradley Kinetix 5500 Drive Fault Codes List

Complete guide to Allen Bradley Kinetix 5500 fault codes. Troubleshoot FLT codes, Single-Cable (DSL) feedback errors, shared bus faults, and perform diagnostics via Studio 5000. Kinetix 5500 Fault Codes Reference Table Kinetix 5500 Fault Codes Reference Table Kinetix 5500 Fault Codes Reference Table Fault Code and Meaning Cause and Remedy FLT S03 – MTR OVERSPEED FL Motor Overspeed Factory Limit Fault Cause: Motor speed has exceeded 125% of its maximum speed. Remedy: Check control loop tuning. FLT S04 – MTR OVERSPEED UL Motor Overspeed User Limit Fault Cause: Motor speed has exceeded motor overspeed user limit. Remedy: Check control loop tuning. Increase the Motor Overspeed UL attribute value. FLT S05 – MTR OVERTEMP FL Motor Overtemperature Factory Limit Fault Cause: Calculations based ...
Read more

Danfoss VACON 100 FLOW Drive Fault Codes List

Access the complete reference guide for Danfoss VACON 100 FLOW drive fault codes. Learn to diagnose Multipump communication errors, dry run faults, and use Vacon Live software. VACON 100 FLOW Fault Codes Reference Table VACON 100 FLOW Faults and Alarms VACON 100 FLOW - Fault Tracing Fault Code and Meaning Cause and Remedy Fault Code 1, ID 1 Overcurrent (Hardware Fault) Cause: There is too high a current (> 4 × IH) in the motor cable. a sudden heavy load increase a short circuit in the motor cables the motor is not the correct type the parameter settings are not properly made Remedy: Check the loading. Check the motor. Check the cables and connections. Make an identification run. Set the acceleration time longer (P3.4.1.2 and P3.4.2.2). Fault Code 1, ID 2 Overcurrent (Software Fault...
Read more

ABB ACH580 Drive Fault Codes List

Access the complete reference guide for ABB ACH580 HVAC drive fault codes. Learn to diagnose issues via the Hand-Off-Auto panel, BACnet integration, and Fireman’s Override. The ABB ACH580 is the industry-standard flagship drive for HVACR applications. Designed to control air handling units, cooling towers, and chillers, it ensures critical comfort and safety in buildings. When a malfunction occurs, the dedicated Hand-Off-Auto (HOA) control panel displays a 4-digit code alongside plain-text diagnostics, often integrated directly into the Building Management System (BMS). This guide provides the most updated reference to help you interpret these codes and maintain building environmental standards. ACH580 Fault Codes Reference Table Use the search bar below or browse the table to identify your specific error code: ABB ACH580 Drive Fault Codes List ABB ACH580 Drive Fault Codes List Fault Code and Meaning Cause and Remedy A2B1...
Read more