Schindler Altivar 212

The Key alarm indicates an issue with the display terminal's keypad. This fault is triggered if a key remains pressed for longer than 10 seconds, if the membrane switch is disconnected, or if the display terminal powers on while a key is already depressed.

This alarm indicates that the Altivar 212 drive is currently executing an auto-tuning procedure. It is a normal operational message and typically clears automatically upon completion of the tuning process.

This fault indicates an issue with the brake control system, where the brake release current may not have been reached or the brake engage frequency threshold ([Brake engage freq] (bEn)) is incorrectly set or not assigned despite brake control ([Brake assignment] (bLC)) being active. This can lead to improper motor braking or starting.

This fault indicates that the Altivar 212 drive has detected a cavitation condition in the motor, often resulting from excessive mechanical load or insufficient fluid flow, leading to a loss of speed or high torque.

This fault indicates that the current drive configuration is inconsistent, possibly due to the addition or removal of an option card. An inconsistent configuration can prevent proper drive operation.

This fault indicates that an invalid configuration has been loaded into the drive, typically via the serial link. The loaded configuration is inconsistent and prevents the drive from operating correctly.

This fault occurs when the Altivar 212 drive's configuration is invalid or inconsistent, typically after a configuration download via PC software. It can also indicate an unsuccessful transfer due to rating differences between the source and target drives (e.g., uploading an ATV212N4 configuration to an ATV212M3).

This alarm message is displayed when the STOP key is pressed on the embedded display terminal while a detected fault is present, indicating that a reset attempt is initiated.

This fault indicates an issue with an optional communication card installed in the drive. It is a read-only fault code that remains stored even after the cause disappears and is reset only by cycling the drive's power. The specific values of this parameter depend on the type of network card.

This fault indicates a detected communication issue on the CANopen bus. It implies a problem with the CANopen network connection or the CANopen option card itself.

This communication error indicates a 50 ms timeout, appearing after 220 retry attempts. It signifies a problem with the communication link between the drive and the remote display terminal, preventing proper data exchange.

This is a generic fault code indicating an unspecified 'other detected fault' by the display terminal's CPU. It suggests an internal issue that doesn't fall under more specific error categories like ROM or RAM abnormalities.

This fault indicates a problem with the drive's internal capacitor precharge circuit, potentially due to a faulty precharge relay control or a damaged precharge resistor. This prevents the drive from powering up correctly and charging its DC bus.

This alarm indicates that the Altivar 212 drive is currently applying DC braking to the motor. It is a normal operational message and should clear once the braking sequence is complete.

This alarm indicates that DC braking is active as part of the [Crankcase heating] (F355) function, typically when the motor is stopped to maintain temperature and prevent condensation.

This fault indicates an incompatibility between the connected display terminal and the drive. Specifically, the brand or type of the drive does not match that of the display terminal, preventing proper operation and communication.

This alarm is triggered if a graphic display option key has been held down for an extended period (more than 20 seconds) or if the graphic display option key itself is malfunctioning.

This fault signifies that the analog input signal at terminal VIA has dropped below the minimum level defined by parameter F633 ([Loss of VIA]), indicating a potential loss of speed reference signal or sensor input.

This fault indicates a communication error between the internal control CPUs of the Altivar 212 drive, suggesting an issue with the internal communication bus or external electromagnetic interference.

This fault is triggered when the [Auto Torque Boost] (F402) parameter is set too high or the motor impedance is too low, leading to excessive torque boost during operation or deceleration. It can also occur under specific deceleration conditions with Quadr. U/F control.

This fault indicates an inoperable condition of the control board CPU, suggesting a critical internal hardware failure within the Altivar 212 drive.

This fault indicates an incompatibility with the EEPROM power or a detected hardware fault within the Altivar 212 product, preventing proper operation.

This fault is detected at startup if the measured current during initial position detection is either too small or too large, indicating a mismatch with the motor's inductance or an output phase loss.

An internal EEPROM memory fault has been detected, indicating an issue with the drive's non-volatile memory. This can affect drive configuration and operation stability.

This fault indicates a data writing error has occurred in the EEPROM, potentially corrupting stored parameters or preventing proper parameter saving.

This fault occurs if power was removed from the Altivar 212 drive during a parameter reset operation, leading to a data writing error in the EEPROM. It can also indicate issues with initial position detection or motor inductance during auto-tuning.

This fault indicates a data reading error has occurred from the EEPROM, preventing the Altivar 212 drive from correctly retrieving stored parameters or configuration data.

This fault signals a ground fault in the motor or the motor cables, indicating an insulation breakdown or improper grounding in the output circuit of the Altivar 212 drive.

This alarm indicates that the number of digits required to display a value (e.g., frequency) on the embedded display terminal exceeds its four-digit capacity, meaning the value is too large to fit.

This alarm indicates that the operation panel is being used to stop the Altivar 212 drive in automatic control or remote control mode, acting as an emergency stop function.

This fault is triggered by an external condition, typically via a configured digital input. It indicates that an external device or safety circuit has signalled a fault condition to the drive.

This fault is detected when one or more output phases to the motor are lost, leading to an imbalance or interruption in motor current from the Altivar 212 drive. This can severely affect motor operation and cause damage.

This fault occurs when one or more input phases to the Altivar 212 drive are lost, indicating an issue with the incoming AC supply or its connection to the drive.

This fault indicates that a monitored condition in an external system, typically temperature, has exceeded its defined high-high threshold, as set by parameter F353 ([High high Thd]), triggering an error state.

This fault is triggered when parameters related to VIA or VIB analog input speed reference points are set improperly, leading to an inconsistent or erroneous speed command from the Altivar 212 drive.

This alarm occurs when the frequency setting signals at points 1 and 2 are configured too close to each other, indicating an insufficient separation in speed reference steps.

This fault indicates that the internal RAM on the control board of the Altivar 212 drive is inoperable, suggesting a critical hardware failure preventing normal operation.

This fault indicates that the internal ROM on the control board of the Altivar 212 drive is inoperable, suggesting a critical hardware failure preventing boot-up or program execution.

This fault indicates an inoperable condition of the main control board CPU (CPU fault 1) within the Altivar 212 drive, suggesting a critical hardware failure that halts drive operation.

This fault indicates a serial communication error over the RJ45 connection of the Altivar 212 drive, potentially due to issues with network devices, cabling, or communication settings.

This fault indicates an inoperable motor current sensor within the Altivar 212 drive, preventing accurate measurement of motor current and potentially leading to unprotected operation.

This fault indicates a general network communication error (not specific to RJ45) preventing proper data exchange between the Altivar 212 drive and a master controller.

This fault occurs when the graphic display option cable is disconnected, preventing communication between the Altivar 212 drive and the remote keypad.

This fault indicates a failure during the Altivar 212 drive's auto-tuning process, which can be caused by incorrect motor parameters, an oversized motor, an undersized cable, or the motor not being completely stopped.

This is a generic Altivar 212 drive fault code indicating an inoperable main control board, suggesting a severe internal hardware issue that prevents proper operation.

For the ATV310 drive, this fault indicates an issue within the internal DC bus precharge circuit. This typically involves a fault with the charging relay control or damage to the precharge resistor, preventing the DC bus capacitors from charging correctly upon power-up.

This ATV310 fault signifies an internal inconsistency where the power card and the stored control card versions are different or incompatible. The drive is unable to correctly identify its own power rating, indicating an internal hardware or firmware mismatch.

This ATV310 fault indicates that the installed power card is incompatible with the control card. This prevents the drive from operating correctly and points to an incorrect or mismatched power section component.

This ATV310 fault signifies an interruption in communication between the internal cards within the drive. This is a critical internal hardware communication issue that prevents proper drive control and monitoring.

This ATV310 fault suggests an inconsistency in the drive's internal data or configuration. It indicates an internal software or data integrity issue that requires specialist attention.

This ATV310 fault indicates that the drive's internal current measurement circuit is not operating correctly, typically due to a hardware circuit fault. This prevents the drive from accurately monitoring motor current, which is essential for protection and control.

This ATV310 fault indicates that the drive's internal temperature sensor is not functioning correctly. This could be due to a short circuit, an open circuit, or a general malfunction of the sensor, which compromises the drive's ability to monitor its own temperature for protection.

This ATV310 fault indicates an internal microprocessor fault within the drive's CPU. This is a critical internal hardware or firmware issue that prevents the drive from processing commands and operating correctly.

This fault occurs in the ATV310 drive due to excessive regenerative energy returned from the motor to the drive, causing the DC bus voltage to rise above its permissible limit. This is typically triggered by sudden deceleration or a high inertia load application.

For the ATV310 drive, this fault indicates that the current drawn by the motor has exceeded the drive's maximum permissible current limit. This is often caused by incorrect motor control parameters, an excessively high load or inertia, or mechanical binding in the driven system.

This fault occurs when the Drive thermal state (809) exceeds 118%. It indicates that the internal temperature of the drive has risen above its safe operating limits, potentially leading to derating or damage to power components.

For the ATV310 drive, this fault indicates that the current drawn by the motor, as monitored by the drive, suggests an overload condition originating from the mechanical process or application itself. It signifies that the mechanical load on the motor is too high.

The drive displays an F013 fault when the Motor thermal state (808) exceeds 118%. This indicates that the motor is operating beyond its safe thermal limits, risking damage to the motor windings.

For the ATV310 drive, this fault is detected when one phase on the drive's output to the motor is lost. This can be caused by poor electrical connections, damaged motor cables, or issues with a downstream contactor.

This ATV310 fault is detected when all three phases on the drive's output to the motor are lost. Common causes include a disconnected motor, a motor with insufficient power relative to the drive, an open output contactor, or transient instability in the motor current during operation.

This ATV310 fault occurs when the incoming line voltage supplied to the drive is excessively high. This can be triggered at power-on (10% over maximum acceptable voltage) or when idle (20% over maximal line supply), or by a disturbed mains supply.

For the ATV310 drive, this fault is detected when one or more phases of the main line supply to the drive are lost or significantly unbalanced. This protection primarily operates when the drive is under load and can be triggered by blown fuses or incorrect supply configuration (e.g., a 3-phase drive on a single-phase supply).

This ATV310 fault is triggered by a short-circuit or ground fault at the drive output, or within the motor itself. It can occur while the drive is running, due to motor switching, or from significant current leakage when multiple motors are connected in parallel.

This ATV310 fault indicates a ground fault condition detected in the system, typically at the drive output or within the motor/cabling. This poses a safety risk and can lead to equipment damage if not promptly addressed.

This ATV310 fault indicates an internal power component short circuit, specifically within the IGBTs (Insulated Gate Bipolar Transistors) of the drive's inverter section. This critical hardware failure is typically detected at power-on and requires specialized repair.

This ATV310 fault detects a short-circuit condition at the drive's output, impacting the motor or cabling. It can be triggered either at the run command or during a DC injection command, especially if parameter 608 (IGBT Test) is set to 01.

For the ATV310 drive, this fault occurs when communication on the Modbus network connected to the drive is interrupted. This can be due to physical connection issues, incorrect communication settings, or an improperly configured Modbus time-out.

This ATV310 fault indicates an interruption in communication with the external display terminal (HMI). This prevents control and monitoring of the drive via the HMI interface.

For the ATV310 drive, this fault indicates that the motor or application is operating at a speed significantly higher than expected, exceeding the drive's configured limits, potentially more than 10% above the Top frequency (parameter 308). This can be caused by control instability, high inertia loads, or incorrect speed loop parameters.

This ATV310 fault indicates that the internal temperature of the drive's IGBTs (Insulated Gate Bipolar Transistors) has reached an excessively high level. This condition is critical and is influenced by ambient temperature, motor load, and drive switching frequency, risking damage to the drive if not addressed.

This ATV310 fault occurs when the drive's auto-tuning function fails to complete successfully. This can be caused by the motor not being properly connected, a motor phase loss during the tuning process, using a special motor type incompatible with standard autotuning, or the motor rotating during the tuning procedure.

This fault is detected when the motor current drops below the Application Underload threshold (211) for a duration longer than the Application underload time delay (210). This condition indicates that the motor is running with insufficient load, and detection is active only during steady-state operation.

The Undervoltage fault occurs when the line supply voltage to the drive is too low or experiences a transient dip. This can lead to unstable drive operation or shutdown to protect internal components.

This fault indicates that the drive's configuration is inconsistent. It can occur if an HMI block from a drive with a different rating is installed, or if the customer parameters currently loaded are not valid for the drive.

This fault signifies that the configuration loaded into the drive, typically via the bus or a communication network, is inconsistent. It can also be triggered if the configuration upload process was interrupted or did not complete successfully.

For the ATV310 drive, this fault is detected if Analog input AI1 is configured for current (parameter 204.1 > 3 mA) and the actual analog input current falls below 2 mA. This indicates a loss of signal from the connected sensor or a wiring integrity issue at the input.

This fault indicates that the damper is locked in a closed position, preventing proper air flow or ventilation, which can lead to overheating or process issues. The drive typically locks in this fault mode.

This fault indicates that the damper is blocked open or soldered, preventing it from closing. This condition can affect temperature control or system operation by not restricting airflow as intended.

This alarm indicates that a value entered during programming exceeds either the maximum or minimum permissible range for that parameter.

This alarm indicates that the integral output power value, displayed as Pout&1MWh, has exceeded 999.99 kWh, indicating a data overflow.

This alarm displays the first and last data items in the AUH (Last Parameters Changed) data group, indicating the start and end of the list when accessed.

An internal fault of unknown rating has occurred within the drive. This indicates a general internal hardware or software issue that prevents normal operation.

An internal fault related to the Human-Machine Interface (HMI) card has been detected. This could be due to the HMI card not being recognized, being incompatible, or the display not being present.

An internal EEPROM memory fault has been detected.

An internal industrial EEPROM memory fault has been detected.

This message indicates that the microcontroller within the device is currently undergoing its initialization sequence. It may also signify that the system is actively searching for communication configurations.

This fault indicates a loss of the 4-20 mA analog input signal, which is typically used for speed reference or process feedback. This can occur even if the [4-20mA loss] (LFL) parameter is set to [No] (nO) on page 95.

This fault occurs when the accumulated input power value, typically measured in kWh, exceeds the maximum displayable value of 999.999 kWh, indicating a data overflow.

This fault indicates that the DC bus voltage within the drive has exceeded its safe operating limits, often referred to as "overbraking." This usually happens when the motor regenerates energy back into the drive during deceleration, and there's no braking resistor to dissipate it.

This fault indicates an overcurrent condition during motor acceleration by the Altivar 212 drive, often caused by excessively short acceleration times, incorrect motor control settings, or high-inertia loads.

This fault indicates a short circuit or ground fault condition detected specifically during the motor acceleration phase of the Altivar 212 drive, which can cause immediate shutdown.

This fault indicates an overcurrent condition during motor deceleration by the Altivar 212 drive, often due to an excessively short deceleration time or a ground fault.

This fault indicates a short circuit or ground fault condition detected specifically during the motor deceleration phase of the Altivar 212 drive, requiring immediate attention to prevent damage.

This fault indicates an overcurrent condition while the motor is running at a constant speed by the Altivar 212 drive, typically caused by abrupt load fluctuations or an abnormal load condition.

This fault indicates a short circuit or ground fault condition detected while the Altivar 212 drive is operating at a constant speed, potentially also due to a malfunctioning cooling fan.

This fault indicates a short circuit condition detected within the Altivar 212 drive's output inverter stage during motor startup, usually caused by a ground fault.

This overcurrent fault indicates that the motor current has exceeded the permissible limits, often due to incorrect drive or motor parameters, excessive mechanical load, or a mechanical locking condition. Sustained overcurrent can damage the motor or the drive.

This fault indicates a phase-to-phase output short circuit or a low motor impedance detected in the motor or its wiring during startup by the Altivar 212 drive.

This fault indicates that the Altivar 212 drive is overheating due to issues with its cooling system, ambient conditions, or internal sensor malfunction, leading to a trip.

This fault indicates that an external PTC thermistor embedded in the motor windings has detected a motor overtemperature condition, causing the Altivar 212 drive to trip and protect the motor.

This fault indicates that the internal temperature of the drive has exceeded its safe operating limits. This can be due to high ambient temperature, inadequate ventilation, or excessive load.

This fault indicates that the Altivar 212 drive is overloaded, often due to excessively short acceleration times, high DC injection current, incorrect motor control settings, or a rotating load.

This fault indicates a motor overload condition, potentially caused by incorrect motor control settings, a jammed motor, continuous low-speed operation, or excessive load from the Altivar 212 drive.

This fault is triggered by excessive motor current, indicating the motor is drawing more current than its thermal protection limits. An incorrect [Cold stator resist.] (rSC) parameter value can also lead to this fault. Continued operation under overload conditions can damage the motor.

This fault indicates an overvoltage condition during motor acceleration by the Altivar 212 drive, which can be caused by abnormal input voltage fluctuations, issues with the power network, or power factor capacitor switching.

This fault indicates an overvoltage condition during motor deceleration by the Altivar 212 drive, possibly due to excessively short deceleration times, overhauling loads, or fluctuating input voltage.

This fault indicates an overvoltage condition while the Altivar 212 drive is operating at a constant speed, often due to abnormal input voltage fluctuations, power network issues, or regenerative braking where the load causes the motor to run faster than the drive's output frequency.

This fault occurs when one or more phases are lost at the drive output to the motor. This can be caused by disconnected motor cables, an open output contactor, or operating with a motor whose power rating is too low for the drive. Instantaneous instability in the motor current can also trigger this fault.

This fault indicates that the incoming line voltage supply to the drive is too high or disturbed. Operating the drive with excessive input voltage can damage internal components.

This fault occurs when the calculated motor torque reaches or exceeds the level set by parameter F616 ([Overtorque level]), indicating that the motor is operating under excessive load and could be damaged.

This fault signifies a loss of one or more input phases to the drive. This can be due to incorrect power connection, a blown fuse, or using a three-phase drive on a single-phase line supply, especially under load. This protection only activates when the drive is operating under load.

This fault indicates that the prestart speed (F327) was not reached within the specified time (F328), or the load on the motor was too high during the prestart sequence of the Altivar 212 drive.

This fault indicates an abnormality detected within the Random Access Memory (RAM) of the display terminal. This suggests an internal memory corruption or hardware issue affecting the display terminal's ability to process and store temporary data.

This fault indicates an abnormality detected within the Read-Only Memory (ROM) of the display terminal, typically identified through a checksum calculation error. This suggests an internal data corruption or hardware issue within the display terminal's ROM.

This fault indicates a short-circuit or grounding fault at the drive output, affecting the motor connection. It can also be triggered by significant ground leakage current if multiple motors are connected in parallel to the drive.

This fault indicates an interruption in communication on the Modbus bus. It can also be triggered if a remote display terminal is enabled ([HMI command] (LCC) = [Yes] (YES), page 61) but is disconnected.

This overspeed fault indicates that the motor speed has exceeded its commanded or permissible limits. This typically results from system instability or an excessively high driving load, which can lead to loss of control.

This fault occurs in permanent magnet motors when the motor pulls out of synchronism, often due to a jammed motor, output phase loss, or sudden impact loads, leading to uncontrolled rotation.

This fault indicates that the auto-tuning procedure, which measures motor parameters, was unsuccessful. This can happen if motor parameters are incorrectly configured prior to auto-tuning, or if the procedure is interrupted.

This fault indicates an underload condition where the measured motor current has dropped below the level set by parameter F611 ([Underload level]), potentially due to loss of load or mechanical failure.

This fault indicates that the input voltage to the Altivar 212 drive is too low, potentially causing instability or improper operation. This can lead to a drive trip to prevent damage.

This fault indicates insufficient line supply voltage, a transient voltage dip, or a damaged precharge resistor. The drive trips if the line voltage drops below specific thresholds: 160V for ATV312 M2/M3 models, 300V for N4 models, and 430V for S6 models.