Standard wiring of the digital inputs (LI1-LI6) and the manual speed-reference potentiometer on analog input AI1, on the ATV61 control terminal block A1. These inputs are typically used for run/stop commands (LI1, LI2) and manual speed reference selection.

Relevant to FCF2 (output contactor stuck open) and the OCC- (output contactor command) function.

Remotely mountable graphic control panel for ATV61 / ATV71 drives, used for parameter programming, fault-code display, and drive status monitoring.

Built-in display panel mounted directly on the ATV61 drive body, showing fault codes and basic parameters on a 7-segment display.

Cause: Supply voltage dropped below the allowed threshold, or a brief mains interruption occurred.

Remedy: Measure L1-L2-L3 line voltage and compare to the SUP display. Increase the undervoltage timeout (menu 1.8 Fault Management > Undervoltage Mgt) from 0.2s to 5-10s if nuisance-tripping.

Cause: Line voltage too high, or disturbed line supply. Occurs while the drive is stopped.

Remedy: Check the line voltage; add an input line reactor if this recurs.

Cause: Braking too abrupt, or an overhauling high-inertia load feeding energy back into the DC bus while running.

Remedy: Increase deceleration time (dEC) or fit a braking resistor.

Cause: Drive incorrectly supplied or a blown fuse, one phase failed, a 3-phase ATV61 run on a single-phase supply, or unbalanced load.

Remedy: Check fuses, the input contactor, and L1/L2/L3 connections.

Cause: One of the three output phases to the motor is lost.

Remedy: Check the motor cable and U/V/W terminals.

Cause: Complete loss of electrical continuity between drive and motor.

Remedy: Inspect the full output wiring path.

Cause: Fault in the DC-bus capacitor precharge circuit or the charging thyristors.

Remedy: Check thyristors via [TEST THYRISTORS]; fully power-cycle the drive.

Cause: The drive fails to power up even though [Mains V. time out] (LCt) has elapsed.

Remedy: Check the input contactor, its wiring, and the timeout setting.

Cause: Output current exceeded ~200% of rated value; too-fast acceleration, mechanical jam, or an undersized drive.

Remedy: Increase acceleration time (ACC), check for mechanical binding, verify the drive is correctly sized for the load.

Cause: Motor current exceeds the calculated thermal capacity; excessive mechanical load or wrong thermal setting (ItH).

Remedy: Check mechanical load, correct ItH per motor nameplate, and let the motor cool before restart.

Cause: Phase-to-phase short circuit in the motor cable or windings.

Remedy: Disconnect the motor cable from U/V/W and megger-test (500V) insulation between phases and frame (below 1 MΩ means motor rewind/replace).

Cause: High-impedance short circuit on the output path (often marginal cable insulation).

Remedy: Check motor cable condition and length (an output filter may be needed for long cable runs).

Cause: Significant ground leakage current at the output — common with multiple motors in parallel or damaged insulation.

Remedy: Megger-test cable and motor insulation to ground.

Cause: Internal power-component (IGBT) failure.

Remedy: Run the [1.10 DIAGNOSTICS] / [TRANSISTOR TEST]; usually requires power-board repair or replacement.

Cause: A short circuit detected at the drive output — not maskable even with Fault Inhibition enabled.

Remedy: Inspect motor cable/insulation and run diagnostics.

Cause: Current mismatch between power block A and B (parallel power-cell drives).

Remedy: Check thyristors ([TEST THYRISTORS]), IGBTs ([TRANSISTOR TEST]), and the current transformer.

Cause: Motor fails to turn despite a run command; heavy or locked load.

Remedy: Check mechanical load, bearings, and coupling.

Cause: Heatsink temperature exceeded the limit set to protect the IGBTs.

Remedy: Check the cooling fan, clean heatsink dust, and verify ambient ventilation.

Cause: Junction temperature measured directly on the output transistors is too high.

Remedy: Check load/motor/drive sizing, reduce switching frequency (SFr), and let it cool before restarting.

Cause: The motor-mounted PTC thermal probe reported an over-temperature.

Remedy: Check motor load/size, ventilation, and PTC probe type/condition; wait for the motor to cool before restarting.

Cause: The PTC probe circuit is open or short-circuited.

Remedy: Check the probe and wiring between motor and drive.

Cause: Load overhauls the motor faster than commanded, or the motor was already spinning before the Run command. Actual speed exceeded [Max Frequency] (HSP) plus tolerance.

Remedy: Enable "Catch on the Fly", check encoder configuration if fitted, and review the speed-reference path.

Cause: The speed feedback signal (encoder/tacho) is lost.

Remedy: Check encoder wiring, power supply, and connections.

Cause: Encoder feedback fault.

Remedy: Check [Number of pulses] (PGI) and [Encoder type] (EnS) parameters, verify encoder mechanical/electrical operation, power, and connections; reverse motor or encoder signal direction if needed.

Cause: Autotuning could not complete. The motor must be at standstill, properly wired, with correct nameplate data entered.

Remedy: Common pitfalls: tuning with the brake not released on a hoist, tuning a star-connected motor with delta nameplate data, or tuning over a long cable without an output filter.

Cause: The drive switched into torque limitation.

Remedy: Check for mechanical problems and the torque-limitation function parameters.

Cause: The brake-release current did not reach the configured threshold.

Remedy: Check motor/brake wiring and the Ibr and bEn parameters.

Cause: The configured maintenance/service reminder time has been reached.

Remedy: Perform scheduled maintenance and reset the timer in parameters.

Cause: Communication fault on the installed communication card.

Remedy: Check link/activity LEDs on the drive port and switch, rule out IP conflicts, verify the timeout setting.

Cause: Communication interruption on the CANopen bus.

Remedy: Check bus cable, termination, and node addressing.

Cause: Interruption on the Modbus bus.

Remedy: Check bus cable, timeout, and addressing per the Modbus manual.

Cause: Communication error between drive and PC configuration software.

Remedy: Check the PC connection cable and timeout.

Cause: Communication with the graphic display terminal is lost.

Remedy: Check terminal connection and timeout.

Cause: Interruption or data-transfer error on the internal high-speed link between the drive's control card and power card.

Remedy: Check physical connections between the two boards, verify cables/connectors aren't damaged, and check grounding/shielding (EMI can be a cause).

Cause: The PID feedback is below the lower limit.

Remedy: Check PID feedback function and its supervision threshold/delay.

Cause: The 4-20mA reference signal on the respective analog input has dropped out.

Remedy: Measure loop current, check transmitter power and correct 4-20mA input configuration.

Cause: Internal memory fault on the control card.

Remedy: Check the environment for EMC issues, power-cycle the drive, restore factory settings; recurring faults require board repair/replacement.

Cause: Internal memory fault on the power card.

Remedy: Same approach as EEF1; if it recurs after a factory reset, board memory failure is likely and replacement is needed.

InF1: Rating error — drive nameplate rating mismatched with the power board.

InF2: Incompatible power board for this drive model/rating.

InF3: Internal serial link — communication between internal boards disrupted.

InF4: Internal manufacturing-area data inconsistent — requires recalibration by Schneider Electric support.

InF6: Installed option card not recognized — check its compatibility.

InF7: Incomplete hardware initialization — power-cycle the drive.

InF8: Control power supply fault — check the control-section power supply.

InF9: Internal current-measurement error.

InFA: Internal circuit fault (mains-related).

InFb: Internal temperature sensor fault.

InFC: Internal timing-measurement fault.

InFE: CPU fault.

General remedy: Try a reset first; if it recurs, contact Schneider Electric technical support — these usually indicate control/power-board failure.

Cause: A short circuit or grounding at the drive output caused IGBT desaturation.

Remedy: Check the motor cables and motor insulation (1000V megger test). Run the Transistor Test from the 1.10 Diagnostics menu. Contact technical support if it recurs.

Cause: The [CARDS PAIRING] (PPI) function is active and a drive card has been changed; firmware/hardware mismatch between control and power boards.

Remedy: Reinsert the original card, or if changed deliberately, confirm the configuration by entering the [Pairing password] (PPI); alternatively update firmware on both boards.

Cause: The loaded configuration is incompatible with the drive's hardware or firmware version (e.g. [Max frequency] (tFr) set above 599Hz).

Remedy: Check the loaded configuration, load a compatible one, or correct the out-of-range parameter.

Cause: The Power Removal (Safe Torque Off) safety function was activated while a Run command was active.

Remedy: Check the safety circuit and STO inputs; confirm the safety activation was intentional.

Cause: The [Power Identification] (Prt) parameter does not match the installed power/control board; typically occurs after replacing the control board or power board.

Remedy: Press and hold ENT to select and save the correct Power ID matching the drive's rating plate. If the control board was intentionally replaced, set the Prt parameter per Schneider's replacement procedure.

Cause: Process load exceeded the [Process Overload Threshold]. This comes from process monitoring, not the motor thermal model.

Remedy: Check process conditions (e.g. blockage, excess mechanical load) and the threshold setting.

Cause: Process load fell below the [Process Underload Threshold] — the classic "broken belt" or "dry pump" indicator on fans and pumps.

Remedy: Check the belt, mechanical coupling, and presence of fluid/product in the system.

Cause: No fluid flow detected in a pumping system.

Remedy: Check the no-flow detection parameters (per the drive's supplied documentation).

Cause: The damper remains closed although opening conditions were met.

Remedy: Check the damper and its wiring, feedback circuit, and the function's time delay.

Cause: The output contactor remains closed despite an open command.

Remedy: Check the contactor, its wiring, and the feedback circuit.

Cause: The output contactor remains open although closing conditions have been met.

Remedy: Check the contactor, its wiring, and the feedback circuit.

Cause: A digital input/control bit configured as [External error] was triggered — typically a vibration switch, motor PTC relay, gas sensor, or upstream PLC fault relay.

Remedy: Trace and check the device wired to this input.

Cause: Same concept as EPF1, but triggered via the communication network from the master controller.

Remedy: Check the cause on the master PLC/controller side and reset once resolved.

Cause: A digital input configured under the [External fault] parameter (positive or negative logic) was activated.

Remedy: Check the connected signal source (e.g. an external safety interlock).

Cause: Fault raised by one of the drive's application-level functions (varies by which function is active).

Remedy: Check the relevant application function's settings in the programming manual.

Cause: Rotor/encoder electrical-alignment issue on Permanent Magnet Synchronous Motors (PMSM).

Remedy: If using a known-good Schneider PMSM, check electrical alignment; otherwise re-tune the motor.

Cause: The AI2 analog input signal is out of the configured range (broken wire or wrong 0-20/4-20mA setting).

Remedy: Check AI2 wiring, signal range, and the input-type configuration.

Cause: The speed measured by the encoder does not match the drive's estimated/commanded speed.

Remedy: Check encoder mechanical mounting, wiring, rotation direction, and the pulse-count parameter (PGI).

Cause: Functional failure in the encoder or its interface card.

Remedy: Check the encoder interface card, wiring, and power supply; replace if needed.

Cause: The braking resistor is under excessive thermal stress — frequent or overly aggressive braking.

Remedy: Review the braking duty cycle and resistor sizing; a higher-power resistor may be required.

Cause: Braking-unit feedback does not match the expected state.

Remedy: Check the external braking unit's wiring and feedback circuit.

Cause: Short circuit at the output of the external braking unit or braking resistor.

Remedy: Check braking resistor/module wiring and the [Brake res. fault Mgt] (bUb) parameter.

Cause: The damper remains open although a close command was issued.

Remedy: Check the damper mechanism, wiring, and feedback circuit.

Cause: Communication between an installed expansion/option card and the main control board is lost.

Remedy: Check that the option card is properly seated, connector pins are clean, and firmware is compatible.