Lenze 8200 Vector Drive

An external disturbance has been detected, activating a digital signal assigned to the TRIP-SET function (DCTRL1-TRIP-SET). This typically results from a LOW level at the signal source for this function, causing the controller to inhibit. Ignoring this can lead to system shutdown and operational delays.

A communication abort has occurred between the keypad and the standard device (e.g., fault codes ErP0 through ErP19), indicating a failure in data exchange. The specific cause can vary. This prevents proper interaction with the device via the keypad and requires expert assistance for diagnosis.

The cooling fan, particularly in 8200 motec controllers (3...7.5 kW), has either failed or is disconnected. This condition can lead to the controller overheating, potentially causing thermal shutdown and reducing the lifespan of internal components if not addressed promptly.

An internal hardware or software fault has been detected within the controller, indicating a critical system malfunction. This issue cannot be resolved through standard troubleshooting and requires specialized attention to prevent potential damage or system instability.

One or more motor phases have failed, the motor current is unusually low, the motor is too small for the drive's rated power, or the DC injection brake is active during identification. This indicates a potential issue with the motor connection, motor sizing, or incorrect operating conditions. Operating with missing or low phases can cause motor overheating, damage to windings, and erratic operation.

The DC bus voltage has dropped below acceptable limits, typically due to low incoming mains voltage or an issue with the power supply module. Incorrect controller wiring to the mains (e.g., 400V controller on 240V mains) can also trigger this. Persistent undervoltage can cause intermittent operation or prevent the drive from starting.

A short circuit has been detected on the drive's output, possibly in the motor, motor cables, or brake resistor circuit. Excessive capacitive charging current from long or high-capacitance motor cables can also falsely trigger this fault. An unresolved short circuit poses a severe risk of damage to the drive's output stage.

An earth fault has been detected, indicating a motor phase has made contact with earth or the motor cable insulation is compromised. Similar to OC1, high capacitive charging current from motor cables can also trigger this. Operating with an earth fault is a safety hazard and can cause severe damage to the motor and drive.

The controller has experienced an overload condition during acceleration, possibly due to an acceleration time (C0012) that is too short, an improperly dimensioned drive, or issues with the motor/cabling like a defective motor cable or interturn fault. Persistent overloading can lead to drive component degradation and premature failure.

The controller has overloaded during deceleration, often because the deceleration time (C0013) is set too short or the external brake resistor is inadequately dimensioned. Excessive regenerative energy not properly dissipated can damage the drive's DC bus components and lead to overvoltage faults.

The controller is experiencing frequent or prolonged overload periods during steady-state operation, indicating the drive is undersized for the continuous load. Continuous operation beyond the drive's rated capacity will lead to overheating and significantly reduce its lifespan, potentially causing premature failure.

The motor has exceeded its thermal overload limit (I²t model), caused by excessive continuous current or frequent/prolonged acceleration cycles. This indicates the motor is either undersized for the application, or the drive parameters are not correctly configured. Continued operation under overload conditions will severely damage the motor windings.

The controller's heatsink temperature has exceeded its safe operating limit (either >85°C or >80°C), typically due to high ambient temperature, blocked airflow, or excessive drive load. A dirty heatsink or high currents during acceleration can also contribute. Sustained overtemperature will lead to derating, thermal shutdown, and reduced component lifespan.

The motor's PTC thermistor has detected an overtemperature condition, triggering a TRIP fault. This is usually caused by the motor operating under impermissible high currents or frequent/long acceleration processes, or simply if the PTC sensor is not connected while monitoring is active (C0119 = 1 or 4). Continued motor operation in an overtemperature state will lead to severe winding damage and premature motor failure.

The controller's internal temperature has exceeded its safe operating limit. This indicates that the controller is experiencing excessive load, has insufficient cooling, or its internal fan is failing. Sustained internal overtemperature will lead to derating, thermal shutdown, and reduced lifespan of internal components.

The motor's PTC thermistor has detected an overtemperature condition, triggering a WARNING (not a TRIP). This typically occurs when the motor operates under impermissible high currents or frequent/long acceleration processes, or if the PTC sensor is not connected while monitoring is active (C0119 = 2 or 5). While a warning, continued operation can still lead to motor damage if the condition escalates.

The DC bus voltage has exceeded its safe operating limit, primarily caused by an excessively high incoming mains voltage. This fault can also be triggered by regenerative energy from the motor if deceleration times are too short or the brake resistor is undersized/missing. Overvoltage poses a significant risk of damage to the drive's internal components, especially the DC bus capacitors and power semiconductors.

An overvoltage condition has occurred, specifically related to braking operations or an earth leakage at the motor end. During braking, insufficient deceleration time or an undersized/defective brake resistor can cause this. An earth leakage in the motor or cable also contributes. This fault indicates high stress on the drive's DC bus, potentially leading to component failure.

All parameter sets within the controller have become defective, often due to an interrupted or faulty parameter transfer from the keypad. This critical issue prevents the drive from operating correctly as its configuration is lost or corrupted. Operating with corrupted parameters can lead to unpredictable behavior and potential damage.

Parameter set 1 within the controller has become defective, likely due to an interrupted or faulty transfer from the keypad. This indicates a corruption in a specific configuration set, which can prevent proper drive operation when that set is active. Operating with corrupted parameters can lead to unpredictable behavior.

Parameter set 2 within the controller has become defective, likely due to an interrupted or faulty transfer from the keypad. This indicates a corruption in a specific configuration set, which can prevent proper drive operation when that set is active. Operating with corrupted parameters can lead to unpredictable behavior.

Parameter set 3 within the controller has become defective, likely due to an interrupted or faulty transfer from the keypad. This indicates a corruption in a specific configuration set, which can prevent proper drive operation when that set is active. Operating with corrupted parameters can lead to unpredictable behavior.

Parameter set 4 within the controller has become defective, likely due to an interrupted or faulty transfer from the keypad. This indicates a corruption in a specific configuration set, which can prevent proper drive operation when that set is active. Operating with corrupted parameters can lead to unpredictable behavior.

An internal fault related to the EEPROM (Electrically Erasable Programmable Read-Only Memory) has been detected, indicating a defect in the controller's non-volatile memory. This is a critical hardware failure that can lead to data loss and system malfunction. This fault requires manufacturer intervention.

A time error occurred during parameter set transfer, meaning the data flow from the keypad or PC was interrupted (e.g., keypad removed). This incomplete transfer can leave parameters in an undefined state, preventing correct operation. Operating with partially transferred parameters can cause erratic and dangerous behavior.

A general system fault has occurred, likely due to strong electromagnetic interference on control cables or the presence of earth loops in the wiring. Such interference can lead to unreliable control signals, erratic operation, and potential system instability.

A communication error has occurred on the AIF (Application Interface) interface, indicating faulty transmission of control commands. This often points to a loose or improperly seated communication module. Unreliable communication can lead to loss of control and unexpected drive behavior.

A communication error has occurred on CAN-IN1 during synchronous control, indicating that faulty data is being received or the communication itself is interrupted. This can be caused by loose bus module connections or issues with the transmitting device. Loss of synchronous communication can lead to unsynchronized operation or system shutdown.

A communication error has occurred on CAN-IN2, meaning faulty data is being received or the communication is interrupted. Potential causes include loose bus module connections or issues with the transmitting device. This can lead to loss of control over devices connected to CAN-IN2.

A communication error has occurred on CAN-IN1 during event or time-controlled operation, indicating faulty data or interrupted communication. This can stem from loose bus module connections or issues with the transmitting device. Loss of critical event or time-based communication can disrupt synchronized operations.

The controller has entered a 'Bus-Off' state, meaning it has detected and received too many faulty telegrams on the system bus and has consequently disconnected itself. This indicates severe bus communication issues, such as incorrect termination, poor shielding, or excessive bus load. Being 'Bus-Off' means the controller cannot communicate, halting operations.

A CAN communication timeout has occurred. This could be due to a slave device not responding during remote parameterization (C0370), incorrect parameter set changeover configuration with application I/O, or an internal error with a module on the FIF. A communication timeout means commands or data are not being exchanged, leading to operational halts or incorrect behavior.

The CAN function module on the FIF has reported a 'Warning' or 'Bus-Off' status, indicating underlying communication issues. This often points to problems with bus termination, cable shielding, PE connection, or an overloaded bus. While 'Warning' might allow limited operation, 'Bus-Off' will completely halt communication.

A communication error has occurred during remote parameterization via the system bus (C0370), typically because a node is unresponsive or unavailable. This can also be caused by incorrect parameter set changeover configuration with application I/O. Such errors prevent remote configuration and control of the drive.

The motor parameter identification process has failed, most likely because the motor is not properly connected to the drive. Incorrect parameter identification can lead to suboptimal motor control, instability, and potential damage to both the motor and the drive if not resolved.

This fault indicates that the controller has attempted and failed to perform more than eight automatic TRIP resets within a 10-minute period. It signifies a persistent underlying fault condition that repeatedly triggers and attempts to reset, but the root cause is not being resolved. Ignoring this means an underlying problem is not being addressed, leading to repeated shutdowns and potential drive wear.

A wire breakage has been detected on analog input 1, specifically when the current on the input is less than 4 mA for a 4-20 mA setpoint range. This indicates an open circuit in the analog signal path. Loss of this input means the drive will not receive its commanded setpoint, potentially leading to incorrect speed or torque.

A wire breakage has been detected on analog input 2. If this input is configured for a 4-20 mA range, it means the current is below 4 mA, indicating an open circuit in the analog signal path. Loss of this input can lead to incorrect operation or functionality if this input is critical for control.