Lenze EVF9300 Vector

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.

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.

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 drive has detected a motor phase failure and has triggered a TRIP fault, indicated via the fieldbus interface. This means one or more motor phases are inactive or drawing insufficient current. The fault prevents further operation and requires investigation of motor connections or parameters to avoid motor or drive 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 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 drive has detected a motor phase failure and issued a Warning, indicated via the fieldbus interface. This means one or more motor phases are inactive or drawing insufficient current, but the drive may still be operating or preparing to trip. It requires prompt attention to prevent potential motor or drive damage if the condition persists.

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.

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.

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 external digital input, configured for the TRIP-Set function, has been activated, triggering a fault condition. This indicates an external safety or interlock circuit has been tripped, potentially stopping the drive. If left unaddressed, the drive will remain inhibited, preventing operation.

This indicates a fault within the internal circuitry of the drive controller itself. The specific cause is not detailed in the manual, suggesting a fundamental hardware or firmware issue. Continued operation with an internal fault could lead to further damage to the controller or unexpected system behavior.

One or more motor phases have failed, or the motor current has dropped below an expected minimum. This could be due to a disconnected cable, an open circuit within the motor, or incorrect parameter settings. Operating with a phase failure can cause motor overheating, damage to the drive, and inefficient operation.

The DC-bus voltage in the drive has fallen below the acceptable operating threshold. This is typically caused by insufficient or unstable mains voltage supplied to the drive, or a fault within the supply module. Low DC-bus voltage prevents the drive from delivering adequate power to the motor and can lead to erratic operation or shutdown.

A short-circuit condition or an excessive capacitive charging current in the motor cable has been detected. The former can be due to damaged wiring or motor faults, while the latter can occur with very long or high-capacitance motor cables, causing the drive to trip due to high initial currents. This can lead to nuisance tripping, operational instability, and severe damage to the inverter output stage if a true short circuit is present.

An earth fault has been detected, potentially due to a grounded motor phase or excessive capacitive charging current in the motor cable. This indicates a breakdown in insulation within the motor or its cables, or spurious signals from long, high-capacitance cables. An earth fault poses an electrical safety hazard, can damage the drive's output stage, and cause nuisance trips.

The inverter has experienced an overload during the acceleration phase, potentially due to the acceleration time parameter (C012) being set too short, a defective motor cable, or an interturn fault within the motor. This indicates the drive is attempting to deliver more current than its rating, which can cause overheating and damage to the inverter if prolonged.

The drive controller has experienced an overload condition during deceleration, primarily caused by the deceleration time (C013) being set too short. This leads to regenerative energy being fed back to the DC bus faster than it can be dissipated, causing the bus voltage to rise and triggering an overload. This can damage the inverter if not properly managed.

This fault indicates a cumulative overcurrent condition, often resulting from frequent and prolonged acceleration processes or continuous operation with the motor current exceeding 105% of the drive's rated current. The drive's internal I x t model has determined that the thermal stress on the inverter is excessive. Persistent I x t overload can lead to premature failure of the drive's power components.

The connected motor is thermally overloaded, likely due to impermissible continuous current, frequent, or excessively long acceleration processes. The drive's internal motor protection model has detected that the motor's temperature limits are being exceeded. Sustained motor overload can cause insulation breakdown and permanent damage to the motor.

The temperature of the drive's heat sink has exceeded its maximum permissible limit. This is often caused by high ambient temperatures within the control cabinet, insufficient ventilation, a dirty heat sink impeding heat dissipation, or incorrect mounting position restricting airflow. Overtemperature significantly shortens the lifespan of electronic components and can lead to drive failure.

The motor's PTC (Positive Temperature Coefficient) thermistor has detected an overtemperature condition within the motor, indicating it is too hot due to excessive currents, frequent, or prolonged accelerations. Alternatively, this fault can occur if the PTC sensor is not properly connected or its monitoring is not correctly configured. High motor temperatures can damage insulation and reduce motor lifespan.

The internal temperature of the drive unit itself has become excessively high. This is typically due to continuous operation at high loads, insufficient cooling, or a malfunctioning internal cooling fan. Sustained internal overtemperature can severely degrade electronic components, leading to reduced reliability and potential failure of the drive.

The DC-bus voltage has exceeded its maximum permissible limit. This can be caused by an excessively high incoming mains voltage, or by regenerative energy feedback from the motor during braking or feedback operation. If the drive cannot dissipate this excess energy, the overvoltage can damage the internal power components.

The incoming mains voltage has been continuously above its specified limit for more than 5 seconds. This indicates a persistent problem with the power supply quality, which can stress the drive's input rectifier and DC-bus capacitors. Prolonged exposure to mains overvoltage can lead to premature failure of input stage components.

A general error occurred during the transfer of parameters via the operating module, specifically indicating that both parameter sets (PAR1 and PAR2) are defective. This means the drive's configuration data is corrupt or could not be reliably written. Operating with corrupted parameters can lead to unpredictable drive behavior or prevent the drive from starting.

An error occurred during the transfer of parameter set 1 (PAR1) via the operating module, indicating that PAR1 is defective or corrupted. This means the primary operating configuration of the drive is unreliable. The drive should not be enabled until this is resolved, as it may operate incorrectly or unsafely.

An error occurred during the transfer of parameter set 2 (PAR2) via the operating module, indicating that PAR2 is defective or corrupted. This means the secondary or alternative operating configuration of the drive is unreliable. The drive should not be enabled until this is resolved, as it may operate incorrectly or unsafely.

The drive's auto-TRIP reset function has failed because more than 8 fault messages occurred within a 10-minute period. This indicates an underlying, persistent problem that is repeatedly triggering faults, preventing the drive from reliably resetting itself. The frequent faults suggest an unstable operating condition that requires thorough investigation to prevent damage.

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.