Lenze 9300 Series

An overcurrent (Ia > 2.25 x IN) has occurred in the motor cable, detected by hardware monitoring. This can be caused by a short circuit in the motor cable, excessive capacitive charging current of the motor cable, or acceleration/deceleration times that are too short for the load. It can also indicate a missing mains phase or an encoder wiring issue.

One of the motor phases has made contact with earth, indicating an insulation fault in the motor cable. This condition poses a risk of electrical shock and further equipment damage.

This fault indicates an overload condition during acceleration due to acceleration or deceleration times (C0012, C0013, C0105) that are too short relative to the connected load. The current controller is likely reaching its limits frequently.

This fault occurs due to frequent and excessively long acceleration processes with overcurrent, or continuous overload where the motor current (Imotor) exceeds 1.05 times the rated current (Irx). A device utilization (C0064) exceeding 100% releases a warning for this condition. The drive dimensioning may be insufficient for the application's duty cycle.

This fault is triggered by frequent and excessively long acceleration processes with motor overcurrent, or permanent motor overload where the motor current (Imotor) exceeds the rated motor current (Irmotor). The drive or motor dimensioning may be inadequate for the application's continuous or peak load requirements.

The heatsink temperature has exceeded +90°C (or >85°C as an earlier warning threshold, C0061). This can be caused by ambient temperatures (Tu) above +40°C or +50°C, a dirty heatsink impeding airflow, or an incorrect mounting position preventing adequate ventilation.

A system failure has occurred, likely due to strong interference injection on control cables or ground/earth loops in the wiring. This indicates an electrical noise or grounding issue affecting the controller's stability.

A checksum error has been detected in parameter set 1. This fault can arise from issues during parameter set loading, interruption during transfer via keypad, or incompatibility between stored parameters and the loaded software version.

A checksum error has been detected in parameter set 2. This fault can arise from issues during parameter set loading, interruption during transfer via keypad, or incompatibility between stored parameters and the loaded software version.

An error has occurred in the program flow of the device. This indicates an internal software issue within the controller's operating system, potentially requiring a software analysis by the manufacturer.

An error has occurred in the parameter set, possibly due to an operating system software update. The Lenze default settings (C0003 = 1) are automatically loaded as a result of this fault.

A checksum error has been detected in parameter set 3, indicating a fault during loading or an interruption during transfer via the keypad. This can also occur if saved parameters are incompatible with the loaded software version.

A checksum error has been detected in parameter set 4, indicating a fault during loading or an interruption during transfer via the keypad. This can also occur if saved parameters are incompatible with the loaded software version.

An error was detected during parameter set transfer between two devices, or the parameter set does not match the controller (e.g., higher-power controller data transferred to lower-power). This prevents proper device initialization.

An internal fault related to the controller's memory has been detected. This indicates a critical hardware or firmware issue within the drive itself.

During the controller's initialization phase, an incorrect power stage was detected. This implies a critical internal hardware mismatch or failure within the power electronics.

A short circuit has occurred in the motor cable, or there is excessive capacitive charging current if the motor cable is too long or has high capacitance. This can lead to drive tripping and potential damage.

One of the motor phases has made contact with earth (ground), indicating an earth fault. This suggests an insulation breakdown in the motor cable or the motor windings.

An error occurred during the motor data identification process. This can be caused by a disconnected motor, excessively high stator resistance, or the controller being externally inhibited during the identification sequence.

An error occurred during motor data identification, indicating the connected motor may be too small for the drive. This can also be caused by an externally inhibited controller during the identification process, preventing proper measurement.

The drive is experiencing an I x t overload, characterized by frequent and excessively long acceleration phases with overcurrent, or continuous overload where Imotor > 1.05 x Irx. This indicates that the drive is undersized for the application.

The drive is experiencing an I²xt overload, characterized by frequent and excessively long acceleration processes with motor overcurrent, or permanent motor overload where Imotor > Irmotor. This signals a prolonged motor overload condition.

This is an advance warning for an I²xt overload, indicating frequent and excessively long acceleration processes with motor overcurrent, or permanent motor overload where Imotor > Irmotor. It signals an impending trip condition if conditions do not change.

The motor speed has exceeded the maximum limit defined in parameter C0596. This indicates an overspeed condition potentially due to incorrect parameter settings, external load conditions, or control system malfunction.

A float error, such as division by zero, has occurred in the system task (ID 0) during real number calculations. This indicates an issue within the program code's arithmetic operations, leading to an imprecise or undefined result.

A float error, such as division by zero, has occurred in the cyclic task (PLC_PRG ID 1) during real number calculations. This indicates an issue within the PLC program's arithmetic operations that impacts the cyclic execution.

A float error, such as division by zero, has occurred in task 1 (ID 2) during real number calculations. This indicates an issue within the program code specific to task 1's arithmetic operations.

A float error, such as division by zero, has occurred in task 8 (ID 9) during real number calculations. This indicates an issue within the program code specific to task 8's arithmetic operations.

The cyclic task (PLC_PRG ID 1) has exceeded its allocated monitoring time. This indicates that the task processing duration is longer than the set monitoring time, potentially due to complex or lengthy program parts.

The controller lacks the necessary technology units to execute a loaded program containing technology functions. This indicates a mismatch between the program's requirements and the controller's hardware capabilities.

No PLC program has been loaded into the controller's memory. The controller is unable to execute any programmed logic or control functions without a loaded program.

The PLC program attempted to call a library function that is not supported by the current controller hardware or firmware. This means a required hardware component might be missing, or the function is incompatible with the controller variant.

Motion profiles (CAM data) are not available in the controller's memory, despite functions from the `LenzeCamControl.lib` library being called. This prevents motion control functions from operating correctly, potentially due to incorrect project setup or a reset.

A current-carrying motor phase has failed, or the current limit value is set too low. This can lead to irregular motor operation, reduced performance, or motor damage.

The heatsink temperature has exceeded +90°C. This is often caused by an ambient temperature greater than +40°C or +50°C, a dirty heatsink, or an incorrect mounting position, leading to potential overheating.

The controller has entered a BUS-OFF state on the system bus (CAN) due to receiving too many faulty telegrams, leading to disconnection from the bus. This indicates a severe communication breakdown.

A time-out has occurred on the system bus (CAN) during remote parameterization (C0370, C0371), indicating a communication error of the gateway function. The slave device did not respond within the communication monitoring time.

The internal 15V voltage supply is experiencing an undervoltage condition. This affects the internal control electronics and can prevent proper device operation.

A system failure has occurred due to strong interference injection on the control cables. This can be caused by inadequate shielding or ground/earth loops in the wiring, leading to unstable operation.

A checksum error was detected in parameter set 1 during loading or transfer via the keypad. This indicates a fault in the parameter data or incompatibility with the loaded software version. The Lenze default settings are loaded automatically.

A checksum error was detected in parameter set 2 during loading or transfer via the keypad. This indicates a fault in the parameter data or incompatibility with the loaded software version. The Lenze default settings are loaded automatically.

An error has occurred in the program flow, indicating an internal software issue within the device. This may lead to unexpected behavior or system stoppage.

An error exists in the parameter set, often triggered after an operating system software update. The device automatically loads the Lenze default settings.

A checksum error was detected in parameter set 3 during loading or transfer via the keypad. This indicates a fault in the parameter data or incompatibility with the loaded software version. The Lenze default settings are loaded automatically.

A checksum error was detected in parameter set 4 during loading or transfer via the keypad. This indicates a fault in the parameter data or incompatibility with the loaded software version. The Lenze default settings are loaded automatically.

A fault occurred during parameter initialization, likely during parameter set transfer between two devices, or because the parameter set does not match the controller (e.g., from a higher-power controller to a lower-power one).

The device has reached the maximum allowed number of user codes. This prevents the creation or storage of additional user-defined settings.

A resolver error has occurred at terminal X7, typically indicating an interrupted resolver cable. This prevents accurate position feedback.

An encoder error has occurred at terminal X9, typically due to an interrupted encoder cable or pin X9/8 not being connected. This can lead to incorrect or no position feedback.

An encoder error has occurred at X6/1 and X6/2 (when C0034 = 1), indicated by a current signal less than 2mA at these terminals. This suggests an open circuit or a faulty current signal encoder.

The encoder for detecting motor temperature at X7 or X8 is indicating undefined values. This suggests a problem with the temperature sensor, its cable, or connection.

An initialization error occurred at the absolute value encoder at X8, or the encoder electronics are defective. This can result from a loose cable, an open circuit, an incorrect encoder type, or failure during rotor position adjustment.

The SinCos encoder at X8 is sending inconsistent data, indicating damaged internal tracks or high interference on the encoder cable. It could also mean the encoder is not transmitting data due to an open circuit, an incorrect encoder type, or a defective sensor.

The rotor position adjustment was canceled, possibly due to an Sd7 or Sd8 error occurring during the adjustment with an absolute value encoder. This error is saved with mains failure protection.

External monitoring has been triggered via the DCTRL input. A digital signal assigned to the TRIP-SET function has been activated.

An overvoltage condition exists in the DC bus, where the DC bus voltage is higher than the value set in parameter C0173. This is typically caused by excessive braking energy being fed back to the bus.

An undervoltage condition exists in the DC bus, where the DC bus voltage is lower than the value specified in parameter C0173. This typically indicates insufficient input power to the drive.

An internal fault related to the device's memory has occurred. This typically indicates a hardware issue that requires specialized attention.

An internal fault related to the power stage has occurred. During the initialisation of the controller, an incorrect power stage was detected, indicating a serious internal hardware issue.

The sensor for detecting the heatsink temperature is indicating undefined values. This suggests a fault with the sensor or its connection, leading to unreliable temperature monitoring.

The temperature sensor inside the controller is indicating undefined values. This suggests a fault with the sensor or its connection, leading to unreliable internal temperature monitoring.

The negative limit switch has been reached, preventing further movement of the drive in the negative direction. This is a safety mechanism to prevent overtravel.

The positive limit switch has been reached, preventing further movement of the drive in the positive direction. This is a safety mechanism to prevent overtravel.

The angle difference between the set position and the actual position is larger than the following error limit set under parameter C0255. This can also indicate the drive cannot follow the digital frequency due to reaching its Imax limit, suggesting insufficient drive dimensioning.

The negative position limit (C1224) was not reached, potentially due to incorrect position targets or issues with the 'set function position value'. This can prevent the drive from reaching its intended negative travel extreme.

The positive position limit (C1223) was exceeded, potentially due to incorrect position targets or issues with the 'set function position value'. This can cause the drive to overtravel its intended positive extreme.

The reference point for the drive is not known. In absolute positioning mode, homing was not performed before the first positioning command, which is essential for establishing a known position.

An absolute parameter set (C1311) was performed or is active during relative positioning (position mode C1210). This mismatch in positioning modes prevents correct operation.

The actual reference dimension offset (C1226) is outside the defined position limits. This indicates an error with the program function 'set position value' or incorrect limit settings.

The positioning program contains impermissible programming. Specifically, a parameter set with a final speed must be followed by a parameter set with positioning, and it is not permissible to wait for input at that stage.

The traversing range of the absolute encoder has been exceeded. This means the physical travel of the drive has gone beyond the measurement capabilities of the installed encoder.

The DC bus voltage has exceeded the switch-off threshold OU (e.g., 770V for <400V mains with C0173=0) as specified by parameter C0173, indicating excessive braking energy. The pulse inhibit is set, and a delay time (C0912) starts until the voltage falls below the switch-on threshold OU (e.g., 755V for <400V mains).

An error occurred when downloading data into the FLASH memory. This can be caused by a time-out, transmission error, or a mains failure during the data transfer process, resulting in incomplete or corrupt data.

The controller, configured as a CAN slave, did not receive a 'Node Guarding' telegram from the CAN master within the configured 'Node Life Time'. This indicates a loss of communication supervision on the CAN bus.

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.

The drive system includes protective measures against earth faults, though to a limited extent, as per EN 61800-5-1. This fault indicates current leakage to ground, posing risks of electrical shock and equipment damage. Fault acknowledgement is necessary to clear this condition and resume operation.

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.

Monitoring of motor phases (LP1) does not respond to an interrupted motor phase, even if C0597 = 0 or 2, because the MLP1 function block is not entered into the processing table. This means an interrupted motor phase will not be detected.

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 drive system provides protection against motor overtemperature, specifically monitored using an I²xt-monitoring function. This feature safeguards the motor from thermal damage caused by prolonged overload or inadequate cooling, triggering a fault when internal temperature limits are exceeded.

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.

An overcurrent (OC1) TRIP occurs if, during DC-injection braking (GSB) at high motor speeds, the residual voltage from magnetism and high speed generates an excessive motor current. This happens because the pulse inhibit (DCTRL-IMP) set during braking is too short.

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.

An overcurrent condition (OC5) can be activated if motor phases are reversed, causing the motor's rotating field to mismatch the feedback system's. This leads to the motor drawing high current, potentially up to Imax (C0022), especially with V/f or vector control.

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 drive has detected a heatsink overtemperature condition. This is a warning that indicates the heatsink temperature has exceeded its normal operating range, but the drive continues to operate in a controlled manner.

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 drive has triggered the PTC monitoring function. This indicates that the Positive Temperature Coefficient (PTC) thermistor, likely in the motor, has exceeded its threshold temperature, signifying an overtemperature condition. The drive continues to operate in a controlled manner.

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.

An overvoltage (OU) TRIP occurs if, during DC-injection braking (GSB) at high motor speeds, the residual voltage from magnetism and high speed generates an excessive motor current. This can lead to overvoltage due to the drive's attempt to reduce magnetization when the pulse inhibit (DCTRL-IMP) is too short.

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 drive system includes protective measures against short circuits, though to a limited extent, as per EN 61800-5-1. This fault indicates an abnormal current path, potentially causing excessive current flow and damage to internal components or connected wiring. Fault acknowledgement is necessary to clear this condition and resume 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.

This is an advance warning indicating frequent and excessively long acceleration processes with motor overcurrent, or permanent motor overload where the motor current (Imotor) exceeds the rated motor current (Irmotor). This condition suggests that the drive or motor dimensioning may be inadequate, and continuous operation without addressing it could lead to an OC6 trip. This warning is managed by parameter C0606.

One of the current-carrying motor phases has failed. This monitoring function is primarily for asynchronous motors and requires the MLP1 function block to be entered in C0465. Possible causes include a faulty motor, a damaged motor cable, or a current limit value (C0599) set too low. The monitoring can be switched off via C0597.

The motor temperature has exceeded the +150°C threshold, detected via resolver or incremental value encoder (e.g., KTY sensor at X8/5, X8/8). This indicates the motor is thermally overloaded due to impermissible continuous current or frequent/long acceleration processes. This monitoring can be switched off via C0583.

The heatsink temperature has exceeded the specific threshold value set in parameter C0122. This is an advance warning for heatsink overheating, which can be caused by high ambient temperatures (Tu > +40°C or +50°C), a dirty heatsink, or an incorrect mounting position. This monitoring can be switched off via C0582.

The motor temperature has exceeded the specific threshold value set in parameter C0121, detected via resolver or incremental value encoder. This indicates the motor is thermally overloaded due to impermissible continuous current or frequent/long acceleration processes. This is an advance warning for motor overheating. This monitoring can be switched off via C0584.

The motor temperature is too high, detected by a PTC or temperature contact connected to terminals T1 and T2. This indicates motor thermal overload due to impermissible continuous current or frequent/long acceleration processes. The fault can also occur if terminals T1 and T2 are not correctly connected to a temperature sensor. This monitoring can be switched off via C0585.

A communication error has occurred on the automation interface (AIF). This indicates a problem with the physical communication link, its configuration, or the communication master. This error is managed by parameter C0126.

A communication error has occurred with the process data input object CAN1_IN. This can be due to issues with the CAN bus, wiring, or incorrect data configuration. The monitoring time for this communication channel can be set with parameter C0357/1.

A communication error has occurred with the process data input object CAN2_IN. This can be due to issues with the CAN bus, wiring, or incorrect data configuration. The monitoring time for this communication channel can be set with parameter C0357/2.

A communication error has occurred with the process data input object CAN3_IN. This can be due to issues with the CAN bus, wiring, or incorrect data configuration. The monitoring time for this communication channel can be set with parameter C0357/3.

The system bus (CAN) has entered a BUS-OFF state due to an excessive number of faulty telegrams. This indicates a severe and persistent communication problem on the CAN network, which is configured via parameter C0595.

The input signal 'Lamp Control' at terminal X9/8 is LOW, indicating an interruption of the digital frequency coupling. If the response (C0587) is set to 'Warning' (2), continued operation without addressing this fault can potentially damage the drive.

The input current at analog input X6/1 or X6/2 has fallen below 2 mA. This monitoring function is only active if parameter C0034 is set to 1, indicating a low current condition on the analog input.

An error has been detected with the thermal sensor connected to the motor inputs X7 or X8. This indicates a malfunction of the sensor itself or an issue with its wiring, preventing accurate motor temperature monitoring. This monitoring is controlled by parameter C0594.

An external monitoring function has triggered this fault, which is activated via DCTRL (Drive Control) and configured through parameter C0581. The 'x' in the code indicates the response type: 0 for TRIP, 1 for message, 2 for warning.

An error has been detected with the thermal sensor responsible for monitoring the heatsink temperature. This indicates a fault with the sensor itself or its wiring, compromising the heatsink temperature monitoring. This monitoring is controlled by parameter C0588.

The internal temperature sensor within the controller is reporting undefined values. This compromises the ability of the drive to monitor and protect itself against overheating conditions.

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.

The maximum system speed (defined by C0596) has been exceeded. This typically occurs due to an excessively high active load, such as in hoist applications, or if the drive is not speed-controlled and torque limits are too low, allowing overspeed.

An attempt was made to transmit profile data that was detected as faulty. This typically occurs during communication processes involving profile data transfer, indicating data integrity issues.

A checksum error was detected for the transferred profile data, indicating corruption or an incomplete transfer. This means the integrity of the loaded profile data is compromised and may lead to incorrect operation.

The transmit request memory has overflowed, indicating too many CAN objects are queued for transmission. This can lead to delays or loss of communication on the system bus.

Too many receive telegrams are present on the system bus (CAN). This overload can cause issues with processing incoming communication data, potentially leading to lost messages or communication delays.

An error occurred during access to the FLASH memory, indicating the PLC program attempted to access non-available or defective memory. This could signify a hardware issue with the FLASH memory module, preventing proper program execution or data storage.

A checksum error occurred when loading data into the FLASH memory. This indicates data corruption during the transfer process to non-volatile memory, which can lead to incorrect program behavior or lost settings.