Schneider ATV320 Solar Drive Fault Codes

Complete reference list of Schneider ATV320 Solar Pump Drive fault codes. Learn to troubleshoot MPPT status messages, USF (Undervoltage), and Dry Run (ULF) protection.

Schneider ATV320 Solar Fault Codes Reference Table

Schneider ATV320 Solar Fault Codes Reference Table

Schneider ATV320 Solar Fault Codes Reference Table

Fault Code and Meaning Cause and Remedy
AnF
Load slipping error		 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: It 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.
blF
Brake control error		 Cause: Brake release current not reached, or 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 [Brk Release Current] Ibr and [Brake release I Rev] Ird settings.
  • Apply the recommended settings for [Brake engage freq] bEn.
brF
Brake feedback error		 Cause: The brake feedback contact does not match the brake logic control, or the brake does not stop the motor quickly enough.

Remedy:
  • Check the feedback circuit and the brake logic control circuit.
  • Check the mechanical state of the brake.
  • Check the brake linings.
CFF
Incorrect configuration error		 Cause: Option module changed or removed, or Control block replaced by a control block configured on a drive with a different rating, or the current configuration is inconsistent.

Remedy:
  • Check that there are no detected module errors.
  • In the event of the option module being changed/removed deliberately, see the remarks below.
  • Return to factory settings or retrieve the backup configuration, if it is valid.
CFI
Invalid configuration error		 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.
CFI2
Configuration transfer error		 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.
CnF
Fieldbus module communication interruption error		 Cause: Communication interruption on communication module.

Remedy:
  • Check the environment (electromagnetic compatibility).
  • Check the wiring.
  • Check the time-out.
  • Replace the option module.
  • Contact Schneider Electric Product Support.
CoF
CANopen communication interruption error		 Cause: Communication interruption on the CANopen® bus.

Remedy:
  • Check the communication bus.
  • Check the time-out.
  • Refer to the CANopen® User manual.
CrF1
Precharge capacitor error		 Cause: Charging relay control detected error or charging resistor damaged.

Remedy:
  • Turn the drive off and then turn on again.
  • Check the internal connections.
  • Contact Schneider Electric Product Support.
CSF
Channel switching detected error		 Cause: Switch to not valid channels.

Remedy:
  • Check the function parameters.
dlF
Dynamic load detected error		 Cause: Abnormal load variation.

Remedy:
  • Check that the load is not blocked by an obstacle.
  • Removal of a run command causes a reset.
EEF1
EEprom control error		 Cause: Internal memory detected error, control block.

Remedy:
  • Check the environment (electromagnetic compatibility).
  • Turn off, reset, return to factory settings.
  • Contact Schneider Electric Product Support.
EEF2
EEprom power error		 Cause: Internal memory detected error, power board.

Remedy:
  • Check the environment (electromagnetic compatibility).
  • Turn off, reset, return to factory settings.
  • Contact Schneider Electric Product Support.
EPF1
External error		 Cause: Event triggered by an external device, depending on user.

Remedy:
  • Check the device which caused the triggering and reset.
EPF2
Fieldbus external detected error		 Cause: Event triggered by a communication network.

Remedy:
  • Check for the cause of the triggering and reset.
fbE
Function block error		 Cause: Function block detected error.

Remedy:
  • See [FB Error] fbFt for more details.
fbES
Function block stop error		 Cause: Function blocks have been stopped while motor was running.

Remedy:
  • Check [FB Motor Stop Type] fbSn configuration.
FCF1
Output contactor closed error		 Cause: The output contactor remains closed although the opening conditions have been met.

Remedy:
  • Check the contactor and its wiring.
  • Check the feedback circuit.
FCF2
Output contactor opened error		 Cause: The output contactor remains open although the closing conditions have been met.

Remedy:
  • Check the contactor and its wiring.
  • Check the feedback circuit.
HCF
Boards compatibility error		 Cause: The [Boards 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.
HdF
IGBT desaturation error		 Cause: Short-circuit or grounding at the drive.

Remedy:
  • Check the cables connecting the drive to the motor, and the motor insulation.
ILF
Internal link error		 Cause: Communication interruption between option module and drive.

Remedy:
  • Check the environment (electromagnetic compatibility).
  • Check the connections.
  • Replace the option module.
  • Contact Schneider Electric Product Support.
InF1
Internal error 1 (Rating)		 Cause: The power board is different from the board stored.

Remedy:
  • Check the reference of the power board.
InF2
Internal error 2 (Soft)		 Cause: The power board is incompatible with the control block.

Remedy:
  • Check the reference of the power board and its compatibility.
InF3
Internal error 3 (Intern Comm)		 Cause: Communication interruption between the internal cards.

Remedy:
  • Check the internal connections.
  • Contact Schneider Electric Product Support.
InF4
Internal error 4 (Manufacturing)		 Cause: Internal data inconsistent.

Remedy:
  • Re-calibrate the drive (performed by Schneider Electric Product Support).
InF6
Internal error 6 (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 ATV320.
InF9
Internal error 9 (Measure)		 Cause: The current measurements are incorrect.

Remedy:
  • Replace the current sensors or the power board.
  • Contact Schneider Electric Product Support.
InFA
Internal error 10 (Mains)		 Cause: The input stage is not operating correctly.

Remedy:
  • Contact Schneider Electric Product Support.
InFb
Internal error 11 (Temperature)		 Cause: The drive temperature sensor is not operating correctly.

Remedy:
  • Replace the drive temperature sensor.
  • Contact Schneider Electric Product Support.
InFE
Internal error 14 (CPU) error		 Cause: Internal microprocessor detected error.

Remedy:
  • Turn off and reset.
  • Contact Schneider Electric Product Support.
LCF
Input contactor error		 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 supply mains /contactor /drive connection.
LFF3

AI3 4-20mA loss error		 Cause:
Loss of the 4-20 mA reference on analog input AI3.

Remedy:
Check the connection on the analog inputs.
OBF

DC bus overvoltage error		 Cause:
  • Braking too sudden or driving load.
  • Supply 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 supply voltage.
OCF

Overcurrent error		 Cause:
  • Parameters in the [Settings] SET- and [Motor control] DRC- 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 overheating error		 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

Process overload error		 Cause:
Process overload.

Remedy:
  • Check and remove the cause of the overload.
  • Check the parameters of the [Process overload] OLD- function.
OLF

Motor overload error		 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

Single output phase loss error		 Cause:
Loss of one phase at drive output.

Remedy:
Check the connections from the drive to the motor.
OPF2

Output phase loss error		 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 [No Error Triggered] OAC.
  • Test on a low power motor or without a motor: In factory settings mode, motor phase loss detection is active. To check the drive in a test environment, deactivate motor phase loss detection.
  • Check and optimize the parameters: [IR compensation] UFR, [Nom Motor Voltage] UNS and [Nom Motor Current] NCR and perform [Autotuning] TUN.
OSF

Supply mains overvoltage error		 Cause:
  • Supply voltage too high.
  • Disturbed mains supply.

Remedy:
Check the supply voltage.
OTFL

DI6=PTC overheat error		 Cause:
Overheating of PTC probes detected on input DI6.

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.
PHF

Input phase loss error		 Cause:
  • Drive incorrectly supplied or a fuse blown.
  • One phase missing.
  • 3-phase ATV320 used on a single-phase supply mains.
  • Unbalanced load.

Remedy:
  • Check the power connection and the fuses.
  • Use a 3-phase supply mains.
  • Disable the detected error by [InPhaseLoss Assign] IPL = [No].
PEFL

DI6=PTC probe error		 Cause:
PTC probe on input DI6 open or short-circuited.

Remedy:
Check the PTC probe and the wiring between it and the motor/drive.
SAFF

Safety function detected error		 Cause:
  • Debounce time exceeded.
  • SS1 threshold exceeded.
  • Incorrect configuration.
  • SLS type overspeed detected.

Remedy:
  • Check the safety functions configuration.
  • Check the ATV320 Integrated safety Functions manual.
  • Contact Schneider Electric Product Support.
SCF1

Motor short circuit error		 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.
SCF3

Ground short circuit error		 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.
SCF4

IGBT short circuit error		 Cause:
Power component detected error.

Remedy:
Contact Schneider Electric Product Support.
SCFS

Motor short circuit error		 Cause:
Short-circuit at drive output.

Remedy:
  • Check the cables connecting the drive to the motor, and the motor insulation.
  • Contact Schneider Electric Product Support.
SLF1

Modbus communication interruption error		 Cause:
Communication interruption on the Modbus bus.

Remedy:
  • Check the communication bus.
  • Check the time-out.
  • Refer to the Modbus User manual.
SLF2

PC communication interruption error		 Cause:
Communication interruption with PC Software.

Remedy:
  • Check the PC Software connecting cable.
  • Check the time-out.
SLF3

HMI communication interruption error		 Cause:
Communication interruption with the graphic display terminal or remote display terminal.

Remedy:
  • Check the terminal connection.
  • Check the time-out.
SOF

Motor overspeed error		 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 has been reached.

Remedy:
  • Check the motor, gain and stability parameters.
  • Add a braking resistor.
  • Check the size of the motor/drive/load.
  • Verify parameters for [Frequency meter].
  • Verify the consistency between [Max Frequency] and [High Speed].
SPF

Encoder feedback loss error		 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.
SSF

Torque limitation error		 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 limit detect].
TJF

IGBT overheating		 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

Autotuning detected error		 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.
tSF

Tank Probe Error		 Cause:
  • Tank water probe disconnected.
  • Tank water probe broken.
  • Alarm threshold too low ([Probe Threshold] LPTP).

Remedy:
  • Check the liquid probe connexion.
  • Check [Liquid Threshold] LPT and [Probe Threshold] LPTP parameters.
ULF

Process underload error		 Cause:
Process underload.

Remedy:
  • Check and remove the cause of the underload.
  • Check the parameters of the [Process underload] ULD- function.
USF

Supply mains undervoltage error		 Cause:
  • Supply mains too low.
  • Transient voltage dip.

Remedy:
Check the voltage and the parameters of [Undervoltage handling] USB-.
 

Troubleshooting Solar Pumping Behavior

On the ATV320 Solar, what looks like a fault is often just the drive reacting to the environment (Sunlight or Water Level).

  • USF (Undervoltage Supply Fault): In an industrial setting, this is bad. In a solar setting, this is normal behavior every evening. As the sun sets, the PV voltage drops, and the drive enters the “USF” state. It stays asleep until the voltage rises again the next morning.
  • ULF (Underload / Dry Run): The drive monitors the motor torque. If the borehole runs dry, the pump loses its load. The ATV320 triggers ULF to stop the motor and protect the pump bearings. It will restart automatically after a programmed timer.
  • STO (Safe Torque Off): Even though it is a pump drive, the SIL3 safety inputs are still active. If the STO terminals are not jumpered (or if an external E-Stop is pressed), the pump will not run regardless of how much sun is available.

Frequently Asked Questions (FAQ)

Q: The drive speed fluctuates constantly. Is the MPPT broken?

A: No, this is the MPPT (Maximum Power Point Tracking) working correctly.
The drive constantly adjusts the motor speed (Hz) to find the “sweet spot” of voltage and current from the solar panels. On a partly cloudy day, the speed will fluctuate up and down to match the changing irradiance.

Q: How do I stop the drive from tripping on “USF” during clouds?

A: USF means the DC bus voltage is too low.
1. Check if your solar string voltage (Voc) is sufficient for the drive rating.
2. You can lower the Undervoltage Management threshold in the Solar menu, but be careful not to drop it below the motor’s operating capability.

Q: What does “tUn” (Autotune) mean on a solar setup?

A: Before running the pump for the first time, it is highly recommended to perform an Autotune.
Navigate to drC- → tUn and set to YES while the motor is connected and cold. This ensures the drive knows the exact resistance of the long submersible cable, preventing nuisance Overcurrent (OCF) trips.

 

 

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