Lenze 8400 topline Servo Drive

Lenze 8400 topline Servo Drive Fault Codes:

Fault Code and MeaningCause and Remedy
User error 1
[xx.0980.00000 … xx.0980.65535]
Cause:

User error 1 has been tripped via the bSetError1 input of the LS_SetError_1 system block.



Remedy:

User-defined.
User error 2
[xx.0981.00000 … xx.0981.65535]
Cause:

User error 2 has been tripped via the bSetError2 input of the LS_SetError_1 system block.



Remedy:

User-defined.
User error 3
[xx.0982.00000 … xx.0982.65535]
Cause:

User error 3 has been tripped via the bSetError3 input of the LS_SetError_1 system block.



Remedy:

User-defined.
User error 4
[xx.0983.00000 … xx.0983.65535]
Cause:

User error 4 has been tripped via the bSetError4 input of the LS_SetError_1 system block.



Remedy:

User-defined.
User error 5
[xx.0984.00000 … xx.0984.65535]
Cause:

User error 5 has been tripped via the bSetError1 input of the LS_SetError_2 system block.



Remedy:

User-defined.
User error 6
[xx.0985.00000 … xx.0985.65535]
Cause:

User error 6 has been tripped via the bSetError2 input of the LS_SetError_2 system block.



Remedy:

User-defined.
User error 7
[xx.0986.00000 … xx.0986.65535]
Cause:

User error 7 has been tripped via the bSetError3 input of the LS_SetError_2 system block.



Remedy:

User-defined.
User error 8
[xx.0987.00000 … xx.0987.65535]
Cause:

User error 8 has been tripped via the bSetError4 input of the LS_SetError_2 system block.



Remedy:

User-defined.
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).
Su03
Too frequent mains switching [xx.0111.00003]
Cause:

Too frequent mains switching of the power section.

  • The device recognises if the power section is switched on and off too frequently.

  • To protect internal charging connections from destruction, the device reports this error and prevents the controller inhibit. All other functions are active.

  • Use of a power supply module in the DC-bus connection, the DC terminals of which are connected downstream to the charging connection for the voltage DC bus (e.g. 9400 from 45 kW).





Remedy:

The error must be acknowledged by mains switching. The charging circuit can only cool down when the mains is switched off.

  • After switching the mains 3 times in one minute, there must be a switching pause of 9 minutes.

  • Cyclic mains switching every 3 minutes is permissible.

  • From version 12.00.00 onwards, this power supply module can be used in the DC-bus connection by enabling it via C02865 (bit 8).
Su04
CU insufficiently supplied [xx.0111.00004]
Cause:

After switching on the device, the 24V supply voltage for the control electronics is too low (100 ms after switch-on U is < 19V). The current supply voltage is displayed in C00065.



Remedy:


  • With internal supply voltage via the power electronics, the inverter must be replaced.

  • With external supply voltage, check the correct connection and/or the stability of the supply voltage.
Su06
Mains input overload [xx.0111.00006]
Cause:

In order to protect the device from overload, the following device outputs have a hardware detection in the mains input: 7.5 kW, 11 kW, 15 kW, 30 kW, 37 kW, 45 kW. In case of the error message “Su06”, this hardware detection has responded.



Remedy:


  • Check whether all mains phases are connected (a 2-phase supply may be existent).

  • Provide for sufficient cooling of the device.
Su07
24V supply off [xx.0111.00007]
Cause:

(Not specified in manual source)



Remedy:

(Not specified in manual source)
oH4
Heatsink temp. > shutdown temp. -5°C [xx.0119.00000]
Cause:

The heatsink temperature now only differs by 5 °C from the shutdown temperature of the motor.



Remedy:

Prevent further heating, i.e. reduce motor load or set controller inhibit so that the heatsink can cool down again.
oH1
Heatsink overtemperature [xx.0119.00001]
Cause:

The heatsink temperature is higher than the fixed limit temperature (90 °C). Maybe the ambient temperature of the inverter is too high or the fan or its ventilation slots are dirty.



Remedy:


  • Check control cabinet temperature.

  • Clean filter.

  • Clean the inverter.

  • If required, clean or replace the fan.

  • Provide for sufficient cooling of the device.
oH7
Motor temperature resolver >= C121 [xx.0119.00002]
Cause:

The motor temperature detected via the resolver interface has reached the warning threshold set in C00121/1.



Remedy:


  • Check motor temperature monitoring.

  • Provide for sufficient cooling of the motor.

  • Check terminals for open circuit or loose contact.
oH9
Motor overtemperature resolver [xx.0119.00003]
Cause:

The motor temperature detected via the resolver interface has reached the fixed limit temperature (150 °C).



Remedy:


  • Check motor temperature monitoring.

  • Provide for sufficient cooling of the motor.

  • Check terminals for open circuit or loose contact.
Sd6
Error thermal detector resolver [xx.0119.00012]
Cause:

The signals of the encoder connected to the resolver interface are outside the defined operating range of the motor temperature detection.



Remedy:


  • Check contacts of the encoder cable at the motor and inverter.

  • Check the selected motor temperature sensor in C01190/1 as to whether it complies with the assembly in the motor.

  • If required, switch off thermal sensor monitoring (C00583/5=”0″).
oH3
Motor temperature (X106) triggered [xx.0119.00015]
Cause:

The motor temperature monitoring function at the plug connector X106, terminal T1/T2, has tripped.

Possible causes:

  • The motor is overheated so that the thermal contact integrated into the motor has been switched.

  • An open circuit or a loose contact at the connections mentioned above has occurred.





Remedy:


  • Check motor temperature monitoring.

  • Provide for sufficient cooling of the motor.

  • Check terminals for open circuit or loose contact.
oH6
Motor temperature MultiEncoder >= C121 [xx.0119.00020]
Cause:

The motor temperature detected via the encoder interface has reached the warning threshold set in C00121/2.



Remedy:


  • Check motor temperature monitoring.

  • Provide for sufficient cooling of the motor.

  • Check terminals for open circuit or loose contact.
oH12
Motor overtemperature MultiEncoder [xx.0119.00021]
Cause:

The motor temperature detected via the encoder interface has reached the fixed limit temperature (150 °C).



Remedy:


  • Check motor temperature monitoring.

  • Provide for sufficient cooling of the motor.

  • Check terminals for open circuit or loose contact.
Sd12
Error thermal detector MultiEncoder [xx.0119.00022]
Cause:

The signals of the encoder connected to the encoder interface are outside the defined operating range of the motor temperature detection.



Remedy:


  • Check contacts of the encoder cable at the motor and inverter.

  • Check the selected motor temperature sensor in C01190/2 as to whether it complies with the assembly in the motor.

  • If required, switch off thermal sensor monitoring (C00583/6=”0″).
oC5
Ixt overload [xx.0119.00050]
Cause:

The Ixt overload check has tripped. Operating threshold = 100% Ixt (adjustable in C00123).

Possible causes:

  • 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).
ot1
Maximum torque reached [xx.0123.00001]
Cause:

The device indicates that the maximally possible torque at the motor shaft has been reached. C00057 displays the current torque.



Remedy:

Reduce motor load.
oC7
Motor overcurrent [xx.0123.00007]
Cause:

Maximum current monitoring has tripped. The instantaneous value of the motor current has exceeded the limit value set in C00939.



Remedy:

Check and, if required, correct dimensioning of the load with regard to the installed device power.
oU
DC bus overvoltage [xx.0123.00014]
Cause:

The device has detected an overvoltage in the DC bus. To protect the device hardware, the inverter control is switched off.

  • Depending on the configuration of the auto-start lock function, set C00142 so that, when this error is tripped, the inverter only restarts after the controller inhibit has been switched.

  • If this error message remains active longer than the time set in C00601, a “Fault” is tripped.

  • In case of the control types VFCplus and SLVC, the motor voltage is approached to the voltage setpoint alongside a ramp.





Remedy:


  • Reduce load in generator mode.

  • Use a brake resistor.

  • Use a regenerative power supply unit.

  • Establish a DC-bus connection.

  • Select a braking method in C00175 which stops the ramp function generator when reaching the brake chopper threshold (“HlgStop”).

  • In case of servo control (SC), set the speed controller parameters correctly.
LU
DC bus undervoltage [xx.0123.00015]
Cause:

The device has detected a DC bus undervoltage. The inverter control is switched off because the drive properties of the motor control cannot be provided anymore due to the DC bus undervoltage.



Remedy:


  • Switch on mains supply or ensure sufficient supply via DC bus.

  • Adjust setting in C00142 if required.
oC1
Power section – short circuit [xx.0123.00016]
Cause:

The device has recognised a short circuit of the motor phases. To protect the device electronics, the inverter control is switched off.

  • Mostly, incorrectly executed motor connections are the cause.

  • If the device is inappropriately dimensioned with regard to the motor load and the current limitation in the controller (Imax controller) is set incorrectly, this error message may also occur.





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:

The device has recognised an earth fault at one of the motor phases. To protect the device electronics, the inverter control is switched off.

  • Mostly, incorrectly executed motor connections are the cause.

  • If motor filter, motor cable length, and cable type (shielding capacity) are dimensioned incorrectly, this error message may occur due to leakage currents to PE.

  • If motor filters with additional terminals for +UG and -UG and devices greater or equal 3 kW are used, the earth fault detection may be triggered due to leakage currents to +UG and -UG.





Remedy:


  • Check motor connections and the corresponding plug connector on the device.

  • Use motor filters, cable lengths, and cable types recommended by Lenze.

  • If motor filters with additional terminals for +UG and -UG and devices greater or equal 3 kW are used: Deactivate earth-fault detection during operation by setting the filter time (C01770) to 250 ms.

  • If motor cables longer than 50 m are used: Increase filter time for earth-fault detection during operation (C01770).
Sd2

Open circuit resolver [xx.0123.00024]
Cause:


  • Encoder signal interferences (EMC).

  • Resolver cable interrupted.

  • Resolver defective.




Remedy:


  • Check resolver cable.

  • Check resolver.

  • Switch off monitoring (C00603/2 = “0: No reaction”) when the resolver is not used.
Sd7

Encoder communication error [xx.0123.00026]
Cause:


  • Encoder cable interrupted.

  • Encoder defective.




Remedy:


  • Check encoder cable.

  • Check encoder.

  • Check parameter setting.
Sd4

Open circuit MultiEncoder [xx.0123.00027]
Cause:


  • Encoder cable interrupted.

  • Encoder defective.

  • Supply voltage for the encoder not sufficient.




Remedy:


  • Check encoder cable.

  • Check encoder.

  • Check the set encoder supply voltage in C00421. Adapt setting to the max. permissible encoder supply voltage.

  • Switch off monitoring (C00603/1 = “0: No reaction”) when the encoder is not used.
Sd9

Status message Hiperface [xx.0123.00028]
Cause:

Sd9 is output when the inverter has received a Hiperface encoder error code from the encoder during initialisation. The received error codes are displayed in C00491/1…4.



Remedy:


  • Eliminate the fault described in the error code.

  • Afterwards, reinitialise the encoder by a renewed writing of the encoder type in C00422.
Sd14

Position invalid Hiperface [xx.0123.00029]
Cause:

No standstill of the Hiperface encoder during initialisation. Hence, the absolute Hiperface track and the incremental SinCos track cannot be initiated exactly.



Remedy:


  • Stop encoder movement.

  • Afterwards reinitialise the encoder by a renewed writing of the encoder type in C00422.
oC10

Maximum current reached [xx.0123.00030]
Cause:

The device displays that the maximum current has been reached.



Remedy:


  • Check and, if required, correct dimensioning of the load with regard to the installed device power.

  • Check the maximum current settings in C00022 (motor mode) and C00023 (generator mode).
oC17

Clamp sets pulse inhibit [xx.0123.00031]
Cause:

Due to a short overcurrent, the inverter was switched off for a short time (clamp disconnection).



Remedy:


  • Check and, if required, correct dimensioning of the load with regard to the installed device power.

  • Reduce the dynamics of the setpoint change or speed control.
oS1

Maximum speed limit reached [xx.0123.00032]
Cause:

The device has recognised that the maximum speed has been reached.



Remedy:


  • Limit setpoint selection to maximum values.

  • Adjust set speed limitation (C00909) and frequency limitation (C00910).
oS2

Max. motor speed [xx.0123.00033]
Cause:

The device has recognised that the maximally permissible motor speed has been reached.



Remedy:


  • Limit setpoint selection to the maximally permissible motor speed.

  • If required, adapt set maximum motor speed (C00965).
oC18

Current monitoring overload [xx.0123.00034]
Cause:

The current monitoring overload has tripped because the apparent motor current has exceeded the switch-off threshold set in C00124/1 for the delay time set in C00563/1.



Remedy:


  • Reduce overload.

  • Increase switch-off threshold (C00124/1).
Id2

Motor data identification error [xx.0123.00056]
Cause:

During the identification of the motor parameters, an error has occurred that caused an abortion of the identification process.

Possible causes: Interrupted motor cable, Switched-off power section, Implausible start parameter settings.



Remedy:


  • Check the motor connections and plug connector.

  • Correct start parameters for the motor parameter identification (motor nameplate data).

  • Ensure stable power supply of the device.
Id1

Motor data identification error [xx.0123.00057]
Cause:

During the identification of motor parameters, an error has occurred.

Possible causes: Interrupted motor cable, Switched-off power section, Implausible start parameter settings.



Remedy:


  • Check the motor connections and plug connector.

  • Correct start parameters for the motor parameter identification (motor nameplate data).

  • Ensure stable power supply of the device.
Id3

CINH identification [xx.0123.00058]
Cause:

The device has detected controller inhibit during the motor data identification. This cancels the identification process.



Remedy:


  • Do not set controller inhibit during the motor data identification.

  • Do not execute any device function which may activate controller inhibit.
Id4

Resistor identification error [xx.0123.00059]
Cause:

The device has recognised that an error has occurred in the calculation of the motor cable resistance. The parameters for cable cross-section and cable length are implausible.



Remedy:


  • Enter sensible values for cable cross-section and motor cable length.
Id7

Motor control does not match motor data [xx.0123.00060]
Cause:

At controller enable, the device has detected that the motor control type set in C00006 cannot control the motor type set (e.g. Asynchronous data entered but Synchronous control set).



Remedy:


  • Enter correct motor nameplate data and set a matching motor control type in C00006.
Id8

Speed encoder has not been set [xx.0123.00061]
Cause:

When being in controller enable status, the device has detected that a motor control type with feedback has been set in C00006, but no speed sensor has been set in C00495.



Remedy:


  • Set the speed sensor in C00495.

  • Ensure settings in C00006 and C00495 match.
Sd8

Encoder angular drift monit. [xx.0123.00062]
Cause:


  • Encoder signal interferences (EMC).

  • Encoder cable interrupted.

  • Encoder defective.

  • Faulty parameter setting of the encoder.




Remedy:


  • Check encoder cable, use shorter encoder cable if required.

  • Check encoder.

  • Check parameter setting.

  • If required, switch off monitoring (C00603/3).
oC12

I2xt overload – brake resistor [xx.0123.00065]
Cause:

Too frequent and too long braking processes.



Remedy:


  • Check drive dimensioning.
oC11

Clamp operation active [xx.0123.00071]
Cause:

The device indicates that the “CLAMP” overcurrent limitation has been activated. A permanent clamp operation causes an overload disconnection.



Remedy:


  • Reduce setpoint generation dynamics or motor load.
Id5

Pole position identification error [xx.0123.00074]
Cause:

The rotor position detected via the encoder system does not comply with the controlled output position (plausibility check), or excessive movement detected during identification.



Remedy:


  • Check parameter setting of the pole position identification.

  • If required, adapt error tolerance for plausibility check in C00645/2.

  • If required, adjust permitted movement in C00645/1.
Id6

Resolver ident. error [xx.0123.00075]
Cause:


  • A controller inhibit was set during resolver error identification.

  • A time-out occurred while the algorithm was being processed.

  • The setpoint speed was too small (|nset| < 500 rpm) or not traversed for at least 1 second.




Remedy:


  • Reduce the gain of the speed controller.

  • Check the shielding of the motor and encoder.

  • Controller is enabled after the “Resolver error identification” device command has been set.

  • Ensure that the speed profile is traversed for at least 1 second at constant setpoint speed (|nset| > 500 rpm).
oC13

Maximum current for Fch exceeded [xx.0123.00090]
Cause:

The device has detected a motor current which exceeds the maximum current limit at permanent switching frequency of the inverter.



Remedy:


  • Observe the maximum current setting depending on the set switching frequency of the inverter.

  • Reduce the required load or setting of the dynamic switching frequency if necessary.
ot2

Speed controller output limited [xx.0123.00093]
Cause:

The output of the speed controller has reached the internal limit value. In this status, the speed controller is not able anymore to correct the system deviation.



Remedy:


  • Observe load requirements.

  • Correct dimensioning or reduce setpoint generation dynamics if necessary.

  • Check Motor control.
FC01

Switching frequency reduction [xx.0123.00094]
Cause:

Load-dependent switching frequency reduction.



Remedy:


  • Observe load requirements.

  • Correct dimensioning or reduce setpoint generation dynamics if necessary.
FC02

Maximum speed for Fchop [xx.0123.00095]
Cause:

Maximum speed for chopper frequency has been reached. The maximum speed has been exceeded depending on the switching frequency.



Remedy:


  • Select the correct maximum speed as a function of the switching frequency.

  • Motor control: Determine speed limits.
oC14

Direct-axis current controller limitation [xx.0123.00096]
Cause:

Direct-axis current controller limitation is active.



Remedy:


  • Observe load requirements.

  • Correct dimensioning or reduce setpoint generation dynamics if necessary.
oC15

Cross current controller limitation [xx.0123.00097]
Cause:

Cross current controller limitation is active.



Remedy:


  • Observe load requirements.

  • Correct dimensioning or reduce setpoint generation dynamics if necessary.

  • Check parameter setting of the current controller with regard to the motor controllers (e.g. reduce Vp).
oC16

Torque controller limitation [xx.0123.00098]
Cause:

Actuator limitation according to speed controller.



Remedy:


  • Observe load requirements.

  • Correct dimensioning or reduce setpoint generation dynamics if necessary.
FC03

Field controller limitation [xx.0123.00099]
Cause:

The output of the field controller has reached its maximum limit value. The drive is at the torque limit in the field weakening range.



Remedy:


  • Observe load requirements.

  • Correct dimensioning or reduce setpoint from the field weakening range if necessary.
oC6

I2xt overload – motor [xx.0123.00105]
Cause:

Thermal overload of the motor.



Remedy:


  • Check whether is it a self-ventilated motor. If not, set C00606 to “0: No Reaction”.

  • Observe load requirements.

  • Correct dimensioning if necessary.

  • For VFCplus control type: Check Vmin boost (C00016).
LP1

Motor phase failure [xx.0123.00145]
Cause:

Motor phase failure – power section. A motor phase carries less current of one half-wave than set in C00599.



Remedy:


  • Check the motor connections and the corresponding plug connector on the device.

  • Check the trigger threshold (C00599).
Sd10

Speed limit – feedback system 12 [xx.0123.00200]
Cause:

Maximally permissible speed of the feedback system connected to DI1/DI2 reached.



Remedy:


  • Reduce speed of the rotation shaft/feedback system.
Sd11

Speed limit for feedback system 67 [xx.0123.00201]
Cause:

Maximally permissible speed of the feedback system connected to DI6/DI7 reached.



Remedy:


  • Reduce speed of the rotation shaft/feedback system.
Sd3
[xx.0123.00205]

Open circuit HTL 2-fold or 4-fold
Cause:

HTL encoder cable interrupted or HTL encoder is defective.

Note: The reason can also be a very dynamic acceleration or an approach against a blocked motor shaft (e.g. with closed holding brake).



Remedy:

  • Check HTL encoder cable.

  • Check HTL encoder.

  • Check related terminals.

  • Switch off monitoring (C00586 = “0: No reaction”) when the HTL encoder is not used.
Sd13
[xx.0123.00206]

Inaccuracy SinCos
Cause:

Only in case of “Multi-Encoder” speed encoder selection (C00495 = 3). A plausibility check for the digital and analog signals of the absolute value encoder (Hiperface) or sin/cos encoder has responded.

The reason for this are EMC interferences.



Remedy:

  • Eliminate EMC interference.
Sd15
[xx.0123.00207]

Open circuit TL 4-fold
Cause:

From version 15.00.00 onwards, Sd15 is triggered if due to different signal levels (4-fold evaluation of the digital inputs) an open circuit has been detected.



Remedy:

  • Check HTL encoder cable.

  • Check HTL encoder.

  • Check wiring of the input terminals for open circuit or loose contact.
Sd16
[xx.0123.00208]

Hiperface-SinCos deviation
Cause:

The deviation between the position of a Hiperface encoder detected from the evaluation of the SinCos track and the position of the Hiperface track detected in parallel is monitored.

Sd16 is triggered if the electrical deviation is higher than 45°. Monitoring is only active as long as the motor speed is below 100 rpm.



Remedy:

  • (No specific remedy listed in source; implied check encoder mounting/interference).
An01
[xx.0125.00001]

AIN1_I < 4 mA
Cause:

Open-circuit monitoring for analog input 1 has tripped.

Only if the analog input has been configured as a current loop of 4 … 20 mA.



Remedy:

  • Check wiring of the analog X3/A1I input terminal for open circuit.

  • Check minimum current values of the signal sources.
An02
[xx.0125.00002]

AIN2_I < 4 mA
Cause:

Open-circuit monitoring for analog input 2 has tripped.

Only if the analog input has been configured as a current loop of 4 … 20 mA.



Remedy:

  • Check wiring of the analog X3/A2I input terminal for open circuit.

  • Check minimum current values of the signal sources.
Ab01
[xx.0126.00001]

Axis bus time-out
Cause:

The axis bus data error monitoring has been triggered as the monitoring time for data errors has been exceeded.

Can be caused by incorrect transmission or reception of telegrams.



Remedy:

  • Check wiring and bus terminating resistor.

  • Assign different IDs to nodes.

  • Eliminate electrical interference (e.g. EMC).
Ab02
[xx.0126.00002]

Axis bus IO error
Cause:

An axis bus node has put the IO axis bus into the “error” status with parameterised “master/slave” function (“release cord” principle).



Remedy:

  • Remove the fault of the node which pulled the “release cord”.

  • Note: The “error” status can only be reset by the node defined as “master”.
CE04
[xx.0127.00002]

MCI communication error
Cause:

Communication error with extension module in slot 1.



Remedy:

  • Eliminate EMC interference.

  • Switch off inverter, plug in module correctly, switch on inverter again.

  • Switch the mains or restart inverter.

  • Replace module/inverter.

  • Please contact Lenze if the problem occurs again.
CE0F
[xx.0127.00015]

MCI control word
Cause:

Bit 14 (“SetFail”) of the wMciCtrl control word of the LS_DriveInterface system block has been set.



Remedy:

  • Trace back signal source on the bus (e.g. PROFIBUS) that sets bit 14 (“SetFail”).
CE4
[xx.0131.00000]

CAN bus off
Cause:

CAN on board: “Bus off” status. Received too many faulty telegrams, damaged cable, or two nodes with 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
[xx.0131.00006]

CAN CRC error
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
[xx.0131.00007]

CAN bus warning
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
[xx.0131.00008]

CAN bus stopped
Cause:

CAN on board: The device has received the “Stop Remote Node” NMT telegram.



Remedy:

  • Check CAN master (NMT master).
CA0b
[xx.0131.00011]

CAN HeartBeatEvent
Cause:

CAN on board: Cyclic node monitoring. Being a Heartbeat consumer, the device has not received a Heartbeat telegram from Heartbeat producer within the defined time.



Remedy:

  • Reactivate Heartbeat producers by mains switching, restarting the inverter, or a CAN Reset Node.

  • Reparameterise CAN Heartbeat producer time or switch off consumer monitoring and reset error status if latched.
CA0F
[xx.0131.00015]

CAN control word
Cause:

Bit 14 (“SetFail”) in the wCANControl control word of the LS_DriveInterface system block has been set.



Remedy:

  • Trace back signal source on the CAN bus that sets bit 14 (“SetFail”).
CE1
[xx.0135.00001]

CAN RPDO1
Cause:

CAN on board: Time monitoring for RPDO1 has been triggered. RPDO1 has not been received within the monitoring time set in C00357/1 or was faulty.



Remedy:

  • Set correct telegram length for CAN master (transmitter).

  • Eliminate electrical interference (e.g. EMC).

  • Adjust monitoring time C00357/1 or switch off time monitoring.
CE2
[xx.0135.00002]

CAN RPDO2
Cause:

CAN on board: Time monitoring for RPDO2 has been triggered. RPDO2 has not been received within the monitoring time set in C00357/2 or was faulty.



Remedy:

  • Set correct telegram length for CAN master (transmitter).

  • Eliminate electrical interference (e.g. EMC).

  • Adjust monitoring time C00357/2 or switch off time monitoring.
CE3
[xx.0135.00003]

CAN RPDO3
Cause:

CAN on board: Time monitoring for RPDO3 has been triggered. RPDO3 has not been received within the monitoring time set in C00357/3 or was faulty.



Remedy:

  • Set correct telegram length for CAN master (transmitter).

  • Eliminate electrical interference (e.g. EMC).

  • Adjust monitoring time C00357/3 or switch off time monitoring.
CE5
[xx.0135.00004]

CAN RPDO4
Cause:

CAN on board: Time monitoring for RPDO4 has been triggered. RPDO4 has not been received within the monitoring time set in C00357/4 or was faulty.



Remedy:

  • Set correct telegram length for CAN master (transmitter).

  • Eliminate electrical interference (e.g. EMC).

  • Adjust monitoring time C00357/4 or switch off time monitoring.
CI01
[xx.0140.00013]

Module missing/incompatible
Cause:

The optional communication module has been removed or there is a connection problem or incompatibility with the standard device.



Remedy:

  • Check connection between the communication module and standard device.

  • Check if the module is plugged in correctly.

  • In case of an incompatibility, either the module or the software of the standard device is out of date. Contact Lenze.
PS01
[xx.0144.00001]

No memory module
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
[xx.0144.00002]

Par. set invalid
Cause:

The parameter set stored in the memory module is invalid (incomplete storage due to voltage failure, or firmware/device mismatch).



Remedy:

  • The error can only be removed by loading the Lenze setting with the C00002/1 = “1: On / start” device command.

  • In order to prevent the error, do not switch off the voltage during the saving process.

  • Use the “copy parameter set” function of the keypad if transferring between versions.
PS03
[xx.0144.00003]

Par. set device invalid
Cause:

The parameter set saved to the memory module is incompatible to the standard device.



Remedy:

  • If the parameter set is compatible but has a lower version, save the parameter set again to eliminate the “Information” message.

  • If saving to a higher device version, you can no longer load it to a lower version.

  • Observe compatibility (e.g. StateLine V2.0 to V3.0 is OK, but HighLine to StateLine is Not OK).
PS04
[xx.0144.00004]

Par. set Mci invalid
Cause:

The parameter set saved to the communication module is incompatible to the standard device.



Remedy:

  • Observe compatibility when replacing memory modules (e.g. Profibus V1.0 to EtherCAT V1.0 is Not OK).
PS07
[xx.0144.00007]

Par. memory module invalid
Cause:

The parameter set saved to the memory module is invalid. The memory module plugged in the device lacks a code or a code is incorrect.



Remedy:

  • Please contact Lenze.
PS08
[xx.0144.00008]

Par. device invalid
Cause:

The parameter set in the device is invalid. One code in the device is incorrect.



Remedy:

  • Please contact Lenze.
PS09
[xx.0144.00009]

Par. format invalid
Cause:

The code format is invalid. The error occurs while loading the parameter set.



Remedy:

  • Please contact Lenze.
PS10
[xx.0144.00010]

Memory module binding invalid
Cause:

Device personalisation is active: The binding ID of the memory module does not comply with the binding ID of the inverter.



Remedy:

  • Use memory module/ inverter with matching binding IDs.

  • Contact machine manufacturer.
PS11
[xx.0144.00011]

Lenze setting loaded
Cause:

(Informational message indicating default settings loaded).



Remedy:

  • (No specific remedy action required).
dF14
SW-HW invalid [xx.0145.00014]
Cause:

Device error.


Remedy:

Please contact Lenze.
dF15
DCCOM CU2 error [xx.0145.00015]
Cause:

Device error.


Remedy:

Please contact Lenze.
dF18
BU RCOM error [xx.0145.00024]
Cause:

Device error.


Remedy:

Please contact Lenze.
dF25
CU RCOM error [xx.0145.00025]
Cause:

Device error.


Remedy:

Please contact Lenze.
dF26
Appl. watchdog [xx.0145.00026]
Cause:

Time-out of the application. The required computing time of the application exceeds the available computing time.


Remedy:

Reduction of the function block interconnection or the complexity of the application.
dF21
BU watchdog [xx.0145.00033]
Cause:

Device error.


Remedy:

Please contact Lenze.
dF22
CU watchdog [xx.0145.00034]
Cause:

Device error.


Remedy:

Please contact Lenze.
dF10
AutoTrip reset [xx.0145.00035]
Cause:

Too frequent auto-trip reset.


Remedy:


  • Check the error cause that activates the auto-trip reset.

  • Eliminate error cause and reset (acknowledge) error manually afterwards.
dF50
Retain error [xx.0145.00050]
Cause:

An error has occurred when accessing retain data. Either caused by an internal hardware error or by lack of mains switching after a firmware download.


Remedy:

Mains switching. Please contact Lenze if the problem occurs again.
dF51
CuCcr error [xx.0145.00051]
Cause:

Device error.


Remedy:

Mains switching. Please contact Lenze if the problem occurs again.
dF52
BuCcr error [xx.0145.00052]
Cause:

Device error.


Remedy:

Mains switching. Please contact Lenze if the problem occurs again.
Ck01
Pos. HW limit switch [xx.0184.00001]
Cause:

MCK: The hardware limit switch in positive traversing direction has tripped. The bLimitSwitchPos input for travel range monitoring via positive hardware limit switch has been set to FALSE (fail-safe).


Remedy:

Reset error message and retract limit switch.
Ck02
Neg. HW limit switch [xx.0184.00002]
Cause:

MCK: The hardware limit switch in negative traversing direction has tripped. The bLimitSwitchNeg input for travel range monitoring via negative hardware limit switch has been set to FALSE (fail-safe).


Remedy:

Reset error message and retract limit switch.
Ck15
Error status sign. brake [xx.0184.00005]
Cause:

MCK: The status monitoring of the holding brake control has tripped.


Remedy:


  • Check configuration of the bMBrakeApplied input for status detection of the brake (via a switching contact at the brake).

  • Check wiring/function of the switching contact.

  • Adapt waiting time (C02589/3).

  • Deactivate status monitoring (via bit 5 in C02582).
Ck03
Pos. SW limit position [xx.0184.00007]
Cause:

MCK: The device has detected that the position is outside the positive software limit position (C01229/1).


Remedy:


  • Increase permissible traversing range (change setting of the software limit positions).

  • Deactivate software limit position monitoring.
Ck04
Neg. SW limit position [xx.0184.00008]
Cause:

MCK: The device has detected that the position is outside the negative software limit position (C01229/2).


Remedy:


  • Increase permissible traversing range (change setting of the software limit positions).

  • Deactivate software limit position monitoring.
Ck14
Target position outside SW limit position [xx.0184.00015]
Cause:

MCK: It has been attempted to position a target outside the software limit positions (C01229/1 and C01229/2).


Remedy:


  • Select a target within the software limit positions.

  • Increase permissible traversing range (change setting of the software limit positions).

  • Deactivate software limit position monitoring.
Ck16
Time overflow manual operation [xx.0184.00064]
Cause:

PC manual control: The connection monitoring has tripped. The online connection between the PC and the inverter has been interrupted for a longer period of time than the timeout set in C00464/1.


Remedy:


  • Check communication link between PC and inverter.

  • Check voltage supply/function of the inverter.

  • Adjust the timeout (C00464/1).
Ck05
Following error 1 [xx.0184.00153]
Cause:

MCK: Following error limit 1 (C01215/1) has been exceeded.


Remedy:


  • Optimise control mode.

  • Increase following error limit.

  • Deactivate following error monitoring.
Ck06
Following error 2 [xx.0184.00154]
Cause:

MCK: Following error limit 2 (C01215/2) has been exceeded.


Remedy:


  • Optimise control mode.

  • Increase following error limit.

  • Deactivate following error monitoring.
Ck07
Travel range limit exceeded [xx.0184.00155]
Cause:

MCK: The maximum travel distance has been exceeded. The maximum travel distance is displayed in C01213/1.


Remedy:


  • Check profile parameters.

  • Deactivate travel range limit monitoring.
Ck08
Home position unknown [xx.0184.00156]
Cause:

MCK: Home position is unknown.


Remedy:

Perform homing.
Ck09
Positioning mode invalid [xx.0184.08005]
Cause:

MCK: The positioning mode defined via the wPosProfileMode input is not supported.


Remedy:

Define a valid positioning mode.
Ck10
Implausible profile data [xx.0184.08007]
Cause:


  • Cause 1: The profile data result in a braking distance that is longer than the distance to be travelled.

  • Cause 2: Reversing process in overchange profile linkage (linkage of two profiles causes reversing not smoothed by sequence profile).

  • Cause 3: Final speed at overchange is higher than maximum profile speed.

  • Cause 4: Traversing, accelerating or braking is not possible due to 0-parameters.




Remedy:


  • On cause 1a: Set the S rounding to zero for the respective profile and go to the next profile with final speed zero.

  • On cause 1b: The error can be avoided with C02868/Bit02!

  • On cause 2: The continuous profile linkage with overchange must not provide any reversing process due to the profile selection.

  • On cause 3: Profiles in an overchange profile linkage with final speeds higher than their max. profile speeds are not supported.

  • On cause 4: Ensure that the corresponding profile parameters for speed, acceleration and deceleration are set to non-zero.
Ck11
Invalid operating mode [xx.0184.08009]
Cause:

MCK: The operating mode defined via the wMckOperationMode input is not supported.


Remedy:

Define a valid operating mode.
Ck12
Invalid profile number [xx.0184.08014]
Cause:

MCK: The positioning profile number in the positioning operating mode specified via the wPosProfileNo input is invalid.


Remedy:

Define a valid profile number.
Ck13
Error – MCKCtrlInterface function block [xx.0184.08015]
Cause:

MCK: An error in the L_MckCtrlInterface_1 function block has occurred.


Remedy:

Check the configuration and parameterisation of the L_MckCtrlInterface_1 FB. In this regard, also observe the status messages of the FB (wFailState or C01299 output).
dH09
EEPROM power section [xx.0400.00009]
Cause:

Device error.


Remedy:

Please contact Lenze.
dH10
Fan failure [xx.0400.00016]
Cause:

The device fan has failed. Possible causes:

  • The short-circuit check of the fan connection has tripped.

  • The speed monitoring of the fan has tripped.




Remedy:


  • Check the fan for short-circuit.

  • Clean the fan.
dH68
Adjustment data error CU [xx.0400.00104]
Cause:

Device error.


Remedy:

Please contact Lenze.
dH69
Adjustment data error BU [xx.0400.00105]
Cause:

Device error.


Remedy:

Please contact Lenze.
dH70
ControlUnit is unequal to BaseUnit [xx.0400.00106]
Cause:

Device error.


Remedy:

Please contact Lenze.