Lenze 8400 BaseLine Drive

Lenze 8400 BaseLine Drive Fault Codes:

Fault Code and Meaning	Cause and Remedy
Su02 One mains phase is missing [xx.0111.00002]	Cause: One mains phase of a three-phase supply has failed. Remedy: Check mains connection (terminal X100).
OH Heatsink overtemperature [xx.0119.00001]	Cause: The heatsink temperature is higher than the fixed limit temperature (90 °C). Maybe the ambient temperature of the controller is too high or the fan or its ventilation slots are dirty. Remedy: Check control cabinet temperature. Clean filter. Clean controller. If required, clean or replace the fan. Provide for sufficient cooling of the device.
OC5 Ixt overload [xx.0119.00050]	Cause: The Ixt overload check has tripped. Operating threshold = 100 % Ixt (adjustable in C123). Wrong dimensioning of the device with regard to its motor load. Load cycles are not complied with. Remedy: Check and, if required, correct dimensioning of the device and the motor load with regard to technical data. Reduce motor load cycles (observe load cycles according to documentation).
OC9 Ixt overload – shutdown limit [xx.0119.00052]	Cause: The Ixt overload check has tripped. Operating threshold = 110 % Ixt (fixed). Wrong dimensioning of the device with regard to its motor load. Load cycles are not complied with. Remedy: Check and, if required, correct dimensioning of the device and the motor load with regard to technical data. Reduce motor load cycles (observe load cycles according to documentation).
OU DC bus overvoltage [xx.0123.00014]	Cause: The device has detected an overvoltage in the DC bus. To protect the hardware, the inverter control is switched off. Auto-start lock function configuration (C142). If active longer than time set in C601, a “Fault” is tripped. Remedy: Reduce load in generator mode. Use a brake resistor. Use a regenerative power supply unit. Establish a DC-bus connection.
LU DC bus undervoltage [xx.0123.00015]	Cause: The device has detected a DC bus undervoltage. Inverter control is switched off because motor control properties cannot be provided. Remedy: Switch on mains supply or ensure sufficient supply via DC bus. Adjust setting in C142 if required.
OC1 Power section – short circuit [xx.0123.00016]	Cause: Short circuit of the motor phases recognised. Mostly, incorrectly executed motor connections are the cause. Device inappropriately dimensioned or Imax controller set incorrectly. Remedy: Check motor connections and the corresponding plug connector on the device. Only use permissible combinations of device power and motor power. Do not set the dynamics of the current limitation controller too high.
OC2 Power section – earth fault [xx.0123.00017]	Cause: Earth fault at one of the motor phases. Mostly, incorrectly executed motor connections. Incorrect dimensioning of motor filter, cable length, or cable type (leakage currents to PE). Remedy: Check motor connections and the corresponding plug connector. Use motor filters, cable lengths, and cable types recommended by Lenze.
ID1 Motor data identification error [xx.0123.00057]	Cause: Error during motor data identification. Interrupted motor cable. Switched-off power section during identification. Implausible start parameter settings. Remedy: Check motor connections and plug connector/terminal box. Correct start parameters (motor nameplate data). Ensure stable power supply.
OC12 I2xt overload – brake resistor [xx.0123.00065]	Cause: Too frequent and too long braking processes. Remedy: Check drive dimensioning.
OC6 I2xt overload – motor [xx.0123.00105]	Cause: Thermal overload of the motor. Remedy: Observe load requirements. Correct dimensioning if necessary. Check Vmin boost (C016) for VFCplus operation.
An01 AIN1_I < 4 mA [xx.0125.00001]	Cause: Open-circuit monitoring for analog input has tripped (only if configured as 4…20 mA loop). Remedy: Check wiring of the analog X4/A1U input terminal for open circuit. Check connection of external 250-Ω load resistor between A1U and GND. Check minimum current values of the signal sources.
CE4 CAN bus off [xx.0131.00000]	Cause: CAN on board: “Bus off” status. Received too many faulty telegrams. Damaged cable (e.g. loose contact). Two nodes have the same ID. Remedy: Check wiring and bus terminating resistor. Set identical baud rate for each bus node. Assign different IDs to nodes. Eliminate electrical interference (e.g. EMC).
CA06 CAN CRC error [xx.0131.00006]	Cause: CAN on board: A faulty CAN telegram has been detected. Remedy: Check wiring and bus terminating resistor. Eliminate electrical interference (e.g. EMC).
CA07 CAN bus warning [xx.0131.00007]	Cause: CAN on board: Incorrect transmission or reception of more than 96 CAN telegrams. Remedy: Check wiring and bus terminating resistor. Set identical baud rate for each bus node. Assign different IDs to nodes. Eliminate electrical interference (e.g. EMC).
CA08 CAN bus stopped [xx.0131.00008]	Cause: CAN on board: The device has received the “Stop Remote Node” NMT telegram. Remedy: Check CAN master (NMT master).
CA0b CAN bus live time [xx.0131.00011]	Cause: CAN on board: Cyclic node monitoring. Heartbeat telegram not received within defined time. Remedy: Reactivate Heartbeat producers by mains switching, restarting controller, or CAN Reset Node. Reparameterise Heartbeat producer time or switch off consumer monitoring.
CA0F CAN control word [xx.0131.00015]	Cause: Bit 14 (“SetFail”) in the wCANControl control word of the system block LS_DriveInterface has been set. Remedy: Trace back signal source on the CAN bus that sets bit 14 (“SetFail”).
CE1 CAN RPDO1 [xx.0135.00001]	Cause: CAN on board: Time monitoring for RPDO1 has tripped. RPDO1 has not been received within the monitoring time set in C357/1 or was faulty. Remedy: Set the correct telegram length at the CAN master (transmitter). Eliminate electrical interference (e.g. EMC). Adjust monitoring time in C357/1 or switch off time monitoring.
CE2 CAN RPDO2 [xx.0135.00002]	Cause: CAN on board: Time monitoring for RPDO2 has tripped. RPDO2 has not been received within the monitoring time set in C357/2 or was faulty. Remedy: Set the correct telegram length at the CAN master (transmitter). Eliminate electrical interference (e.g. EMC). Adjust monitoring time in C357/2 or switch off time monitoring.
PS01 No memory module [xx.0144.00001]	Cause: Memory module is either not available or not snapped into place correctly. Remedy: If a memory module has been provided: Plug the memory module into the slot of the standard device intended for this purpose. Check if the memory module has been plugged-in correctly.
PS02 Par. set invalid [xx.0144.00002]	Cause: The parameter set saved to the memory module is invalid because it has not been saved completely. This can be due to voltage failure or removing the memory module while saving. Remedy: Ensure voltage supply during the storage process. Ensure the module remains plugged into the slot during saving.
PS03 Par. set device invalid [xx.0144.00003]	Cause: The parameter set in the device is invalid. Remedy: Consultation with Lenze required.
PS04 Par. set device incompatible [xx.0144.00004]	Cause: The parameter set saved to the memory module is incompatible to the standard device (e.g. higher version than expected). Remedy: Observe downward compatibility: OK (BaseLine V2.0 to V3.0), Not OK (StateLine to BaseLine), Not OK (BaseLine V3.0 to < V3.0).
PS31 Ident. error [xx.0144.00031]	Cause: Incompatible or unknown HW components have been found. Remedy: Check which HW components are faulty (C203/x: Product type code). Check temperature range of the device at the start. Check whether a software update at Lenze is possible.
dF01 Internal error 01 [xx.0145.00001]	Cause: Device error. Remedy: Reduce switching frequency (C018) to 4 kHz. If the problem occurs again, consult Lenze.
dF02 to dF10 Internal errors [xx.0145.00002 to 00010]	Cause: Device error. Remedy: Mains switching or restart of the controller. If the problem occurs again, consult Lenze.
dH69 Adjustment fault [xx.0400.00105]	Cause: Device error. Remedy: Consultation with Lenze required.
US01 User error 1 [xx.0980.00000]	Cause: User error 1 has been tripped via the bSetError1 input of the LS_SetError_1 system block. Remedy: User-defined.
US02 User error 2 [xx.0981.00000]	Cause: User error 2 has been tripped via the bSetError2 input of the LS_SetError_1 system block. Remedy: User-defined.