Schneider Electric Altivar 340

This fault indicates an error within the drive controller's internal EEPROM memory, which stores configuration parameters and operational data. This can lead to incorrect settings being loaded or data corruption, preventing proper drive operation. A corrupted EEPROM can cause unpredictable behavior or prevent the drive from starting.

This fault signifies a general internal malfunction within the drive controller, possibly related to internal circuitry or connections. Electromagnetic interference (EMI) can sometimes induce such faults, or it could be a hardware failure. Continued operation with an internal fault is not possible and requires immediate attention to prevent further damage or unexpected behavior.

This fault occurs when the motor generates excessive regenerative energy back into the drive controller's DC bus during rapid deceleration or when driving an overhauling load (e.g., lowering a weight). This rapid increase in DC bus voltage can exceed safe limits and damage the drive's internal components if not dissipated properly.

This fault indicates that the drive controller has detected excessive current flowing to the motor. This can be caused by the motor accelerating too quickly, the drive or motor being undersized for the mechanical load, or a physical blockage preventing the motor from turning freely. Leaving this unresolved can damage the motor, drive controller, or connected machinery due to overheating or mechanical stress.

This fault indicates that the drive controller's internal temperature has exceeded its safe operating limits, often due to sustained high motor current or insufficient cooling. This protects the drive's power components from thermal damage. The fault is triggered when the drive controller's thermal state estimate reaches 118%, necessitating a cooldown period.

This fault indicates that the connected motor has experienced a prolonged overload condition, causing its estimated thermal state to exceed safe limits (118% as per page 75). This protects the motor windings from overheating and damage. It could be due to incorrect thermal protection settings or an undersized motor for the application, leading to premature motor failure.

This fault indicates a loss of one or more phases at the output of the drive controller, meaning the motor is not receiving power on all its windings. This can be caused by loose motor connections, a damaged motor cable, or if the drive is significantly oversized for a small motor (making phase loss harder to detect). Operating with a missing motor phase will cause excessive heating and damage to the motor windings and potentially the drive.

This fault indicates that the DC bus voltage within the drive controller has exceeded a safe threshold during steady-state operation or acceleration. The primary cause is typically an input line voltage that is consistently higher than the drive controller's nominal rating, which can stress and damage internal power components like the DC bus capacitors and IGBTs.

This fault indicates a loss or significant imbalance of one or more input phases to the drive controller. Common causes include blown line fuses, loose connections, or an issue with the utility supply. Using a 3-phase drive on a single-phase supply without proper configuration can also trigger this. Operating with missing phases can lead to motor and drive damage due to unbalanced currents.

This fault indicates a short-circuit or ground fault has occurred at the output of the drive controller, either in the motor cables or within the motor itself. This is a critical fault that can severely damage the drive controller's output stage (IGBTs) if power is maintained. Immediate action is required to prevent component failure.

This fault occurs when communication is lost between the drive controller and its connected serial devices, such as a remote keypad display or a MODBUS master controller. This prevents external control, monitoring, or parameter adjustment of the drive, interrupting automated processes. The cause could be physical disconnection, incorrect settings, or device malfunction.

This fault occurs during the auto-tuning process, indicating that the drive controller is unable to successfully tune itself to the connected motor. This is typically due to using a specialized motor or one whose power rating does not match the 'n' (nominal) or 'nld' (no-load) settings of the UFb parameter, preventing optimal motor control. Incorrect tuning can lead to inefficient operation or other motor control issues.

This fault signifies that the input voltage to the drive controller has dropped below its minimum operating threshold or experienced a significant transient dip. A damaged pre-charge resistor or internal power supply issue could also prevent the DC bus from charging correctly. Operating with undervoltage can cause erratic drive behavior, prevent it from starting, or damage internal components over time.