Lenze SM29_05 Service

The heatsink temperature has exceeded 85°C (displayed as OH). This condition is monitored by the MCTRL function and indicates that the drive's cooling system may be insufficient, blocked, or the ambient temperature is too high, leading to potential drive damage.

An internal system fault (displayed as CCr) has occurred within the drive. This indicates a potential malfunction in the internal hardware or software of the device and requires further investigation of the drive's internal status.

An internal fault (displayed as H07) has been detected within the power section of the drive. This indicates a critical hardware failure in the power electronics, such as IGBT or rectifier issues, and often requires professional service.

The DC bus voltage (C0173) has exceeded the permissible limit (displayed as OU). This condition is monitored by the MCTRL function and can be caused by regeneration from the motor, an unstable input supply voltage, or incorrect braking resistor configuration.

The DC bus voltage (C0173) has fallen below the permissible limit (displayed as LU). This condition is monitored by the MCTRL function and can be caused by a sag in the input supply voltage, a missing phase, or a problem with the drive's internal power supply unit.

This fault indicates a system failure caused by strong interference injection on the control cables or ground/earth loops in the wiring. Such interference can lead to unpredictable system behavior and instability.

Faulty transfer of control commands has occurred via the Automation Interface (AIF). This is often due to a loose communication module or keypad XT connection, disrupting essential command signals.

The CAN1_IN object is receiving faulty data or communication is interrupted. This is likely caused by wiring issues at X4, a faulty sender, or an insufficient monitoring time for the communication, leading to unreliable data exchange.

The CAN2_IN object is receiving faulty data or communication is interrupted. This is likely caused by wiring issues at X4, a faulty sender, or an insufficient monitoring time for the communication, leading to unreliable data exchange.

The CAN3_IN object is receiving faulty data or communication is interrupted. This is likely caused by wiring issues at X4, a faulty sender, or an insufficient monitoring time for the communication, leading to unreliable data exchange.

The controller has received too many faulty telegrams via the system bus (CAN) and has disconnected from the bus. This indicates a severe communication issue on the CAN network, preventing data exchange.

An external monitoring function has been triggered via DCTRL, meaning a digital signal assigned to the TRIP-SET function has been activated. This indicates an external safety or control system has detected an issue.

This status indicates an initialization error or a communication error between the keypad and the controller. It signifies that the drive controller is unable to properly start up or establish communication with its human-machine interface.

An internal memory fault has occurred within the device. This indicates a critical internal hardware or software issue.

During the initialisation of the controller, an incorrect power stage was detected. This signifies a critical internal hardware issue related to the power conversion circuitry.

The sensor for detecting the heatsink temperature is indicating undefined values. This prevents accurate monitoring of the heatsink's thermal status, potentially leading to overheating if not addressed.

The sensor for detecting the internal temperature of the controller is indicating undefined values. This prevents accurate monitoring of the internal component temperature, risking damage from overheating.

A current-carrying motor phase has failed, or the current limit value is set too low. This monitoring function is only applicable for asynchronous motors and requires the MLP1 function block to be entered in C0465. Loss of a motor phase can cause motor damage.

The DC bus voltage is lower than the value specified in C0173. This indicates insufficient input power to the drive, potentially due to issues with the mains voltage or supply cabling, preventing proper drive operation.

The motor speed is out of the tolerance margin defined by C0576. This typically occurs due to an excessively high active load (e.g., in hoists) or mechanical blockades, preventing the drive from achieving the commanded speed.

The maximum system speed, set by C0596, has been exceeded. This can be caused by an active load that is too high, the drive not being speed-controlled, or an excessively limited torque, leading to overspeed conditions.

A short circuit is detected in the motor cable, or excessive capacitive charging current is flowing. This can cause immediate damage to the drive's output stage or the motor itself.

One of the motor phases has earth contact, indicating an insulation fault in the motor cable or motor windings. This presents a safety risk and can cause drive damage.

This fault indicates an overload condition based on current and time, caused by frequent and prolonged acceleration with overcurrent, or continuous overload with Imotor > 1.05 x Irx. This can lead to motor and drive overheating.

This fault signifies a cumulative thermal overload condition based on the square of current and time, resulting from frequent and prolonged acceleration processes with motor overcurrent or permanent motor overload with Imotor > Irmotor. This can severely stress the motor and drive components.

This is an advance warning for a potential I²xt overload, indicating frequent and prolonged acceleration processes with motor overcurrent or permanent motor overload with Imotor > Irmotor. It suggests that conditions are approaching a trip threshold.

The heatsink temperature has exceeded +90°C. This is typically caused by ambient temperatures above +40°C or +50°C, a dirty heatsink impeding heat dissipation, or an incorrect mounting position restricting airflow.

The motor temperature, detected via resolver or incremental encoder, has exceeded +150°C. This signifies severe thermal overload due to impermissible continuous current or frequent/prolonged acceleration processes. A missing PTC/temperature contact can also prevent proper monitoring.

The heatsink temperature has exceeded the threshold set in C0122. Causes include ambient temperatures above +40°C or +50°C, a dirty heatsink, an incorrect mounting position, or the value specified under C0122 being set too low.

The motor temperature, detected via resolver or incremental encoder, has exceeded the threshold set in C0121. This indicates thermal overload from impermissible continuous current, frequent/prolonged acceleration processes, or the C0121 value being set too low.

The motor temperature, measured via inputs T1 and T2, is too high. This signifies thermal overload due to impermissible continuous current or frequent/prolonged acceleration processes. It can also occur if terminals T1 and T2 are not connected to a PTC/temperature contact.

The DC bus voltage is higher than the value set in C0173, primarily caused by excessively high braking energy during deceleration. Sustained overvoltage can damage the drive's DC bus components.

The angle difference between the set and actual position is larger than the following error limit set under C0255. This indicates that the drive cannot accurately follow the commanded position or speed, possibly due to insufficient torque or excessive load.

The phase controller limit has been reached, meaning the drive cannot follow the digital frequency due to hitting its Imax limit. This indicates the drive is being commanded beyond its current capability, potentially causing instability.

The sync telegram from the master (PLC) is out of sync cycle or not received, indicating a communication issue. This can also occur if the controller is enabled too fast, before the sync telegrams are stable.

The function block DFIN is limiting the input values at X9, which causes a loss of increments. This suggests an issue with the digital frequency connection or a mismatch in master/slave settings, affecting precise control.

An error has been detected in the program flow of the device. This signifies an internal software issue that prevents normal operation.

An error was detected during the parameter set transfer between two devices, or the parameter set does not match the controller (e.g., if data was transferred from a higher-power controller to a lower-power controller). This can lead to incorrect drive configuration.

The rotor position adjustment process was cancelled, often because an Sd7 or Sd8 error occurred during adjustment with an absolute value encoder. Without a successfully executed rotor position adjustment, the drive may carry out uncontrolled movements.

This error occurs when the operating system software has been updated and requires the storage of the Lenze setting to ensure compatibility. This typically happens after a firmware upgrade.

A fault occurred when loading parameter set 1, which could be due to an interruption during transmission via the keypad or incompatibility between the stored parameters and the loaded software version. The Lenze setting is loaded automatically.

The resolver cable connected to X7 is interrupted, or the resolver itself is faulty. This prevents accurate motor position feedback, which is crucial for precise motor control.

The encoder cable connected to X9 is interrupted, or pin X9/8 is not connected (input signal 'Lamp Control' at X9/8 is LOW). This leads to a loss of encoder feedback, which can cause uncontrolled drive movements if not addressed.

The current signal at analog input X6/1 and X6/2 is less than 2mA, indicating an issue with the encoder or its wiring. This monitoring is only possible if C0034 = 1, and its failure means loss of accurate position feedback.

The encoder for detecting the motor temperature at X7 or X8 is indicating undefined values. This prevents proper motor thermal protection and could lead to motor damage due to overheating.

The absolute value encoder at X8 has an initialisation error, is defective, or is not sending data. This may also occur if the encoder constant (C0420) for C0025=309 is altered. An uninitialised encoder can lead to uncontrolled drive movements.

The SinCos encoder at X8 is sending inconsistent data, indicating damaged tracks, high interference levels on the cable, or an open circuit. It could also be due to an incorrect encoder type or improperly set supply voltage.

The motor temperature has exceeded 150°C (displayed as OH3). This is monitored by the MCTRL function and related to parameter C0583. Continued operation under this condition will lead to rapid degradation and destruction of the motor windings and insulation.

The heatsink temperature has exceeded the threshold defined in parameter C0122 (displayed as OH4). This condition is monitored by the MCTRL function and related to parameter C0582, indicating a configurable heatsink thermal protection limit has been reached.

The motor temperature has exceeded the threshold defined in parameter C0121 (displayed as OH7). This condition is monitored by the MCTRL function and related to parameter C0584, indicating a configurable motor thermal protection limit has been reached. Operation above this threshold risks motor damage.

The motor temperature, as measured across inputs T1 and T2 from a PTC resistor or thermal contact, is too high (display OH8 on keypad). This condition is monitored by the MCTRL function and its response can be set via parameter C0585. Operating with this fault not eliminated can destroy the drive if C0585 is set to 'Warning' (2) or 'Off' (3). An 'open' cable on T1, T2 can act as an antenna and cause faults. Only one PTC resistor should be connected; multiple in series or parallel will result in incorrect temperature measurement.

A communication error (displayed as CE0) has occurred on the automation interface (AIF). The monitoring is related to parameter C0126. This indicates a problem with data exchange on the primary communication channel, such as PROFIBUS or INTERBUS.

A communication error (displayed as CE1) has occurred at the process data input object CAN1_IN. The monitoring time for this error can be set with parameter C0357/1. This indicates an issue with receiving process data on CAN channel 1, potentially due to incorrect wiring, termination, or a bus fault.

A communication error (displayed as CE2) has occurred at the process data input object CAN2_IN. The monitoring time for this error can be set with parameter C0357/2. This indicates an issue with receiving process data on CAN channel 2, potentially due to incorrect wiring, termination, or a bus fault.

A communication error (displayed as CE3) has occurred at the process data input object CAN3_IN. The monitoring time for this error can be set with parameter C0357/3. This indicates an issue with receiving process data on CAN channel 3, potentially due to incorrect wiring, termination, or a bus fault.

The system bus (CAN) has entered a BUS-OFF state (displayed as CE4), indicating that too many faulty telegrams have been transmitted. This often means the CAN node has ceased transmitting due to excessive errors. The monitoring relates to parameter C0595 and typically points to severe bus communication problems.

A thermal sensor error has occurred at the motor (displayed as Sd6), specifically at terminals X7 or X8. This indicates a problem with the motor's temperature sensing circuit, such as a broken sensor or incorrect wiring. This condition is monitored by the MCTRL function and related to parameter C0594.

This fault (displayed as EEr) indicates that an external monitoring function, activated via DCTRL, has detected an issue. The monitoring response can be parameterized via C0581, suggesting a configurable external safety or process monitoring system has triggered a fault.

A thermal sensor error has occurred at the heatsink (displayed as H10). This condition is monitored by the FWM function and related to parameter C0588. This indicates a problem with the drive's heatsink temperature sensing circuit, potentially a damaged sensor or wiring issue.

An incorrect transmission of the synchronization telegram (displayed as P16) has occurred on the CAN system bus. This internal fault, related to C1290, indicates an issue with the timing or integrity of CAN communication synchronization, which can lead to unstable multi-axis operation.