Lenze 8400 stateline Drive

Lenze 8400 stateline Drive Fault Codes:

Fault Code and Meaning	Cause and Remedy
0x01bc3100 Connection to 8400 standard device lost	Cause: Network cable (plug) is defective. Network cable is not connected to the PROFIBUS terminal X201. Voltage supply is interrupted. Remedy: Check cables and terminals. Connect network cable to the PROFIBUS terminal X201.
0x01bc5531 Memory: No access	Cause: Access to memory was not possible. Remedy: Repeat the download of the application (including module).
0x01bc5532 Memory: Read error	Cause: Parameter could not be read. Remedy: Repeat the download of the application (including module).
0x01bc5533 Memory: Write error	Cause: Parameter could not be written. Remedy: Repeat the download of the application (including module).
0x01bc6010 Restart after watchdog reset	Cause: Module defective. Remedy: If this occurs repeatedly, contact the Lenze service.
0x01bc6011 Internal error	Cause: Module defective. Remedy: If this occurs repeatedly, contact the Lenze service.
0x01bc6100 Internal error	Cause: Internal error. Remedy: If this occurs repeatedly, contact the Lenze service.
0x01bc6101 Internal error	Cause: The communication module carries out an automatic software reset and reinitialises itself. Remedy: If this occurs repeatedly, contact the Lenze service.
0x01bc6110 Internal error	Cause: Module defective. Remedy: If this occurs repeatedly, contact the Lenze service.
0x01bc641f Invalid parameter set	Cause: No active parameter set could be loaded. Remedy: Repeat the download of the application (including module).
0x01bc6420 Error: Lenze settings loaded	Cause: Access to parameter set was not successful. Remedy: Repeat the download of the application (including module).
0x01bc8130 Profibus watchdog: Monitoring time elapsed	Cause: Permanent interruption of communication to the PROFIBUS master. Remedy: Check cables and terminals.
0x01bc8131 Profibus: Data_Exchange state exited	Cause: Data exchange via PROFIBUS has been stopped. Remedy: Check cables and terminals. The slave must receive new parameterisation and configuration files from the master in order to be able to exchange data again.
0x01bc8132 Profibus watchdog: DP-V1 MSC2 monitoring time exceeded	Cause: Permanent interruption of communication to C2-PROFIBUS master. Remedy: Check cables and terminals.
0x01bc3100 Lost connection to 8400 base device	Cause: Network cable (plug) is defective. Network cable at INTERBUS terminal X206 (IN) or X207 (OUT) is disconnected. Remedy: Check network cable (plug) and replace it, if required. Plug in network cable at INTERBUS terminal X206 (IN) or X207 (OUT).
0x01bc5531 Memory not accessible	Cause: Memory could not be accessed. Remedy: Send module with error description to Lenze.
0x01bc5532 Memory read error	Cause: Parameter in the memory module could not be read. Remedy: Repeat download of the application (including module).
0x01bc5533 Memory write error	Cause: Parameter in the memory module could not be written. Remedy: Repeat download of the application (including module).
0x01bc6010 Internal error	Cause: Communication module is defective. Remedy: Send communication module with error description to Lenze.
0x01bc6011 Internal error	Cause: Communication module is defective. Remedy: Send communication module with error description to Lenze.
0x01bc6100 Internal error	Cause: Communication module is defective. Remedy: Send communication module with error description to Lenze.
0x01bc6101 Internal error	Cause: Communication module is defective. Remedy: Send communication module with error description to Lenze.
0x01bc641f Invalid parameter set	Cause: Loading of an active parameter set was not possible. Remedy: Repeat download of the application (including module).
0x01bc6420 Lenze setting loaded	Cause: Access via standard device to the parameter set in the memory module failed. Remedy: Repeat download of the application (including module).
0x01bc6430 Invalid module configuration	Cause: Module configuration is faulty. Remedy: Check and correct module configuration.
0x01bc8125 Invalid configuration	Cause: The active configuration is invalid: Data word sum (PD + PCP) > 10 words Data word sum (PD + PCP) = 0 Remedy: Adapt the number of PD and PCP: Data word sum (PD + PCP) = 1 … 10 words
0x01bc8126 Communication stack reset	Cause: Error during processing the INTERBUS services. Remedy: Execute reinitialisation by the master.
0x01bc8127 Invalid initialisation	Cause: The INTERBUS initialisation has failed. Remedy: Execute reinitialisation by the master.
0x01bc8131 Data exchange stopped	Cause: The data exchange at the INTERBUS has been terminated. Remedy: Check cables and connections. Execute reinitialisation by the master.
0x01bc3100 Lost connection to 8400	Cause: MCI communication for the Inverter Drives 8400 is interrupted. Inverter Drive 8400 is switched off. The communication module has not been inserted properly into the slot of the Inverter Drives 8400. Remedy: Switch on Inverter Drive 8400. Check screwed connection of the communication module to the MC slot of the Inverter Drive 8400. Send communication module and Inverter Drive 8400 with error description to Lenze.
0x01bc5531 Memory: No access	Cause: Access via standard device to parameter set within the memory module was not successful. Remedy: Repeat download of the application (including module).
0x01bc5532 Memory: Read error	Cause: Parameters of the memory module could not be read. Remedy: Repeat download of the application (including module).
0x01bc5533 Memory: Write error	Cause: Parameters of the memory module could not be written. Remedy: Repeat download of the application (including module).
0x01bc6010 Restart by watchdog reset	Cause: Communication module is defective. Remedy: Send communication module with error description to Lenze.
0x01bc6011 Internal error	Cause: Communication module is defective. Remedy: Send communication module with error description to Lenze.
0x01bc6100 Internal error	Cause: Communication module is defective. Remedy: Send communication module with error description to Lenze.
0x01bc6101 Internal error	Cause: Communication module is defective. Remedy: Send communication module with error description to Lenze.
0x01bc641f Invalid parameter set	Cause: No active parameter set could be loaded. Remedy: Repeat download of the application (including module).
0x01bc6420 Error: Lenze setting loaded	Cause: Access via standard device to parameter set within the memory module was not successful. Remedy: Repeat download of the application (including module).
0x01bc6430 Invalid module configuration	Cause: Faulty module configuration. Incorrect sync settings. Remedy: Check and correct module configuration/sync settings.
0x01bc8131 Operational status quit	Cause: The EtherCAT data exchange was stopped in the “Operational” state. See also chapter “Interruption of EtherCAT communication”. Remedy: Check cables and terminals. The master has to reset the node to the “Operational” status. (If required, check a pending emergency message first).
0x01bc8700 Sync telegram failure	Cause: The cycle time settings are faulty. The task time setting of a linked PLC program is faulty. EtherCAT master / DC master settings are incorrect. The sync source setting is faulty. Remedy: Check the cycle times. Check the task time of a linked PLC program. Check the EtherCAT master / DC master settings. Check the settings in C01120 of the standard device (selection of the sync source).
0x01bc3100 PROFINET: Exist. conn. to 8400 lost	Cause: MCI communication to Inverter Drive 8400 is interrupted. – Inverter Drive 8400 is switched off. – The communication module is not connected correctly at the MCI slot. Remedy: Switch on Inverter Drive 8400. Check screwed connection of the communication module at the MCI slot. Send the communication module and Inverter Drive 8400 together with a description of the fault to Lenze.
0x01bc5531 PROFINET: Memory: No access	Cause: Access to memory was not possible. Remedy: Send communication module together with a description of the fault to Lenze.
0x01bc5532 PROFINET: Memory: Read error	Cause: Parameter could not be read. Remedy: Send communication module together with a description of the fault to Lenze.
0x01bc5533 PROFINET: Memory: Write error	Cause: Parameter could not be written. Remedy: Send communication module together with a description of the fault to Lenze.
0x01bc6010 PROFINET: Restart by watchdog reset	Cause: Communication module is defective. Remedy: Send communication module together with a description of the fault to Lenze.
0x01bc6011 PROFINET: Internal error	Cause: Communication module is defective. Remedy: Send communication module together with a description of the fault to Lenze.
0x01bc6100 PROFINET: Internal error	Cause: Internal error. Remedy: Send communication module together with a description of the fault to Lenze.
0x01bc6101 PROFINET: Internal error	Cause: Internal error. Remedy: Send communication module together with a description of the fault to Lenze.
0x01bc641f PROFINET: Invalid parameter set	Cause: No active parameter set could be loaded. Remedy: Download application again (including module). Send communication module together with a description of the fault to Lenze.
0x01bc6420 PROFINET: Error: Lenze setting loaded	Cause: Access to parameter set in the memory module was not possible. Remedy: Download application again (including module). Send device with error description to Lenze.
0x01bc6430 PROFINET: Invalid module configuration	Cause: A module or submodule does not comply with the configuration of the Siemens S7 engineering tool. Remedy: Check configuration.
0x01bc6501 PROFINET: Record Parameter: Invalid read	Cause: Invalid parameter read access. Remedy: Check configuration.
0x01bc6502 PROFINET: Record Parameter: Invalid write	Cause: Invalid parameter write access. When reading back the data, the IO Controller has requested a data length (number of data bytes) that is too small. Remedy: Check configuration.
0x01bc6503 PROFINET: Data output status bad	Cause: – Output data invalid. – Connection to Siemens S7 has been interrupted. Remedy: Check cables and terminals. Connect network cable to PROFINET connections.
0x01bc6531 PROFINET: Data_Exchange status quit	Cause: The data exchange via PROFINET has been terminated. (Also see chapter “Interruption of PROFINET communication”). Remedy: Check cables and terminals. Connect network cable to PROFINET connections.
0x01bc6532 PROFINET: Station name error	Cause: Station name is not DNS-conform. Remedy: Use a DNS-compliant station name. (Refer to “Setting the station name”).
0x01bc6533 PROFINET: IP address error	Cause: An invalid IP address has been assigned by the I/O controller via PROFINET or has been set in code C13000. Remedy: Make sure that the I/O controller has assigned a valid IP address via PROFINET. Set a valid IP address. (Refer to “Setting the IP configuration”).
0x01bc6534 PROFINET: Stack init error	Cause: The stack cannot be initialised with the parameters selected by the user. This may be due to a station name which does not comply with the PROFINET specification. Remedy: Check and, if necessary, adapt PROFINET parameters: – Setting the IP configuration. – Setting the station name.
0x01bc6650 PROFINET: Internal error	Cause: Internal error. Remedy: Send communication module together with a description of the fault to Lenze.
0x01bc3100 EtherNet/IP: Exist. connect. to 8400 lost	Cause: The communication module is being supplied with external voltage but the Inverter Drive 8400 is not being supplied with voltage. The communication module has not been correctly connected to the Inverter Drive 8400. Remedy: Supply the Inverter Drive 8400 with voltage. Securely connect the communication module to the Inverter Drive 8400.
0x01bc5531 EtherNet/IP: Memory: No Access	Cause: Access to memory was not possible. Remedy: Send communication module together with a description of the fault to Lenze.
0x01bc5532 EtherNet/IP: Memory: Read Error	Cause: Parameter could not be read. Remedy: Download application again (including module). Send communication module together with a description of the fault to Lenze.
0x01bc5533 EtherNet/IP: Memory: Write Error	Cause: Parameter could not be written. Remedy: Download application again (including module). Send communication module together with a description of the fault to Lenze.
0x01bc6010 EtherNet/IP: Restart by Watchdogreset	Cause: Communication module is defective. Remedy: Send communication module with error description to Lenze.
0x01bc6011 EtherNet/IP: Internal Error	Cause: Communication module is defective. Remedy: Send communication module with error description to Lenze.
0x01bc6100 EtherNet/IP: Internal Error	Cause: Communication module is defective. Remedy: Send communication module with error description to Lenze.
0x01bc6101 EtherNet/IP: Internal Error	Cause: Communication module is defective. Remedy: Send communication module with error description to Lenze.
0x01bc641f EtherNet/IP: Invalid Parameter Set	Cause: No active parameter set could be loaded. Remedy: Download application again (including module). Send communication module together with a description of the fault to Lenze.
0x01bc6420 EtherNet/IP: Error: Lenze Setting Loaded	Cause: Access to parameter set was not possible. Remedy: Download application again (including module). Send communication module together with a description of the fault to Lenze.
0x01bc6430 EtherNet/IP: Invalid Configuration	Cause: Module configuration is faulty. Remedy: Check and correct module configuration.
0x01bc6533 EtherNet/IP: Invalid IP parameters	Cause: One or more IP parameters are faulty. Remedy: Check and correct IP configuration (See Manual Page 42).
0x01bc8111 EtherNet/IP: Fault Mode	Cause: Connection to scanner has been interrupted. Controlling I/O connection failed by timeout. Within the timeout time for implicit messages parameterised by the scanner, no “implicit messages” have been received. Remedy: Check cables and terminals. Plug in the network cable into the Ethernet port. Check Requested Package Interval (RPI) of I/O connection. Increase timeout time for implicit messages.
0x01bc8112 EtherNet/IP: Explicit Message Timeout	Cause: Connection to scanner has been interrupted. Failure of an explicit connection. Within the timeout time for explicit messages parameterised by the scanner, no “explicit messages” have been received. Remedy: Check cables and terminals. Plug in the network cable into the Ethernet port. Check Requested Package Interval (RPI) of the explicit connection. Increase timeout time for explicit messages.
0x01bc8114 EtherNet/IP: Overall Ethernet Timeout	Cause: Failure of »Engineer« communication via Ethernet. When the time set in C13881 has expired, there is no access via the »Engineer«. Remedy: Check cables and terminals. Plug in the network cable into the Ethernet port. Increase the overall Ethernet timeout time in C13881.
0x01bc8121 EtherNet/IP: Ethernet cable pulled out	Cause: Network cable has been detached from the Ethernet terminal. Network cable (plug) is defective. Remedy: Plug the network cable into the Ethernet terminal. Check the network cable (plug) and replace it if necessary.
0x01bc8132 EtherNet/IP: Idle Mode	Cause: Scanner has received an idle event. The scanner is in the “PROG” mode. In the “Scanner Command Register”, the run/idle flag (bit 0) is 0. Remedy: Set the scanner to the run mode. Run/idle flag (bit 0) = 1.
0x01bc8273 EtherNet/IP: Duplicate IP Address	Cause: An IP address has been allocated twice within the network. The addresses of the network nodes must differ from each other. Remedy: Correct the IP address (C13000). (See Manual Page 42).
0x01bc3100 EPL: Lost connection to 8400 target	Cause: MCI communication to Inverter Drive 8400 is interrupted. Inverter Drive 8400 is switched off. The communication module is not connected correctly at the MCI slot of the Inverter Drive 8400. Remedy: Switch on Inverter Drive 8400. Check screwed connection of the communication module at the MCI slot of the Inverter Drive 8400. Send the communication module and Inverter Drive 8400 together with a description of the fault to Lenze.
0x01bc5531 EPL: NV Memory: No access	Cause: Access to parameter set in memory module via standard device was not successful. Remedy: Download application again (including module).
0x01bc5532 EPL: NV Memory: Read error	Cause: Parameter in the memory module could not be read. Remedy: Download application again (including module).
0x01bc5533 EPL: NV Memory: Write error	Cause: Parameter in the memory module could not be written. Remedy: Download application again (including module).
0x01bc6010 EPL: Restart after watchdog reset	Cause: Communication module is defective. Remedy: Send the communication module and a description of the fault to Lenze.
0x01bc6011 EPL: Watchdog reset	Cause: Communication module is defective. Remedy: Send the communication module and a description of the fault to Lenze.
0x01bc6100 EPL: Software error	Cause: Communication module is defective. Remedy: Send the communication module and a description of the fault to Lenze.
0x01bc6101 EPL: Fatal software error	Cause: Communication module is defective. Remedy: Send the communication module and a description of the fault to Lenze.
0x01bc6110 EPL: PDO Mapping invalid	Cause: Invalid mapping configuration. Remedy: Correct the mapping configuration.
0x01bc641f EPL: Invalid parameter set	Cause: No active parameter set could be loaded. Remedy: Download application again (including module).
0x01bc6420 EPL: Factory settings loaded	Cause: Access to parameter set in memory module via standard device was not successful. Remedy: Download application again (including module).
0x01bc6430 EPL: Invalid module configuration	Cause: Module configuration is faulty. Remedy: Check and correct module configuration.
0x01bc8131 EPL: State OPERATIONAL lost	Cause: Data exchange via POWERLINK has been terminated. Also see chapter “Interruption of POWERLINK communication”. Remedy: Check the network cable (plug) and replace it if necessary. Connect the network cable to the Ethernet POWERLINK terminals X251 or X252 and continue to check the status of the managing node.
0x01bc8261 EPL: Invalid address selected	Cause: An invalid IP address has been assigned by the managing node via POWERLINK or set as node ID. Remedy: Ensure that a valid IP address is assigned by the managing node via POWERLINK. Set valid node ID.
0x01bc8265 EPL: Synchronisation lost from MN	Cause: In the controlled node, the synchronisation cycle of the managing node has failed. The controlled node changes automatically to the NMT_CS_PREOPERATIONAL_1 state and waits for a new run-up by the managing node. Remedy: Check network cable and components (failure of managing node, router). Restart managing node if required.
0x01bc8266 EPL: Telegram error detected (CRC)	Cause: Faulty Ethernet frames (CRC error) have been detected. Possible causes: A device in the network is not EPL-compliant. EMC interference is too strong. Remedy: Check if a non-EPL-compliant device is in the network (e.g. diagnostics PC). Reduce EMC interference on the network or use an additional shield connection.
Su02 One mains phase is missing [xx.0111.00002]	Cause: A 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: Supply voltage failure detected. Remedy: Check external 24V supply.
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 controller is too high or the fan or its ventilation slots are dirty. Remedy: Check control cabinet temperature. Clean filter. Clean inverter. If required, clean or replace the fan. Provide for sufficient cooling of the device.
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.
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: The maximum current monitoring function has been triggered. 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. From version 15.00.00, this voltage ramp can be set in C00983/2. Remedy: Reduce regenerative load. Use 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”).
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. 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. 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. A cause can also be the use of shielded motor cables longer than 50 m. 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 are used: up to V05.00.00 set C00602 to “0: No Reaction”. From V05.01.00 deactivate earth-fault detection during operation (C01770 to 250 ms). If motor cables > 50 m are used: From V05.01.00 increase filter time for earth-fault detection (C01770).
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 (Imax in motor mode) and C00023 (Imax in 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	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	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).
Id1 Motor data identification error	Cause: During the identification of motor parameters, an error has occurred. Possible causes: Interrupted motor cable. Switched-off power section during the identification. Implausible start parameter settings. Remedy: Check the motor connections and the corresponding plug connector on the device and, if necessary, the motor terminal box. Correct start parameters for the motor parameter identification (motor nameplate data). Ensure stable power supply of the device.
Id3 CINH identification	Cause: The device has detected controller inhibit during the motor data identification. This cancels the identification process. The Lenze setting of the motor data is used. 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	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	Cause: At controller enable, the device has detected that the motor control type set in C00006 cannot control the motor type set. Example: Motor nameplate data for an asynchronous motor have been entered; however, a motor control type for a synchronous motor is set in C00006. Remedy: Enter correct motor nameplate data and set a matching motor control type in C00006: Motor nameplate data asynchronous motor → motor control type must be ASM, SLVC or VFCplus servo control. Motor nameplate data synchronous motor → motor control type must be PSM, SLPSM or VFCplus servo control.
Id8 Speed encoder has not been set	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. Note: The error can only be reset if the settings in C00006 and C00495 match.
oC12 I2xt overload – brake resistor	Cause: Too frequent and too long braking processes. Remedy: Check drive dimensioning.
oC19 Brake resistor – short circuit	Cause: Short circuit at the terminals of the brake resistor. Low-resistance brake resistor. Remedy: Check terminals of the brake resistor. Check brake resistor.
oC11 Clamp operation active	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	Cause: Pole position identification has not been completed successfully. Remedy: Check parameter setting of the pole position identification.
oC13 Maximum current for Fch exceeded	Cause: The device has detected a motor current which exceeds the maximum current limit at permanent switching frequency of the inverter. If a permanent switching frequency inverter is set, a certain limit arises for the maximum current, depending on the setting. If this current limit is exceeded due to a load impulse or overload, an error message is displayed. 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	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. Only during “Closed loop” operation or with vector control (SLVC). Remedy: Observe load requirements. Correct dimensioning or reduce setpoint generation dynamics if necessary. Check Motor control settings.
FC01 Switching frequency reduction	Cause: Load-dependent switching frequency reduction. Remedy: Observe load requirements. Correct dimensioning or reduce setpoint generation dynamics if necessary. Check Motor control settings.
FC02 Maximum speed for Fchop	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. Check Motor control: Determine speed limits.
oC14 Direct-axis current controller limitation	Cause: Direct-axis current controller limitation is active. Remedy: Observe load requirements. Correct dimensioning or reduce setpoint generation dynamics if necessary. Check Motor control settings.
oC15 Cross current controller limitation	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). Check Motor control settings.
oC16 Torque controller limitation	Cause: Actuator limitation according to speed controller. Remedy: Observe load requirements. Correct dimensioning or reduce setpoint generation dynamics if necessary. Check Motor control settings.
FC03 Field controller limitation	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. Check Motor control settings.
oC6 I2xt overload – motor	Cause: Thermal overload of the motor. Only self-ventilated motors can be monitored using the I2xt function. 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	Cause: Motor phase failure – power section. This error message is displayed if 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 and, if necessary, the motor terminal box. Check the trigger threshold (C00599).
Sd10 Speed limit – feedback system 12	Cause: Maximally permissible speed of the feedback system connected to DI1/DI2 reached. Remedy: Reduce speed of the rotation shaft/feedback system. nencoder <= (fmax x 60) / encoder increments (for fmax = 10 kHz)
Sd3 Open circuit HTL 2-fold or 4-fold	Cause: HTL encoder cable interrupted. HTL encoder is defective. Note: May also be caused by a very dynamic acceleration or starting up against a blocked motor shaft (e.g. with a 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.
Sd18 V/f emergency operation	Cause: Error in encoder system. Remedy: Check all available encoder error messages. Perform the troubleshooting measures for these error messages as described in this manual.
An01 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 (C00034/1 = 2). Remedy: Check wiring of the analog X3/A1I input terminal for open circuit. Check minimum current values of the signal sources.
CE04 MCI communication error [xx.0127.00002]	Cause: Communication error with extension module in slot 1. Remedy: Check setting of sync window (C01123) if sync signal source (C01120) is set to “4: MCI”. Eliminate EMC interference. Switch off inverter, correctly plug in the module, switch on the inverter again. Switch mains or restart inverter. Replace module/inverter. Please contact Lenze if the problem occurs again.
CE0F MCI control word [xx.0127.00015]	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 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 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 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. The current CAN error status is displayed in C00345. 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 HeartBeatEvent [xx.0131.00011]	Cause: CAN on board: Cyclic node monitoring. Being a Heartbeat consumer, the device has not received a Heartbeat telegram from Heartbeat producer 1 … 7 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 CAN control word [xx.0131.00015]	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 CAN RPDO1 [xx.0135.00001]	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 CAN RPDO2 [xx.0135.00002]	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 CAN RPDO3 [xx.0135.00003]	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 CAN RPDO4 [xx.0135.00004]	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 Module missing/incompatible [xx.0140.00013]	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. In this case, please contact Lenze.
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. If a memory module has been provided: Check if the memory module has been plugged-in correctly.
PS02 Par. set invalid [xx.0144.00002]	Cause: The parameter set stored in the memory module is invalid. Reasons: Incomplete storage due to voltage failure; Module stems from a device with new firmware or different device type. 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. If parameter set is transferred from higher version to lower version, use “copy parameter set” function. Ensure no functions are used that are unavailable in the older device.
PS03 Par. set device invalid [xx.0144.00003]	Cause: The parameter set saved to the memory module is incompatible to the standard device. E.g. HighLine module plugged into StateLine or version mismatch. Remedy: Observe compatibility when replacing memory modules. OK: StateLine V2.0 to StateLine V3.0. OK: StateLine V2.0 to HighLine V2.0. Not OK: HighLine Vx.x to StateLine Vx.x. Not OK: StateLine V3.0 to StateLine < V3.0. If set is compatible but version is lower, message is only “Information”. Save parameters again to eliminate message. If saving to a higher device version, you can no longer load this set to a lower device version.
PS04 Par. set Mci invalid [xx.0144.00004]	Cause: The parameter set saved to the communication module is incompatible to the standard device (e.g. MCI module parameters do not match plugged module). Remedy: When memory modules are replaced, observe compatibility. Not OK: Profibus V1.0 to EtherCAT V1.0.
PS07 Par. memory module invalid [xx.0144.00007]	Cause: The parameter set saved to the memory module is invalid. Error occurs while loading; plugged module lacks a code or code is incorrect. Remedy: Please contact Lenze.
PS08 Par. device invalid [xx.0144.00008]	Cause: The parameter set in the device is invalid. Error occurs while loading; One code in the device is incorrect. Remedy: Please contact Lenze.
PS09 Par. format invalid [xx.0144.00009]	Cause: The code format is invalid. The error occurs while loading the parameter set. Remedy: Please contact Lenze.
PS10 Memory module binding invalid [xx.0144.00010]	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 Lenze setting loaded [xx.0144.00011]	Cause: Lenze default settings have been loaded. Remedy: No specific remedy listed (Information only).
PS12 Parameter sets loaded [xx.0144.00012]	Cause: Informational message (No Reaction/Info). Remedy: No action required.
PS13 Parameter sets saved [xx.0144.00013]	Cause: Informational message (No Reaction/Info). Remedy: No action required.
dF01 FW updated [xx.0145.00001]	Cause: Informational message (No Reaction/Info). Remedy: No action required.
dF14 SW-HW invalid [xx.0145.00014]	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.
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).
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).
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.
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.