Lenze 9400 highline Servo Drive Fault Codes:
| Fault Code and Meaning | Cause and Remedy |
|---|---|
| 0x00650000 Logbook: Overflow | Cause: Too many events/faults have occurred in a very short time. It was therefore not possible to list all of them in the logbook. Remedy:
|
| 0x00650001 Logbook: Reset (read error) | Cause: The logbook has been reset due to a read error. Remedy:
|
| 0x00650002 Logbook: Reset (version error) | Cause: The logbook has been reset due to a version conflict. Remedy:
|
| 0x00650003 Memory module is missing | Cause: Memory module is defective or not available. Remedy:
|
| 0x00680000 Control card is defect | Cause: Operating system could not identify the control card. Remedy:
|
| 0x00680001 Power section is defect | Cause: Operating system could not identify the power section. Remedy:
|
| 0x00680002 Memory module is defect or missing | Cause: Operating system could not identify the memory module. Remedy:
|
| 0x00680003 Safety module is defect or missing | Cause: Operating system could not identify the safety module. Remedy:
|
| 0x00680004 MXI1: Module changed during operation | Cause: It was tried to plug an extension module into module slot MXI1, which is not “Hot-plug”-able. Remedy:
|
| 0x00680005 MXI2: Module changed during operation | Cause: It was tried to plug an extension module into module slot MXI2, which is not “Hot-plug”-able. Remedy:
|
| 0x00680006 Memory module has been removed | Cause: You have tried to remove or change the memory module during operation. Remedy:
|
| 0x00680007 Safety module has been removed | Cause: You have tried to remove or change the safety module during operation. Remedy:
|
| 0x00680008 Control card is defect | Cause: Operating system could not identify the control card. Remedy:
|
| 0x00680009 Power section is defect | Cause: Operating system could not identify the power section. Remedy:
|
| 0x0068000a MXI1: Module is defect or missing | Cause: Operating system could not identify the extension module in module slot MXI1. Remedy:
|
| 0x0068000b MXI2: Module is defect or missing | Cause: Operating system could not identify the extension module in module slot MXI2. Remedy:
|
| 0x0068000c Memory module is defect or missing | Cause: Operating system could not identify the memory module. Remedy:
|
| 0x0068000d Safety module is defect or missing | Cause: Operating system could not identify the safety module. Remedy:
|
| 0x0068000e Control card incompatible | Cause: The control card is not supported by the operating system. Remedy:
|
| 0x0068000f Power section incompatible | Cause: The power section is not supported by the operating system. Remedy:
|
| 0x00680010 MXI1: Wrong module | Cause: The extension module in module slot MXI1 is not supported by the operating system. Remedy:
|
| 0x00680011 MXI2: Wrong module | Cause: The extension module in module slot MXI2 is not supported by the operating system. Remedy:
|
| 0x00680012 Incorrect memory module | Cause: The memory module is not supported by the operating system. Remedy:
|
| 0x00680013 Incorrect safety module | Cause: The safety module is not supported by the operating system. Remedy:
|
| 0x00680014 Power section was changed | Cause: The power section has been changed since the last mains switching. Remedy:
|
| 0x00680015 MXI1: Module has been changed | Cause: The extension module in module slot MXI1 has been changed since the last mains switching. Remedy:
|
| 0x00680016 MXI2: Module has been changed | Cause: The extension module in module slot MXI2 has been changed since the last mains switching. Remedy:
|
| 0x00680017 Memory module has been changed | Cause: The memory module has been changed since the last mains switching. Remedy:
|
| 0x00680018 Safety module has been changed | Cause: The safety module has been changed since the last mains switching. Remedy:
|
| 0x00680019 Combination MXI1/MXI2 not possible | Cause: Extension modules which are not supported in this combination are plugged into module slots MXI1 & MXI2. Remedy:
|
| 0x0068001a Firmware has been changed | Cause: The firmware of the operating system has been updated. Remedy:
|
| 0x0068001b Electronic nameplate: Communication error | Cause: Communication with the electronic nameplate is interrupted, the data could not be read. Remedy:
|
| 0x0068001c Memory module: Faulty file system | Cause: Memory module is plugged in incorrectly or is defective. Remedy:
|
| 0x0068001d Electronic nameplate: Checksum error | Cause: The checksum of the electronic nameplate is defective. Remedy:
|
| 0x0068001e Firmware is incompatible with control card | Cause: Firmware is not compatible with the hardware. Remedy:
|
| 0x0068001f Combination memory module/device not possible | Cause: The memory module used is not supported by the controller according to the license model. Remedy:
|
| 0x00680020 Combination of module in MXI1/device not possible | Cause: The extension module in module slot MXI1 is not supported by the controller. Remedy:
|
| 0x00680021 Combination of module in MXI2/device not possible | Cause: The extension module in module slot MXI2 is not supported by the controller. Remedy:
|
| 0x00680022 Real-time clock is defective | Cause: Device error: The clock integrated in the MM440 memory module is defective. Remedy:
|
| 0x00680023 Real-time clock: Change battery | Cause: The battery in the clock integrated in the MM440 memory module is low. The clock is expected to fail soon. Remedy:
|
| 0x00680024 Real-time clock: Battery empty, time lost | Cause: The battery integrated in the clock in the MM440 memory module is empty. The clock has been reset to its initial value (01.01.1970 – 00:00:00 o’clock). Remedy:
|
| 0x00690000 Code refresh | Cause: Serious device error or component failure. Remedy:
|
| 0x00690001 Internal error (memory area – logbook) | Cause: Serious device error or component failure. Remedy:
|
| 0x00690002 Internal error (LDS instance data) | Cause: Serious device error or component failure. Remedy:
|
| 0x00690003 Internal error (LDS tasks) | Cause: Serious device error or component failure. Remedy:
|
| 0x00690004 Internal error (storage blocks) | Cause: Serious device error or component failure. Remedy:
|
| 0x00690005 Internal error (task queue) | Cause: Serious device error or component failure. Remedy:
|
| 0x00690006 Internal error (message memory) | Cause: Serious device error or component failure. Remedy:
|
| 0x00690007 Internal error (message queue) | Cause: Serious device error or component failure. Remedy:
|
| 0x00690008 Internal error (name data base) | Cause: Serious device error or component failure. Remedy:
|
| 0x00690009 Internal error (event mechanism) | Cause: Serious device error or component failure. Remedy:
|
| 0x0069000a Internal error (event mechanism) | Cause: Serious device error or component failure. Remedy:
|
| 0x0069000b Internal error (semaphores) | Cause: Serious device error or component failure. Remedy:
|
| 0x0069000c Internal error (semaphores) | Cause: Serious device error or component failure. Remedy:
|
| 0x0069000d Internal error (file system lifetime) | Cause: The maximum number of permissible writing cycles has been reached for the memory module. Remedy:
|
| 0x006a0000 General error in the application | Cause: General application error. Remedy:
|
| 0x006a0001 Faulty program download | Cause: Faulty transmission of the application to the controller (checksum error). Remedy:
|
| 0x006a0002 Fault during the update of the inputs and outputs | Cause: Internal error. Remedy:
|
| 0x006a0003 New application loaded | Cause: Application has been changed by transmission from Engineer or loading from the memory module. Remedy:
|
| 0x006a0004 ApplicationTask: Overflow | Cause: Program runtime in Application task is too high. Remedy:
|
| 0x006a0005 UserTask: Overflow | Cause: Program runtime in user task is too high. Remedy:
|
| 0x006a0006 IdleTask: Overflow | Cause: Program runtime in idle task is too high. Remedy:
|
| 0x006a000d Runtime error | Cause: A runtime error has occurred in the application. The application processing has been interrupted. Remedy:
|
| 0x006a000e Application has stopped | Cause: The application has been stopped using the device command C00002=”32″. All user tasks are stopped. Remedy:
|
| 0x006a000f Breakpoint reached | Cause: The application has reached a set breakpoint and the user task with the breakpoint has stopped. Remedy:
|
| 0x006a0010 Faulty application parameter | Cause: An invalid parameter description is available. Remedy:
|
| 0x006a0011 Division by zero | Cause: An impermissible division by zero occurred in the application. The division has been intercepted and the divisor was replaced by the value “1”. Remedy:
|
| 0x006a0012 Pointer access in impermissible memory area | Cause: An invalid pointer access to a protected area occurred in the application. Remedy:
|
| 0x006a0013 Application has started | Cause: The application in the controller has been started. Remedy:
|
| 0x006a0014 Application has stopped | Cause: The application in the controller has been stopped. Remedy:
|
| 0x006a0015 PDO mapping (MXI1): Faulty configuration | Cause: CANopen communication module in MXI1: Incorrectly configured process data mapping. – The corresponding PDO channel is not installed. – Communication module does not support PDO mapping. – Mapping information is faulty. Remedy:
|
| 0x006a0016 PDO mapping (MXI2): Faulty configuration | Cause: CANopen communication module in MXI2: Incorrectly configured process data mapping. – The corresponding PDO channel is not installed. – Communication module does not support PDO mapping. – Mapping information is faulty. Remedy:
|
| 0x006a0017 Fault in the control configuration | Cause: An invalid control configuration has occurred. Remedy:
|
| 0x006a001a Retain memory of the application faulty | Cause: During reading or saving the retain memory of the application a fault has occurred. Remedy:
|
| 0x006a001b Watchdog cycle is greater than task cycle | Cause: An application has been downloaded with the highest priority task having a smaller cycle than the watchdog cycle, or the watchdog is deactivated. Remedy:
|
| 0x006f0000 Control card: Supply voltage (24 V DC) too low | Cause: External 24 V supply voltage of the control card is lower than 18 V. Remedy:
|
| 0x00720000 Read error service register | Cause: During reading or writing the service register a fault has occurred. Remedy:
|
| 0x00750000 External error | Cause: The drive interface has activated the error message “External error”. The input DI_bSetExternError has been set to TRUE. Remedy:
|
| 0x00750001 Controller enabled | Cause: The controller is enabled and has the “Operation” state. Remedy:
|
| 0x00750003 Controller in STO state | Cause: The controller has received the “Safe torque off (STO)” request by the safety module and is now in the “Safe torque off active” device state. Remedy:
|
| 0x00750005 Controller: Pulse inhibit is active | Cause: The pulse inhibit is active in the controller. Remedy:
|
| 0x00750006 PLC configuration invalid | Cause: An invalid control configuration has occurred. Remedy:
|
| 0x00770000 Heatsink: Temperature > C00122 | Cause: Heatsink temperature higher than variable temperature limit (C00122). – Ambient controller temperature too high. – Dirty fan or ventilation slots. – Value set under C00122 is too low. Remedy:
|
| 0x00770001 Heatsink: Overtemperature | Cause: Heatsink temperature higher than fixed temperature limit (90 °C). – Ambient controller temperature too high. – Dirty fan or ventilation slots. Remedy:
|
| 0x00770002 Motor: Temperature > C00121 | Cause: Motor temperature higher than variable temperature limit (C00121). – Motor too hot (high currents or long accel). – No PTC connected. – Value set under C00121 is too low. Remedy:
|
| 0x00770003 Motor: Overtemperature | Cause: Motor temperature higher than fixed temperature limit (150 °C). – Motor too hot (high currents or long accel). – No PTC connected. Remedy:
|
| 0x00770008 CPU: Temperature > C00126 | Cause: CPU temperature higher than variable temperature limit (C00126). – Ambient controller temperature too high. – Dirty fan or ventilation slots. – Value set under C00126 is too low. Remedy:
|
| 0x00770009 CPU: Overtemperature | Cause: CPU temperature higher than fixed limit temperature (85 °C). • Ambient controller temperature too high. • Dirty fan or ventilation slots. Remedy:
|
| 0x0077000a Heatsink: Thermal detector is defect | Cause: Encoder for heatsink temperature supplies undefined values. Remedy:
|
| 0x0077000b Inside the device: Thermal detector is defective | Cause: Encoder for interior temperature supplies undefined values. Remedy:
|
| 0x0077000c Motor: Thermal detector is defect | Cause: The signals of the connected encoder for the motor temperature detection (resolver at X7 or encoder at X8) are outside the defined operating range. Remedy:
|
| 0x0077000d DC-bus capacitor: Thermal detector is defect | Cause: Encoder for capacitor temperature supplies undefined values. Remedy:
|
| 0x0077000e CPU: Thermal detector is defect | Cause: Encoder for CPU temperature supplies undefined values. Remedy:
|
| 0x0077000f Motor: PTC has triggered | Cause: The motor temperature detected via terminals T1/T2 is too high. • High/frequent acceleration processes. • Increased ambient conditions. • Lacking cooling. • Open circuit of supply cables. Remedy:
|
| 0x00770010 Heatsink: Fan is defect | Cause: Speed of heatsink fan too low, e.g. due to dirt. Remedy:
|
| 0x00770011 Inside the device: Fan is defective | Cause: Speed of internal fan is too low, e.g. due to dirt. Remedy:
|
| 0x00780000 Device utilisation Ixt > C00123 | Cause: Frequent and too long acceleration processes with overcurrent > C00123. Remedy:
|
| 0x00780001 Device utilisation Ixt > 100 % | Cause: Frequent and too long acceleration processes with overcurrent. Remedy:
|
| 0x00780002 Motor load I²xt > C00127 | Cause: Motor is thermally overloaded, e.g. due to impermissible continuous current or frequent/long acceleration. Remedy:
|
| 0x00780003 Motor load I²xt > C00120 | Cause: Motor is thermally overloaded, e.g. due to impermissible continuous current or frequent/long acceleration. Remedy:
|
| 0x00780004 Control card is defect (UB24) | Cause: Device error. Remedy:
|
| 0x00780005 Control card is defect (VCC15) | Cause: Device error. Remedy:
|
| 0x00780006 Control card is defect (UB8) | Cause: Device error. Remedy:
|
| 0x00780007 Control card is defect (VCC15 neg.) | Cause: Device error. Remedy:
|
| 0x00780008 Control card is defect (UB18 neg.) | Cause: Device error. Remedy:
|
| 0x00780009 Control card is defect (VCC5) | Cause: Device error. Remedy:
|
| 0x0078000a Electronic nameplate: Data are incompatible | Cause: The connected motor with feedback is not supported by the controller firmware. Remedy:
|
| 0x00790000 Device command transferred incorrectly | Cause: Internal error. Remedy:
|
| 0x00790001 Time error – controller interface | Cause: Internal error. Remedy:
|
| 0x00790002 Violation of time slice | Cause: Internal error. Remedy:
|
| 0x007b0001 Motor: Calculated motor impedance unrealistic | Cause: Faulty motor parameterisation. Remedy:
|
| 0x007b0002 Motor: Calculated mutual inductance unrealistic | Cause: Faulty motor parameterisation. Remedy:
|
| 0x007b0003 Motor data are inconsistent | Cause: Faulty motor parameterisation. Remedy:
|
| 0x007b0004 Motor: Phase resistance too high | Cause: Faulty motor parameterisation. Remedy:
|
| 0x007b0006 Motor: Device current too low for rated magnetisation | Cause: Controller current is too low for rated magnetisation, i.e. the controller cannot energise the motor sufficiently. Remedy:
|
| 0x007b0007 Motor: Rated current < rated magnetising current | Cause: Faulty motor parameterisation. Remedy:
|
| 0x007b0009 Motor: Calculated rotor resistance unrealistic | Cause: Faulty motor parameterisation. Remedy:
|
| 0x007b000a Motor: Calculated mutual inductance unrealistic | Cause: Faulty motor parameterisation. Remedy:
|
| 0x007b000b Motor: Calculated e. m. f. factor unrealistic | Cause: Faulty motor parameterisation. Remedy:
|
| 0x007b000c Motor: Calculated rotor time constant unrealistic | Cause: Faulty motor parameterisation. Remedy:
|
| 0x007b000d Motor: Calculated flux factor unrealistic | Cause: Faulty motor parameterisation. Remedy:
|
| 0x007b000e DC bus overvoltage | Cause: Due to a too high braking energy, the DC-bus voltage exceeds the overvoltage threshold which results from the mains voltage setting in C00173. Remedy:
|
| 0x007b000f DC bus undervoltage | Cause: DC bus voltage is lower than the undervoltage threshold resulting from the mains setting under C00173. Remedy:
|
| 0x007b0010 Overcurrent detected | Cause: • Short circuit/earth fault in motor cable. • Excessive capacitive charging current in the motor cable. Remedy:
|
| 0x007b0011 Earth fault detected | Cause: • Earth fault in motor cable. • Excessive capacitive charging current in the motor cable. Remedy:
|
| 0x007b0012 Actual speed value outside the tolerance (C00576) | Cause: Difference between actual and setpoint speed is too big. Remedy:
|
| 0x007b0013 Motor control: Task overflow | Cause: Internal error (motor control). Remedy:
|
| 0x007b0014 Internal communication error (host MCTRL) | Cause: Internal error (motor control). Remedy:
|
| 0x007b0017 Motor data are inconsistent | Cause: Faulty motor parameterisation. Remedy:
|
| 0x007b0018 Resolver: Open circuit | Cause: • Resolver cable interrupted. • Resolver defective. Remedy:
|
| 0x007b0019 Motor: Calculated leakage inductance unrealistic | Cause: Faulty motor parameterisation. Remedy:
|
| 0x007b001a Absolute value encoder: Communication error | Cause: Absolute value encoder does not send any data or a digital readout has been activated while the machine is coasting down. Remedy:
|
| 0x007b001b (27) Encoder: Open circuit | Cause:
Remedy:
|
| 0x007b001c (28) Brake transistor: Ixt overload | Cause: Too frequent and too long braking processes. Remedy: Check drive dimensioning. |
| 0x007b001d (29) Brake resistor: I²xt overload | Cause: Too frequent and too long braking processes. Remedy:
|
| 0x007b001e (30) Motor: Actual current value > C00620 | Cause: The instantaneous value of the motor current has exceeded the value set in C00620. Remedy:
|
| 0x007b001f (31) Resolver: Calculated acceleration unrealistic | Cause: Resolver evaluation faulty (implausible acceleration at the resolver). Remedy: Check structure. |
| 0x007b0020 (32) Motor: Actual speed value > C00596 | Cause: Threshold for speed monitoring set in C00596 has been exceeded. Remedy: Check drive dimensioning. |
| 0x007b0021 (33) Brake transistor: Overcurrent | Cause: Brake chopper short circuit/earth fault detected. Remedy: Check brake chopper cable and brake resistor. |
| 0x007b0023 (35) Position encoder: Module selected in C00490 not available | Cause: The position encoder selected under C00490 has not been recognised. Remedy:
|
| 0x007b0024 (36) Motor encoder: Module selected in C00495 not available | Cause: The motor encoder selected under C00495 has not been recognised. Remedy:
|
| 0x007b0025 (37) Motor temperature: Module selected in C01193 not available | Cause: The module for temperature feedback selected in C01193 has not been recognised. Remedy:
|
| 0x007b0026 (38) EnDat encoder: Lamp error | Cause: EnDat encoder defective. Remedy: Check EnDat encoder. |
| 0x007b0027 (39) EnDat encoder: Signal error | Cause: EnDat encoder defective. Remedy: Check EnDat encoder. |
| 0x007b0028 (40) EnDat encoder: Position error | Cause: EnDat encoder defective. Remedy: Check EnDat encoder. |
| 0x007b0029 (41) EnDat encoder: Overvoltage | Cause: EnDat encoder defective. Remedy: Check EnDat encoder. |
| 0x007b002a (42) EnDat encoder: Undervoltage | Cause: EnDat encoder defective. Remedy: Check EnDat encoder. |
| 0x007b002b (43) EnDat encoder: Overcurrent | Cause: EnDat encoder defective. Remedy: Check EnDat encoder. |
| 0x007b002c (44) EnDat encoder: Battery empty | Cause: EnDat encoder defective. Remedy: Check EnDat encoder. |
| 0x007b002d (45) Failure of motor phase U | Cause: U phase interruption of motor cable. Remedy:
|
| 0x007b002e (46) Failure of motor phase V | Cause: V phase interruption of the motor cable. Remedy:
|
| 0x007b002f (47) Failure of motor phase W | Cause: W phase interruption of the motor cable. Remedy:
|
| 0x007b0030 (48) Electronic nameplate: Data loaded | Cause: New electronic nameplate (ENP) has been found. Remedy: (Information only) |
| 0x007b0031 (49) Electronic nameplate: Not found | Cause: Electronic nameplate (ENP) is not available. Remedy: (Information only) |
| 0x007b0032 (50) Electronic nameplate: Encoder protocol unknown | Cause: The connected motor with feedback is not supported by the controller firmware. Remedy: Check drive dimensioning. |
| 0x007b0033 (51) Electronic nameplate: Encoder signal unknown | Cause: The connected motor with feedback is not supported by the controller firmware. Remedy: Check drive dimensioning. |
| 0x007b0034 (52) Internal communication error (DMA) | Cause: Internal error. Remedy: Please contact Lenze. |
| 0x007b0035 (53) Controller: Overload during acceleration phases | Cause: Frequent or too long acceleration processes. Remedy:
|
| 0x007b0036 (54) Internal communication error (MCTRL host) | Cause: Internal error. Remedy: Please contact Lenze. |
| 0x007b0037 (55) PLC configuration invalid | Cause: An invalid control configuration has occurred. Remedy: Load a different application. |
| 0x007b0038 (56) Motor parameter identification was cancelled | Cause: The motor current during identification was too high. Remedy:
|
| 0x007b0039 (57) Electronic nameplate: Data outside the parameter limits | Cause: The motor parameters of the electronic nameplate are outside of the limit values of the controller and therefore cannot be accepted. Remedy: Consultation with Lenze required. |
| 0x007b003a (58) Hiperface encoder: Transmission error | Cause:
Remedy:
|
| 0x007b003b (59) Hiperface encoder: Command error | Cause:
Remedy:
|
| 0x007b003c (60) Hiperface encoder: Unknown encoder | Cause: Encoder is not supported by the controller firmware. Remedy:
|
| 0x007b003d (61) Hiperface encoder: Position initialisation error | Cause: A digital readout of the absolute encoder is only possible at standstill. Remedy: Prevent coasting of the machine while the absolute encoder is read out. |
| 0x007b003e (62) Encoder monitoring: Pulse deviation detected | Cause:
Remedy:
|
| 0x007b003f (63) Failure of a mains phase | Cause: Missing mains phase. (Note: only available for devices ≥ 75 kW). Remedy: Check mains connection. |
| 0x007b0040 (64) Brake chopper: Ixt > C00570 | Cause: Frequent and too long braking. Remedy:
|
| 0x007b0041 (65) Brake resistor: I2t > C00572 | Cause: Frequent and too long braking. Remedy:
|
| 0x007b0042 (66) Power section is defect | Cause: Device error. Remedy:
|
| 0x007b0047 (71) Controller: Clamp operation | Cause: Actual motor current is higher than the maximum device current (C00789). Remedy:
|
| 0x007b004a (74) Pole position recognition cancelled | Cause: An error occurred during the pole position identification. The pole position identification could not be completed successfully. Remedy:
|
| 0x007b004c (76) Motor switched off | Cause: Interruption of several motor cable phases. Remedy: Check cabling between the controller and motor. |
| 0x007b004e (78) EnDat encoder: Transmission error | Cause:
Remedy:
|
| 0x007b004f EnDat encoder: Command error | Cause:
Note: This information is always supplied together with the “I/O error – encoder communication” error message and is entered in the logbook even if the encoder monitoring is deactivated (C00580). Remedy:
|
| 0x007b0050 EnDat encoder: Position initialisation error | Cause: A digital readout of the absolute encoder is only possible at standstill. The readout is activated by the following actions:
Remedy: Prevent coasting of the machine while the absolute encoder is read out. |
| 0x007c0000 Memory module: File system has been formatted | Cause: File system of the memory module has been formatted. Remedy: – (Information only) |
| 0x007c0001 Memory module: File system has been restored | Cause: File system of the memory module has been restored. Remedy: – (Information only) |
| 0x007d0000 Analog input 1: Master current < 4 mA | Cause: Master current is in the impermissible range -4 … +4 mA, e.g. due to a cable break or a defective master current value encoder.
Remedy: Remove cable break. |
| 0x007d0001 PLC configuration invalid | Cause: An invalid control configuration has occurred. Remedy: Load a different application. |
| 0x007f0002 Communication error between device and device module | Cause: Communication between the controller and extension module is interrupted, e.g. due to disturbances in the ambience (EMC), defective hardware, or loose contact.
Remedy:
|
| 0x007f0003 Communication with module in MXI1 interrupted | Cause: Communication between the controller and the extension module in module slot MXI1 cannot be established. Remedy:
|
| 0x007f0004 Communication with module in MXI2 interrupted | Cause: Communication between the controller and the extension module in module slot MXI2 cannot be established. Remedy:
|
| 0x00830000 CAN on board: Bus off | Cause: CAN on board: “Bus-Off” state
Remedy:
|
| 0x00830001 CAN on board: Invalid node address 0 | Cause: CAN on board: initialisation error
Note: Instead of the impermissible node address 0, node address 1 is used. Remedy:
|
| 0x00830002 CAN on board: Basic configuration invalid | Cause: CAN on board: configuration error
Remedy:
|
| 0x00840000 … 0x0084001f CAN on board: Heartbeat error index 1 … 32 | Cause: CAN on board: Cyclic node monitoring
Remedy:
Tip: Save the current parameter set before mains switching and restart of the controller (C00002=”11″). |
| 0x00840020 CAN on board: Lifeguarding error | Cause: CAN on board: Cyclic node monitoring
Remedy: Select a different Lifeguarding monitoring time or switch off monitoring. |
| 0x00840021 CAN on board: Faulty NMT slave configuration | Cause: CAN on board: A configuration error has occurred in the network management of the CAN slave.
Remedy:
|
| 0x00850000 CAN on board: Faulty emergency configuration | Cause: CAN on board: CAN emergency configuration is faulty.
Remedy:
|
| 0x00860000 … 0x0086001f CAN on board: Node guarding error 1 … 32 | Cause: CAN on board: Cyclic node monitoring
Remedy:
Tip: Save the current parameter set before mains switching and restart of the controller (C00002=”11″). |
| 0x00860020 CAN on board: Faulty NMT master configuration | Cause: CAN on board: A configuration error has occurred in the network management of the CAN master.
Remedy:
|
| 0x00870000 CAN on board RPDO1: Telegram not received or faulty | Cause: CAN on board: CAN-IN 1 error
Remedy:
|
| 0x00870001 CAN on board RPDO2: Telegram not received or faulty | Cause: CAN on board: CAN-IN 2 error
Remedy:
|
| 0x00870002 CAN on board RPDO3: Telegram not received or faulty | Cause: CAN on board: CAN-IN 3 error
Remedy:
|
| 0x00870003 CAN on board RPDO4: Telegram not received or faulty | Cause: CAN on board: CAN-IN 4 error
Remedy:
|
| 0x00870008 CAN on board PDO manager: Faulty configuration | Cause: CAN on board: CAN-PDO configuration error
Remedy:
|
| 0x00880000 CAN on board SDO server: Faulty configuration | Cause: CAN on board: A configuration error has occurred in the CAN SDO server.
Remedy:
|
| 0x00890000 CAN on board SDO client: Faulty configuration | Cause: CAN on board: A configuration error has occurred in the CAN SDO client.
Remedy:
|
| 0x008c0000 File ProjectSelection.dat defect | Cause: Internal error Remedy: Reformat memory module (C00002=”1030″) and repeat project download. |
| 0x008c0001 File ProjectList.dat defect | Cause: Internal error Remedy: Reformat memory module (C00002=”1030″) and repeat project download. |
| 0x008c0002 File DeviceCFG.dat defect | Cause: Internal error Remedy: Reformat memory module (C00002=”1030″) and repeat project download. |
| 0x008c0003 File ProjectSelection.dat is missing | Cause: Internal error Remedy: Reformat memory module (C00002=”1030″) and repeat project download. |
| 0x008c0004 File ProjectList.dat is missing | Cause: Internal error Remedy: Reformat memory module (C00002=”1030″) and repeat project download. |
| 0x008c0005 File DeviceCFG.dat is missing | Cause: Internal error Remedy: Reformat memory module (C00002=”1030″) and repeat project download. |
| 0x008c0006 File ProjectSelection.dat invalid | Cause: Internal error Remedy: Reformat memory module (C00002=”1030″) and repeat project download. |
| 0x008c0007 File ProjectList.dat invalid | Cause: Internal error Remedy: Reformat memory module (C00002=”1030″) and repeat project download. |
| 0x008c0008 File DeviceCFG.dat invalid | Cause: Internal error Remedy: Reformat memory module (C00002=”1030″) and repeat project download. |
| 0x008c0009 Project is not loaded | Cause: Application could not be loaded because of a file error. Remedy: Load new or different application. |
| 0x008c000a Project is not available | Cause: Application not available. Remedy:
|
| 0x008c000b Required licence missing | Cause: Memory module could not be initialised. Remedy: Two possibilities:
|
| 0x008c000c Application and device are incompatible | Cause: Application is incompatible with the controller. Remedy:
|
| 0x008c000d MXI1: Module is missing or incompatible | Cause: Extension module in module slot MXI1 is incompatible with the application. Remedy: Use extension module supported by the application. |
| 0x008c000e MXI2: Module is missing or incompatible | Cause: Extension module in module slot MXI2 is incompatible with the application. Remedy: Use extension module supported by the application. |
| 0x008c000f MXI1: PROFIBUS module is missing or incompatible | Cause: E94AYCPM communication module (PROFIBUS) in module slot MXI1 is incompatible with the application. Remedy: Use communication module supported by the application. |
| 0x008c0010 MXI2: PROFIBUS module is missing or incompatible | Cause: E94AYCPM communication module (PROFIBUS) in module slot MXI2 is incompatible with the application. Remedy: Use communication module supported by the application. |
| 0x008c0011 MXI1: Ethernet module is missing or incompatible | Cause: E94AYCEN communication module (Ethernet) in module slot MXI1 is incompatible with the application. Remedy: Use communication module supported by the application. |
| 0x008c0012 MXI2: Ethernet module is missing or incompatible | Cause: E94AYCEN communication module (Ethernet) in module slot MXI2 is incompatible with the application. Remedy: Use communication module supported by the application. |
| 0x008c0013 MXI1: Digital frequency module is missing or incompatible | Cause: Digital frequency extension module in module slot MXI1 is incompatible with the application. Remedy: Use extension module supported by the application. |
| 0x008c0014 MXI2: Digital frequency module is missing or incompatible | Cause: Digital frequency extension module in module slot MXI2 is incompatible with the application. Remedy: Use extension module supported by the application. |
| 0x008c0015 MXI1: ICM module is missing or incompatible | Cause: ICM extension module in module slot MXI1 is incompatible with the application. Remedy: Use extension module supported by the application. |
| 0x008c0016 MXI2: ICM module is missing or incompatible | Cause: ICM extension module in module slot MXI2 is incompatible with the application. Remedy: Use extension module supported by the application. |
| 0x008c0017 MXI1: CAN module is missing or incompatible | Cause: CANopen communication module in module slot MXI1 is incompatible with the application. Remedy: Use communication module supported by the application. |
| 0x008c0018 MXI2: CAN module is missing or incompatible | Cause: CANopen communication module in module slot MXI2 is incompatible with the application. Remedy: Use communication module supported by the application. |
| 0x008c001a ConnectTable active | Cause: The application is provided with a so-called connection table, i. e. connections can be altered “online” in the function block editor without having to carry out a new complete download. Remedy: – (Information only) |
| 0x008c001d Internal error (CRC application) | Cause:
Remedy: Transmit the application to the controller again. |
| 0x008c001e Storage capacity for user parameters exceeded | Cause: Due to the creation of too many user parameters within the application, the storage capacity available on the memory module has been exceeded. User parameters are produced directly by manual creation or indirectly by the insertion of function blocks. Remedy:
Then the current utilisation of the memory can be assessed using code C02112. If 100 % is displayed, this corresponds to the maximum utilisation for an executable application. |
| 0x00900000 Parameter set faulty | Cause: Parameter set is invalid. Remedy: Transfer parameter set from Engineer to the controller and save with C00002=”11″. |
| 0x00900001 Lenze setting loaded | Cause: Lenze setting has been loaded. Remedy: – (Information only) |
| 0x00900002 Parameter set saved | Cause: Parameter set has been saved. Remedy: – (Information only) |
| 0x00900003 Parameter set loaded | Cause: Parameter set has been loaded. Remedy: – (Information only) |
| 0x00900004 Loading of Lenze setting failed | Cause: Lenze setting of a parameter is not within the valid limits. Remedy: Eliminate error in the application and retransfer application to controller. |
| 0x00900005 Parameter set restored | Cause: An error has occurred while loading the selected parameter set. Remedy: Transfer parameter set from Engineer to the controller and save with C00002=”11″. |
| 0x00900006 Saving of parameters failed | Cause: An error has occurred while saving the current parameter set. Remedy: Use a different memory module. |
| 0x00900007 Parameter set: Version conflict | Cause: The parameter set version on the memory module is not compatible with the firmware of the controller. Remedy: Transfer parameter set from Engineer to the controller and save with C00002=”11″. |
| 0x00900008 Code number duplicated | Cause: Code number of the operating system has been assigned to the application. Remedy: Eliminate error in the application and retransfer application to controller. |
| 0x00900009 Parameter set: Type of standard device has been changed | Cause: The firmware has loaded a parameter set the type code of which does not correspond to the type code of the controller. Remedy: Load a suitable parameter set. |
| 0x0090000a No parameters for module in MXI1 | Cause: The parameter set contains no parameters for the module inserted in MXI1. Remedy: Integrate the module inserted in MXI1 into the Engineer project and then retransmit the parameter set to the controller. |
| 0x0090000b No parameters for module in MXI2 | Cause: The parameter set contains no parameters for the module inserted in MXI2. Remedy: Integrate the module inserted in MXI2 into the Engineer project and then retransmit the parameter set to the controller. |
| 0x0090000c Disconnection in the case of par. storage | Cause: The supply voltage has failed before the saving of the parameter set could be completed. In the case of a device replacement/firmware update, the parameter set can no longer be established automatically. Remedy: Save the start parameters again, and in doing this, ensure that the supply voltage is applied until the saving process has been completed. Afterwards acknowledge the error message with “Reset error”. |
| 0x00910000 Mains voltage is switched on | Cause: Mains voltage has been switched on. Remedy: – (Information only) |
| 0x00910001 Mains voltage is switched off | Cause: Mains voltage has been switched off. Remedy: – (Information only) |
| 0x00910002 No heartbeat signal detected | Cause: Internal error Remedy: If the error occurs frequently, please contact Lenze. |
| 0x00910003 Heartbeat not periodic | Cause: Internal error Remedy: If the error occurs frequently, please contact Lenze. |
| 0x00910004 Internal error: See C00180 | Cause: Internal error Remedy: If the error occurs frequently, please contact Lenze. |
| 0x00910005 Internal error: See C00180 | Cause: Internal error Remedy: Consultation with Lenze required. |
| 0x00910006 Internal error: See C00180 | Cause: Divisor of division was “0”. Remedy: Replace application. |
| 0x00910008 Internal error: See C00180 | Cause: Internal error Remedy: If the error occurs frequently, please contact Lenze. |
| 0x00910009 Internal error: See C00180 | Cause: Internal error Remedy: If the error occurs frequently, please contact Lenze. |
| 0x0091000a System task 1: Task overflow | Cause: System overload. Remedy: Consultation with Lenze required. |
| 0x0091000b System task 2: Task overflow | Cause: System overload. Remedy: Consultation with Lenze required. |
| 0x0091000c System task 3: Task overflow | Cause: System overload. Remedy: Consultation with Lenze required. |
| 0x0091000d System task: Task overflow | Cause: System overload. Remedy: Consultation with Lenze required. |
| 0x0091000e Communication task: Standstill > 3 s | Cause: Service data communication within the system (SDO communication of all bus systems connected) has caused an overload of service data processing. Due to this, the monitoring interval of the processing task has been violated. PDO communication is not affected by this overload. Remedy: Reduce system load.
For systems frequently affected by this type of overload, the error response can be changed to warning via code C01230 in order to increase the drive availability. |
| 0x0091000f Cyclic task: Standstill > 60 s | Cause: System overload or CRC check task crash. Remedy: Reduce system load.
|
| 0x00910010 Position value faulty | Cause: Internal error Remedy: If the error occurs frequently, please contact Lenze. |
| 0x00910011 Error during initialisation | Cause: Internal error Remedy: If the error occurs frequently, please contact Lenze. |
| 0x00910012 Block function in wrong MEC task | Cause: Internal error Remedy: If the error occurs frequently, please contact Lenze. |
| 0x00920000 Safety module: Incompatible with setting in C00214 | Cause: The controller has detected a safety module which does not match the setting under C00214. Remedy: Change setting under C00214 or use a suitable safety module.
|
| 0x00920001 Communication with safety module interrupted | Cause: It is not possible to establish communication between the controller and safety module. Remedy:
|
| 0x00990000 DFIN (MXI1): Track error A-/A | Cause: Digital frequency extension module in MXI1: Interruption (open circuit) of the signal cable for track A. Remedy:
|
| 0x00990001 DFIN (MXI1): Track error B-/B | Cause: Digital frequency extension module in MXI1: Interruption (open circuit) of the signal cable for track B. Remedy:
|
| 0x00990002 DFIN (MXI1): Track error Z-/Z | Cause: Digital frequency extension module in MXI1: Interruption (open circuit) of the signal cable for track Z. Remedy:
|
| 0x00990003 DFIN (MXI1): Signal error enable/lamp control | Cause: Digital frequency extension module in MXI1: Interruption (open circuit) of the signal cable for the “Enable” signal or no “Enable” signal available. Remedy:
|
| 0x00990004 DFIN (MXI1): Supply cannot be corrected anymore | Cause: Digital frequency extension module in MXI1: The encoder voltage controlled by the digital frequency input has reached the voltage limit. Remedy: Check encoder. |
| 0x00990005 DFOUT (MXI1): Maximum frequency reached | Cause: Digital frequency extension module in MXI1: Limit frequency at the digital frequency output reached (limit value set in C013053). Remedy: Check limit value set. |
| 0x009d0000 CAN module (MXI1): Bus off | Cause: CANopen communication module in MXI1: “Bus-off” state.
Remedy:
|
| 0x009d0001 CAN module (MXI1): Invalid node address 0 | Cause: CANopen communication module in MXI1: Initialisation error. The hardware allocation of the node address was selected via DIP switches, and the DIP switches are all on zero. Remedy:
|
| 0x009d0002 CAN module (MXI1): Basic configuration invalid | Cause: CANopen communication module in MXI1: Configuration error.
Remedy:
|
| 0x009e0000 … 0x009e001f CAN module (MXI1): Heartbeat error index 1 … 32 | Cause: CANopen communication module in MXI1: Cyclic node monitoring. Node station has not received a heartbeat telegram from node 1…32 within defined time. Remedy:
|
| 0x009e0020 CAN module (MXI1): Lifeguarding error | Cause: CANopen communication module in MXI1: Cyclic node monitoring. Maximum time between two node guarding telegrams from the master has been exceeded. Remedy: Select a different Lifeguarding monitoring time or switch off monitoring. |
| 0x009e0021 CAN module (MXI1): Faulty NMT slave configuration | Cause: CANopen communication module in MXI1: Configuration error in network management of CAN slave.
Remedy:
|
| 0x009f0000 CAN module (MXI1): Faulty emergency configuration | Cause: CANopen communication module in MXI1: CAN emergency configuration is faulty (Faulty download or Invalid settings). Remedy:
|
| 0x00a00000 … 0x00a0001f CAN module (MXI1): Node guarding error 1 … 32 | Cause: CANopen communication module in MXI1: Cyclic node monitoring. CAN master has not received a response to a node guarding telegram from node 1…32 within defined time. Remedy:
|
| 0x00a00020 CAN module (MXI1): Faulty NMT master configuration | Cause: CANopen communication module in MXI1: Configuration error in network management of CAN master.
Remedy:
|
| 0x00a10000 CAN module (MXI1) RPDO1: Telegram not received or faulty | Cause: CANopen communication module in MXI1: CAN-IN 1 error.
Remedy:
|
| 0x00a10001 CAN module (MXI1) RPDO2: Telegram not received or faulty | Cause: CANopen communication module in MXI1: CAN-IN 2 error. Remedy:
|
| 0x00a10002 CAN module (MXI1) RPDO3: Telegram not received or faulty | Cause: CANopen communication module in MXI1: CAN-IN 3 error. Remedy:
|
| 0x00a10003 CAN module (MXI1) RPDO4: Telegram not received or faulty | Cause: CANopen communication module in MXI1: CAN-IN 4 error. Remedy:
|
| 0x00a10004 CAN module (MXI1) RPDO5: Telegram not received or faulty | Cause: CANopen communication module in MXI1: CAN-IN 5 error. Remedy:
|
| 0x00a10005 CAN module (MXI1) RPDO6: Telegram not received or faulty | Cause: CANopen communication module in MXI1: CAN-IN 6 error. Remedy:
|
| 0x00a10006 CAN module (MXI1) RPDO7: Telegram not received or faulty | Cause: CANopen communication module in MXI1: CAN-IN 7 error. Remedy:
|
| 0x00a10007 CAN module (MXI1) RPDO8: Telegram not received or faulty | Cause: CANopen communication module in MXI1: CAN-IN 8 error. Remedy:
|
| 0x00a10008 CAN module (MXI1) PDO manager: Faulty configuration | Cause: CANopen communication module in MXI1: CAN-PDO configuration error.
Remedy:
|
| 0x00a20000 CAN module (MXI1) SDO server: Faulty configuration | Cause: CANopen communication module in MXI1: In the CAN SDO server a configuration error has occurred. Remedy:
|
| 0x00a30000 CAN module (MXI1) SDO client: Faulty configuration | Cause: CANopen communication module in MXI1: In the CAN SDO client a configuration error has occurred. Remedy:
|
| 0x00aa0000 DFIN (MXI2): Track error A-/A | Cause: Digital frequency extension module in MXI2: Interruption (open circuit) of the signal cable for track A. Remedy:
|
| 0x00aa0001 DFIN (MXI2): Track error B-/B | Cause: Digital frequency extension module in MXI2: Interruption (open circuit) of the signal cable for track B. Remedy:
|
| 0x00aa0002 DFIN (MXI2): Track error Z-/Z | Cause: Digital frequency extension module in MXI2: Interruption (open circuit) of the signal cable for track Z. Remedy:
|
| 0x00aa0003 DFIN (MXI2): Signal error enable/lamp control | Cause: Digital frequency extension module in MXI2: Interruption (open circuit) of the signal cable for the “Enable” signal or no “Enable” signal available. Remedy:
|
| 0x00aa0004 DFIN (MXI2): Supply cannot be corrected anymore | Cause: Digital frequency extension module in MXI2: The encoder voltage controlled by the digital frequency input has reached the voltage limit. Remedy: Check encoder. |
| 0x00aa0005 DFOUT (MXI2): Maximum frequency reached | Cause: Digital frequency extension module in MXI2: Limit frequency at the digital frequency output reached (limit value set in C014053). Remedy: Check limit value set. |
| 0x00ac0000 CAN module (MXI2): Bus off | Cause: CANopen communication module in MXI2: “Bus-off” state.
Remedy:
|
| 0x00ac0001 CAN module (MXI2): Invalid node address 0 | Cause: CANopen communication module in MXI2: Initialisation error. The hardware allocation of the node address was selected via DIP switches, and the DIP switches are all on zero. Remedy:
|
| 0x00ac0002 CAN module (MXI2): Basic configuration invalid | Cause: CANopen communication module in MXI2: Configuration error.
Remedy:
|
| 0x00ad0000 … 0x00ad001f CAN module (MXI2): Heartbeat error index 1 … 32 | Cause: CANopen communication module in MXI2: Cyclic node monitoring. Node station has not received a heartbeat telegram from node 1…32 within defined time. Remedy:
|
| 0x00ad0020 CAN module (MXI2): Lifeguarding error | Cause: CANopen communication module in MXI2: Cyclic node monitoring. Slave response: Maximum time between two node guarding telegrams (remote transmission request telegram) from the master has been exceeded. Remedy:
|
| 0x00ad0021 CAN module (MXI2): Faulty NMT slave configuration | Cause: CANopen communication module in MXI2: A configuration error has occurred in the network management of the CAN slave.
Remedy:
|
| 0x00ae0000 CAN module (MXI2): Faulty emergency configuration | Cause: CANopen communication module in MXI2: CAN emergency configuration is faulty.
Remedy:
|
| 0x00af0000 … 0x00a0001f CAN module (MXI2): Node guarding error 1 … 32 | Cause: CANopen communication module in MXI2: Cyclic node monitoring. CAN master has not received a response to a node guarding telegram from node 1 … 32 within the defined time. Remedy:
|
| 0x00af0020 CAN module (MXI2): Faulty NMT master configuration | Cause: CANopen communication module in MXI2: A configuration error has occurred in the network management of the CAN master.
Remedy:
|
| 0x00b00000 CAN module (MXI2) RPDO1: Telegram not received or faulty | Cause: CANopen communication module in MXI2: CAN-IN 1 error.
Remedy:
|
| 0x00b00001 CAN module (MXI2) RPDO2: Telegram not received or faulty | Cause: CANopen communication module in MXI2: CAN-IN 2 error.
Remedy:
|
| 0x00b00002 CAN module (MXI2) RPDO3: Telegram not received or faulty | Cause: CANopen communication module in MXI2: CAN-IN 3 error.
Remedy:
|
| 0x00b00003 CAN module (MXI2) RPDO4: Telegram not received or faulty | Cause: CANopen communication module in MXI2: CAN-IN 4 error.
Remedy:
|
| 0x00b00004 CAN module (MXI2) RPDO5: Telegram not received or faulty | Cause: CANopen communication module in MXI2: CAN-IN 5 error.
Remedy:
|
| 0x00b00005 CAN module (MXI2) RPDO6: Telegram not received or faulty | Cause: CANopen communication module in MXI2: CAN-IN 6 error.
Remedy:
|
| 0x00b00006 CAN module (MXI2) RPDO7: Telegram not received or faulty | Cause: CANopen communication module in MXI2: CAN-IN 7 error.
Remedy:
|
| 0x00b00007 CAN module (MXI2) RPDO8: Telegram not received or faulty | Cause: CANopen communication module in MXI2: CAN-IN 8 error.
Remedy:
|
| 0x00b00008 CAN module (MXI2) PDO manager: Faulty configuration | Cause: CANopen communication module in MXI2: CAN-PDO configuration error.
Remedy:
|
| 0x00b10000 CAN module (MXI2) SDO server: Faulty configuration | Cause: CANopen communication module in MXI2: In the CAN SDO server a configuration error has occurred.
Remedy:
|
| 0x00b20000 CAN module (MXI2) SDO client: Faulty configuration | Cause: CANopen communication module in MXI2: In the CAN SDO client a configuration error has occurred.
Remedy:
|
| 0x00b80000 PLC configuration invalid | Cause: An invalid control configuration has occurred. Remedy:
|
| 0x00b80001 Positive limit switch has triggered | Cause: The travel range limit switch in positive traversing direction has tripped. Remedy:
|
| 0x00b80002 Negative limit switch has triggered | Cause: The travel range limit switch in negative traversing direction has tripped. Remedy:
|
| 0x00b80003 Motor brake: Angular drift with closed brake too high | Cause: The stop position of the motor axis has changed by more than the permissible angle of rotation set in C02595, although the brake is engaged. Remedy:
|
| 0x00b80004 Motor brake: Automatically activated after waiting time has elapsed | Cause: This time monitoring will only be active if the speed setpoint has reached the threshold for brake activation (C02581). If the actual speed value does not reach/fall below the threshold set in C02581 within the parameterised waiting time, the brake will be closed due to time-out. Remedy:
|
| 0x00b80005 Motor brake: Status monitoring error | Cause: Faulty external feedback of the brake status to the brake control. Remedy:
|
| 0x00b80007 Positive software limit switch overtravelled | Cause: The positive software limit position parameterised in C02702/2 has been overtravelled. Remedy:
|
| 0x00b80008 Negative software limit switch overtravelled | Cause: The negative software limit position parameterised in C02702/1 has been overtravelled. Remedy:
|
| 0x00b80009 Positive direction of rotation limited | Cause: Due to the setting of C02707 it was tried to traverse in the impermissible positive direction of rotation. Remedy:
|
| 0x00b8000a Negative direction of rotation limited | Cause: Due to the setting of C02707 it was tried to traverse in the impermissible negative direction of rotation. Remedy:
|
| 0x00b8000b Speed has been limited | Cause: The requested profile speed is higher than the maximum speed set in C02703 and has been limited to this speed. The required profile speed cannot be achieved with the motor reference speed set in C00011. Remedy:
|
| 0x00b8000c Acceleration has been limited | Cause: The requested profile acceleration is higher than the maximum acceleration set in C02705 and has been limited to this acceleration. Remedy:
|
| 0x00b8000d Deceleration has been limited | Cause: The requested profile deceleration is higher than the maximum acceleration set in C02705 and has been limited to this acceleration. Remedy:
|
| 0x00b8000e Jerk has been limited | Cause: The requested S-ramp time is lower than the minimum S-ramp time set in C02706 and has been limited to this S-ramp time. Remedy:
|
| 0x00b8000f Position target outside the software limit positions | Cause: It was tried to position to a target outside the software limit positions. Remedy:
|
| 0x00b80010 Maximum speed exceeded | Cause: The max. speed parameterised in C02703 or C00011 has been exceeded. Remedy:
|
| 0x00b80011 Maximum acceleration exceeded | Cause: The max. acceleration parameterised in C02705 has been exceeded. Remedy:
|
| 0x00b80012 Time-out torque feedforward control – brake | Cause: After 1 second the actual torque has not yet reached 90% of the precontrolled setpoint torque for releasing the brake. Remedy:
|
| 0x00b80013 Cam data: Serial number MM does not match | Cause: The cam data are provided with an access protection of level 3 (linkage to the memory module), and the serial number contained in the cam data does not correspond to the serial number of the memory module. Remedy:
|
| 0x00b80014 Cam data are corrupted | Cause: Checksum error during reading the file, or the password was manipulated. Remedy:
|
| 0x00b80015 Cam data restored | Cause: The last download of the cam data was faulty or has not been completed successfully. The previous cam data – if available – have been downloaded from the backup file. Remedy:
|
| 0x00b80016 Cam data locked due to incorrect password | Cause: The cam data were locked since the user password was entered incorrectly for three times. The cam data were not loaded. Remedy: Reset parameters to the Lenze setting via device command C00002 = “0: Load Lenze setting”. Then download cam data again. |
| 0x00b80017 Cam data locked due to incorrect safety key | Cause: The cam data were not loaded because the safety key is damaged. The password in the cam data or the serial number of the memory module has been manipulated. Remedy: Reset parameters to the Lenze setting via device command C00002 = “0: Load Lenze setting”. Then download cam data again. |
| 0x00b80019 Homing mode not allowed | Cause: From software version V3.0: The homing mode selected in C02640 is not supported in the motor control type selected in C00006. Remedy: Select another homing mode in C02640. |
| 0x00b8001a Int. overflow C02620 (manual jog: Speed 1) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b8001b Int. overflow C02621 (manual jog: Speed 2) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b8001c Int. overflow C02622 (manual jog: Acceleration) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b8001d Int. overflow C02623 (manual jog: Deceleration) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b80020 Int. overflow C02701/1 (positive software limit position) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b80021 Int. overflow C02701/2 (negative software limit position) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b80022 Int. overflow C02703 (maximum speed) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b80023 Int. overflow C02705 (maximum acceleration) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b80024 Int. overflow C02708/1 (limited speed 1) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b80025 Int. overflow C02708/2 (limited speed 2) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b80026 Int. overflow C02708/3 (limited speed 3) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b80027 Int. overflow C02708/4 (limited speed 4) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b80028 Int. overflow C02708/1 (decel. limited speed 1) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b80029 Int. overflow C02708/2 (decel. limited speed 2) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b8002a Int. overflow C02708/3 (decel. limited speed 3) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b8002b Int. overflow C02708/4 (decel. limited speed 4) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b8002c Int. overflow C02713 (max. dist. manual control) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b8002d Int. overflow C02642 (home position) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b8002e Int. overflow C02643 (homing: Target position) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b8002f Int. overflow C02644 (homing: Speed 1) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b80030 Int. overflow C02645 (homing: Acceleration 1) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b80031 Int. overflow C02646 (homing: Speed 2) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b80032 Int. overflow C02647 (homing: Acceleration 2) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b80033 Int. overflow C02670 (positioner: Tol. for target position) | Cause: From software version V3.0: Due to a subsequent change of the machine parameters for gearbox ratio, feed constant, or resolution of an encoder revolution, the value set in the parameter cannot be displayed in the internal unit. Remedy:
|
| 0x00b80034 Cam data: Invalidated due to change of mechanical data | Cause: From software version V4.0: One or several machine parameters have been changed that have an influence on the internal scaling of the Cam data. The Cam data has to be recalculated. Remedy: Execute device command C00002 = “503: Calculate Cam Data”. This automatically resets the warning. |
| 0x00b80035 Cam data: invalid product number | Cause: From software version V5.0: A product number has been created in the system block LS_CamInterface which is not in the range of product number of the downloaded cam data. Remedy: Check number of products.
|