Lenze i700 cabinet Servo Drive

Lenze i700 cabinet Servo Drive Fault Codes:

Fault Code and MeaningCause and Remedy
EtherCAT_Master: Start master failed. Bus mismatch


Bus does not assume “Pre-Operational” state
Cause: Faulty bus configuration and bus structure.

  • Slaves are missing.

  • Slaves have been inverted or their configuration is faulty.

  • A wrong slave type has been configured or is at the fieldbus.

  • The inputs and outputs of the EtherCAT communication module are reversed (IN/OUT connections).

  • Faulty wiring.




Remedy:

  • Correct the bus configuration or the physical bus structure.

  • Afterwards, reload the »PLC Designer« application into the automation system.
EtherCAT_Master: Start master failed. EtherCAT cable disconnected


Wiring error
Cause: Wiring error: EtherCAT cable is not connected to the master.



Remedy:

  • Correct wiring.

  • Afterwards, reload the »PLC Designer« application into the automation system.
0x4000005
EtherCAT_Master: Set master ‘Operational’ failed


SDO Abort ‘Object does not exist’
Cause: Start parameter could not be written.



Remedy:

  • Correct the start-up parameters in »PLC Designer« on the Configuration tab of the EtherCAT master.
EtherCAT_Master: Set master ‘Operational’ failed. DCM not in-sync


Wiring error (IN/OUT inverted)
Cause: Wiring error: The EtherCAT terminals (IN/OUT) of the slave were inverted. A fieldbus scan does not indicate this error!



Remedy:

  • Correct wiring.

  • Afterwards, reload the »PLC Designer« application into the automation system.
0x12 / 0x1E
AL Status Code: ‘Invalid Input Configuration’


Structure mismatch (EPM-S130)
Cause: The real structure at an EPM-S130 head end does not correspond to the control configuration configured. This error can occur if I/O panels have been added manually.



Remedy:

  • Correct control configuration in the »PLC Designer«.

  • Note: In “data: …”, a coded information says which error has occurred in which slave device/module.
0x4000005 / 0x1A
AL Status Code: ‘Synchronization error’


Inconsistent Sync settings
Cause: Synchronisation settings in the standard device (slave) and the »PLC Designer« configuration are inconsistent.



Remedy:

  • Adapt the synchronisation settings in the slave.
EtherCAT_Master: DC slaves ‘out-of-sync’


Deviation xxxxxxxx ns
Cause: The first slave after the master has not been defined as DC master.



Remedy:

  • Declare the first slave after the master as DC master (“DC for Synchronization”).
WKC Error / Not all slaves ‘Operational’


Cyclical command WKC error
Cause:

  • The bus cable between two EtherCAT nodes has been unplugged.

  • The node at position X is deenergised.

  • A slave no longer receives cyclical frames so that the watchdog determined by the device description is triggered.




Remedy:

  • Correct bus topology.

  • Restart the EtherCAT fieldbus.
Invalid SyncManager Configuration


[DeviceName] (1001)
Cause:

  • One of the slaves does not support an LRW command (Logical Read/Write).

  • A slave is not written to correctly.




Remedy:

  • In the EtherCAT master tab, do not select the “Use LRW instead of LWR/LRD” checkbox.
Invalid Input/Output Configuration


AL state code: 0x1E or 0x1D
Cause: The process data configuration of a slave is not correct.

  • In case of a modular device (e.g., I/O system 1000), configuration in project does not comply with real assembly.

  • More process data than permissible are mapped for the device.




Remedy:

  • Correct the control configuration in the »PLC Designer« (adjustment with the real setup).

  • Reduction of the process data (maximum length must not be exceeded).
Logic Address Error


Error during process data transfer
Cause: Use of logic addresses directly (%Ixx, %Qxx) instead of symbolically. The bus structure or PDO selection may have changed.



Remedy:

  • In the »PLC Designer« application, input/output objects must be accessed via individual, non-ambiguous variables.

  • Variable names must comply with IEC 61131 syntax.
Manual definition of logic address


I/O mapping manipulation
Cause: Manual definition of the logic address in the EtherCAT I/O mapping (e.g. changing %QB70 to %QB1000).



Remedy:

  • It is not permissible to manually manipulate the I/O addresses for the EtherCAT bus!
Missing or incorrect I/O mapping


Servo Drives 9400 / Inverter 8400
Cause: Ports in »Engineer« are displayed incorrectly or not at all.



Remedy:

  • Check and correct the mapping settings in the control configuration and in the inverter.

  • Note: When Lenze Controller starts, mapping entries from »Engineer« are overwritten by the configuration/PDO mapping.
Variables not used in »PLC Designer«


Process image update issue
Cause: I/O variables not used in »PLC Designer« are not copied into the process image, so they are not updated.



Remedy:

  • With the slave, go to the EtherCAT I/O Mapping tab and set a checkmark at Always update variables.
EtherCAT_Master: EtherCAT cable not connected


Timeout / Safe-Operational
Cause: The bus cable between the Lenze Controller and the first node has been unplugged and plugged back in. The slaves sync managers timed out.



Remedy:

  • After the bus cable has been plugged in again, Restart the EtherCAT fieldbus.
EtherCAT_Master: Frame response error


Repeated 1/10/100 times
Cause: A frame sent by the master does not return until the next cycle.

  • Task utilisation too high.

  • EtherCAT bus cycle task does not have the highest IEC task priority.

  • Slave error forwarding frames.

  • Only a switch or ET2000 connected but no slave.




Remedy:

  • Reduce the program code or increase the bus task cycle time.

  • Assign the sole and highest IEC task priority to the EtherCAT bus cycle task.

  • Correct the slave error or bus structure.
Shafts make clicking noises


Cycle time mismatch
Cause: The task and DC cycle times set in the logic/motion system differ.



Remedy:

  • Adjust the task cycle time and DC cycle time.
Shafts make clicking noises


“out-of-sync” re-synchronisation
Cause: If due to a fault, the preset DC deviation limit is exceeded, a re-synchronisation is carried out. Currently not synchronised.



Remedy:

  • Restart the EtherCAT fieldbus so that the DC slaves and DC master synchronise again.
Sync Source Error


9400 HighLine CiA402
Cause: Wrong selection of the device sync source (C01120). After change, download may fail.



Remedy:

  • Manual setting of code C01120 to MXI1 or MXI2.

  • Repeated download with PLC start.

  • Restarting the EtherCAT fieldbus with reset of the SoftMotion drive.
Shafts do not rotate


Faulty SoftMotion scaling
Cause: Faulty SoftMotion scaling/mapping; increments per revolution are not set.



Remedy:

  • Check Gearbox ratio in the »PLC Designer« application.

  • Check Mapping settings in the master configuration.

  • Tip: In the case of Servo Drive 9400 HighLine CiA402, 65536 increments per revolution are correct.
0x0000

No error
Cause:

No error pending.



Remedy:

None.
0x2320

Short circuit or earth leakage at the motor end
Cause:


  • Earth fault in motor cable.

  • Excessive capacitive charging current in the motor cable.




Remedy:


  • Check motor cable.

  • Use motor cable that is shorter or has a lower capacitance.


Note: Error reset only possible after 5 s.
0x2340

Short circuit at the motor end
Cause:


  • Short circuit/earth fault in motor cable.

  • Excessive capacitive charging current in the motor cable.




Remedy:


  • Check motor cable.

  • Use motor cable that is shorter or has a lower capacitance.


Note: Error reset only possible after 5 s.
0x2351

Motor utilisation (I²xt) > [value] %
Cause:

Motor is thermally overloaded, e.g. due to:

  • Impermissible continuous current.

  • Frequent or too long acceleration processes.




Remedy:


  • Check drive dimensioning.

  • Check setting or the warning or error threshold.
0x2380

Fault – utilisation of the power section (Ixt) too high
Cause:

Frequent and too long acceleration processes with overcurrent.



Remedy:


  • Check drive dimensioning.
0x2381

Warning – utilisation of the power section (Ixt) too high
Cause:

Frequent and too long acceleration processes with overcurrent.



Remedy:


  • Check drive dimensioning.
0x2382

Fault – device utilisation (Ixt) too high
Cause:

Frequent and too long acceleration processes with overcurrent.



Remedy:


  • Check drive dimensioning.
0x2383

Warning – device utilisation (Ixt) too high
Cause:

Frequent and too long acceleration processes with overcurrent.



Remedy:


  • Check drive dimensioning.
0x2384

Ultimate motor current reached
Cause:

The motor current has exceeded the “ultimate” motor current. The “ultimate” motor current corresponds to the current level at which the permanent magnets of a synchronous motor suffer permanent damage.



Remedy:


  • Reduce maximum current (0x6073 | 0x6873) and/or adjust the current controller (0x2942 | 0x3142) in order to reduce the current overshoot.
0x2385

Output current > [value] A (maximum device current)
Cause:

The desired maximum current (0x6073 | 0x6873) is higher than the maximum current of the axis (display in 0x2DDF:2 | 0x35DF:2).



Remedy:

The permissible maximum current (0x6073 | 0x6873) is: Maximum axis current / Rated motor current.

  • Check setting of rated motor current in 0x6075 | 0x6875.
0x2386

Clamp is active
Cause:

Maximum current of the axis (display in 0x2DDF:2 | 0x35DF:2) has been reached.



Remedy:


  • Select a flatter speed ramp.

  • Reduce the load.

  • Set the Imax controller (0x2B08 | 0x3308) more dynamically.
0x2387

Clamp responded too often
Cause:

Maximum current of the axis (display in 0x2DDF:2 | 0x35DF:2) was reached too often in a row.



Remedy:


  • Select a flatter speed ramp.

  • Reduce the load.

  • Set the Imax controller (0x2B08 | 0x3308) more dynamically.
0x2390

Fault – utilisation of the power section (Ixt) too high
Cause:

Frequent and too long acceleration processes with overcurrent in combination of both axes.



Remedy:


  • Check drive sizing of both axes.
0x2391

Warning – utilisation of the power section (Ixt) too high
Cause:

Frequent and too long acceleration processes with overcurrent in combination of both axes.



Remedy:


  • Check drive sizing of both axes.
0x2392

Fault – device utilisation (Ixt) too high
Cause:

Frequent and too long acceleration processes with overcurrent in combination of both axes.



Remedy:


  • Check drive sizing of both axes.
0x2393

Warning – device utilisation (Ixt) too high
Cause:

Frequent and too long acceleration processes with overcurrent in combination of both axes.



Remedy:


  • Check drive sizing of both axes.
0x3210

DC bus – overvoltage [value] V
Cause:

Due to a too high braking energy, the DC-bus voltage exceeds the overvoltage threshold which results from the mains voltage setting.



Remedy:


  • Connect brake resistor to power supply module or use regenerative module.

  • Check mains setting.

  • Check drive profile.
0x3220

DC bus – undervoltage [value] V
Cause:

DC bus voltage is lower than the undervoltage threshold resulting from the mains setting.



Remedy:


  • Check mains voltage.

  • Check DC-bus voltage.

  • Check mains settings.
0x4210

Module temperature too high, [value]
Cause:

Heatsink temperature higher than fixed temperature limit (100 °C):

  • i700 servo inverters ambient temperature too high.

  • Dirty fan or ventilation slots.

  • Fan defective.

  • Warning threshold set too low.




Remedy:


  • Check control cabinet temperature.

  • Clean filter.

  • Clean i700 servo inverters.

  • Replace fan.
0x4280
Internal fault – module temperature monitoring
Cause: Thermal sensor error.



Remedy:

  • 24 V mains switching required.

  • If the error occurs frequently, please contact Lenze.
0x4310
Motor temperature too high, [value]
Cause: Motor temperature higher than variable temperature limit:

  • Motor too hot due to impermissibly high currents or frequent and too long acceleration processes.

  • No KTY connected.

  • Error or warning threshold set too low.





Remedy:

  • Check drive dimensioning.

  • Connect KTY or switch off monitoring.

  • Set a higher warning or error threshold.
0x4380
Motor temperature sensor
Cause: Motor temperature sensor.



Remedy:

  • Connect KTY or switch off monitoring.

  • Set a higher warning or error threshold.
0x5112
24 V supply
Cause: 24 V supply has failed or has fallen below the warning threshold (21.45 V) or error threshold (18.15 V).



Remedy:

  • Check 24 V voltage supply.
0x6010
Watchdog reset
Cause:

  • Reset was triggered via device command 1100.

  • Internal error.





Remedy:

  • If the reset was not triggered via the device command, consult Lenze if the error occurs frequently.
0x6080
The new firmware is incompatible
Cause:

  • The redownloaded firmware is incompatible to the one on the device.

  • The new firmware has not been accepted.





Remedy:

  • Download a compatible firmware version (same major version).

  • If the current firmware shall be maintained, the error can simply be acknowledged.
0x6310
Incorrect parameter set download
Cause: Error when downloading a parameter set:

  • CRC error in the parameter set detected.

  • Vendor, product code or revision of the object directory are different.

  • Unknown parameter set.





Remedy:

  • Repeat parameter set download.

  • Recreate parameter set.
0x6320
Parameter error in object [value]
Cause: Unknown index in the parameter set.



Remedy:

  • Recreate parameter set.
0x7121
PLI – motor blocked
Cause: An error occurred during the pole position identification. The pole position identification could not be completed successfully:

  • Too many deviations during the identification.

  • Motor is blocked.





Remedy:

  • Check whether all requirements for an identification of the pole position are fulfilled.

  • Ensure that the machine is not braked or blocked during the pole position identification.

  • Repeat the pole position identification.
0x7303
Error in feedback system
Cause:

  • Encoder cable interrupted.

  • Encoder defective.





Remedy:

  • Check encoder cable.

  • Check encoder.

  • Switch off monitoring if feedback is not used.
0x7380
Hiperface communication error
Cause: Communication with HIPERFACE® absolute value encoder is disturbed.



Remedy:

  • Check the supply voltage of the encoder (0x2C42:2 | 0x3442:2).

  • Check wiring to the encoder.
0x7381
Hiperface: Wrong absolute value – motor speed too high
Cause: The absolute position of the HIPERFACE® absolute value encoder cannot be accepted as the motor rotates too fast.



Remedy:

  • Let the motor coast.
0x8180
ECAT DC – synchronisation required
Cause: EtherCAT DC mode not activated. (DC = Distributed Clock).



Remedy:

  • Activate DC mode.
0x8181
EtherCAT communication
Cause: EtherCAT communication error.



Remedy:

  • Check EtherCAT bus cabling.

  • Select a longer PDI watchdog time.
0x8280
Sync Manager – address [value]
Cause: Incorrect Sync Manager setting of the EtherCAT master.



Remedy:

  • Check the devices on the bus.

  • Check cabling or sequence of the devices on the bus.

  • Remove the i700 servo inverter from the project tree and rescan the bus.

  • Check the device description of the i700 servo inverter.
0x8281
Sync Manager – current size [value]
Cause: Incorrect Sync Manager setting of the EtherCAT master.



Remedy:

  • Check the devices on the bus.

  • Check cabling or sequence of the devices on the bus.

  • Remove the i700 servo inverter from the project tree and rescan the bus.

  • Check the device description of the i700 servo inverter.
0x8282
Sync Manager – settings [value]
Cause: Incorrect Sync Manager setting of the EtherCAT master.



Remedy:

  • Check the devices on the bus.

  • Check cabling or sequence of the devices on the bus.

  • Remove the i700 servo inverter from the project tree and rescan the bus.

  • Check the device description of the i700 servo inverter.
0x8283
PDO mapping: Object unknown (index [value])
Cause: Unknown index in the PDO mapping.



Remedy:

  • Check PDO mapping.
0x8284
No PDO mapping object (index [value])
Cause: Index cannot be mapped as PDO.



Remedy:

  • Check PDO mapping.
0x8285
Too many objects mapped (max. number = [value])
Cause: Max. number of PDO mapping objects has been exceeded (> 64).



Remedy:

  • Reduce the number of mapping objects in the “free mapping”.
0x8286

PDO mapping – error
Cause:

Incorrect PDO mapping.



Remedy:

Check PDO mapping.
Response: Interference
0x8700

Sync controller
Cause:

  • EtherCAT Sync0 signal has failed.

  • PDO transmitted or received too late.




Remedy:

  • Check in EtherCAT master configuration whether DC mode is set.

  • Restart EtherCAT configuration.

  • Select a later instant of reception, outside the user shift time.

  • Sync Error Counter – increase monitoring limit (0x10F1:2).


Response: Class II fault. The response set in 0x605E | 0x685E takes place.
0x8701

Time-out during synchronisation with EtherCAT sync signal
Cause:

During the EtherCAT state change from “Pre-Operational” to “Safe-Operational”:

  • EtherCAT Sync0 signal has failed.

  • Jitter of the EtherCAT Sync0 signal is too high.




Remedy:

  • Check EtherCAT master configuration for DC deviation.

  • Restart EtherCAT configuration.


Response: Interference
0xFF00

Fatal internal error
Cause:

Internal error.



Remedy:

  • 24 V mains switching required.

  • If the error occurs frequently, please contact Lenze.


Response: Interference
0xFF01

Fatal internal communication error, cycle [value]
Cause:

Internal error.



Remedy:

  • 24 V mains switching required.

  • If the error occurs frequently, please contact Lenze.


Response: Interference
0xFF02

Brake
Cause:

Brake error due to short circuit or cable break.



Remedy:

Check brake cable or brake.
Response: Warning in “manual control” mode. Otherwise class II fault. If “fault” is set, the response set in 0x605E | 0x685E takes place.
0xFF03

Fatal internal error overflow task
Cause:

Internal error.



Remedy:

  • 24 V mains switching required.

  • If the error occurs frequently, please contact Lenze.


Response: Interference
0xFF04

PLI – motor movement too large
Cause:

Motor moved too much during pole position identification.



Remedy:

  • Check settings of the pole position identification in 0x2C62 | 0x3462.

  • If this error takes place in pole position identification without any motion, the motor has to be stalled.


Response: Fault (adjustable in 0x2C60 | 0x3460)
0xFF05

STO inhibited
Cause:

The servo inverter is inhibited via STO terminals, despite controller enable via the control word.



Remedy:

  • Deactivate STO or inhibit the servo inverter.

  • Check the cabling of the STO terminals.


Response: Warning with change to the “Switch on disabled” device status.
0xFF06

Max. speed reached
Cause:

Motor speed too high.



Remedy:

  • Reduce motor speed.

  • Check resolver or cabling.


Response: Fault (adjustable in 0x2D44:2 | 0x3544:2). Threshold can be adapted in 0x2D44:1 | 0x3544:1.
0xFF07

Impermissible during identification or in test mode
Cause:

A parameter was attempted to change which influences the identification in progress or the currently activated test mode.



Remedy:

Postpone changing the parameter until the identification is completed or the test mode is deactivated again.
Response: Warning
0xFF08

Impossible during identification
Cause:

A parameter was attempted to change which influences the identification in progress.



Remedy:

Postpone changing the parameter until the identification is completed.
Response: Warning
0xFF09

Motor phase failure
Cause:

Multiple motor phases are not connected.



Remedy:

  • Correct the wiring between the servo inverter and the motor.

  • In the case of a false alarm, increase the threshold values for monitoring in 0x2D45 | 0x3545.


Response: Default setting: No response. Monitoring takes place before and during operation.
0xFF0A

Motor phase failure phase U
Cause:

Motor phase U is not connected.



Remedy:

  • Correct the wiring between the servo inverter and the motor.

  • In the case of a false alarm, increase the threshold values for monitoring in 0x2D45 | 0x3545.


Response: Default setting: No response.
0xFF0B

Motor phase failure phase V
Cause:

Motor phase V is not connected.



Remedy:

  • Correct the wiring between the servo inverter and the motor.

  • In the case of a false alarm, increase the threshold values for monitoring in 0x2D45 | 0x3545.


Response: Default setting: No response.
0xFF0C

Motor phase failure phase W
Cause:

Motor phase W is not connected.



Remedy:

  • Correct the wiring between i700 servo inverters and motor.

  • In the case of a false alarm, increase the threshold values for monitoring in 0x2D45 | 0x3545.


Response: Default setting: No response.
0xFF0E

Speed too low –> command cannot be executed
Cause:

The actual speed is too low for the resolver error to be identified.



Remedy:

Repeat identification at higher speed.
Response: Warning
0xFF0F

No resolver connected –> command cannot be executed
Cause:

The identification of a resolver error was attempted but an encoder is used as feedback system.



Remedy:

Identification is only possible with devices with resolver feedback.
Response: Warning
0xFF10

Time-out
Cause:

The actual speed is too low for the resolver error to be identified.



Remedy:

Repeat identification at higher speed.
Response: Warning
0xFF11

Numerical problem
Cause:

The actual speed is too low for the resolver error to be identified.



Remedy:

Repeat identification at higher speed.
Response: Warning
0xFF12

Inverter error too big
Cause:

The results of the inverter error identification are not plausible.



Remedy:

Check shielding of the motor cable. Connect the shield with a surface as large as possible.
Response: Warning
0xFF13

Identification aborted
Cause:

A started identification was aborted due to an error or a controller inhibit.



Remedy:

Repeat the identification and avoid the cause of the abort.
Response: Faulty pole position identification (adjustable in 0x2C60 | 0x3460). Otherwise warning.
0xFF14

Impossible in the ‘operation enabled’ or ‘quick stop active’ state
Cause:

Reading out and accepting the hiperface data is only permitted when the controller is inhibited.



Remedy:

Inhibit controller.
Response: Warning
0xFF15

No Hiperface absolute value encoder connected –> command cannot be executed
Cause:

When the “resolver” device version or the sin/cos encoder has been selected, an attempt is being made to read the data from a HIPERFACE® absolute value encoder.



Remedy:

The command is only possible with the “encoder” device version. Moreover, the “2: Hiperface absolute value encoder” selection has to be set in 0x2C40 | 0x3440.
Response: Warning
0xFF16

Connected Hiperface absolute value encoder is not supported
Cause:

The HIPERFACE® absolute value encoder has a type code which is neither stored in the firmware nor corresponds to the type code set in 0x2C41:2 | 0x3441:2.



Remedy:

Set type code in 0x2C41:2 | 0x3441:2.
Response: Fault (adjustable in 0x2C41:4 | 0x3441:4)
0xFF17

Connected Hiperface absolute value encoder is not supported –> Command cannot be executed
Cause:

The HIPERFACE® absolute value encoder is not supported by the device. Hence, no data can be detected.



Remedy:

Connect a HIPERFACE® absolute value encoder which is supported by the device.
Response: Warning
0xFF18

Communication time-out in manual control mode
Cause:

In the “manual control” mode, writing the setpoint data failed to appear for a longer period of time than set in 0x2836:5 | 0x3036:5.



Remedy:

  • Check connection between device, Controller and »EASY Starter« or »PLC Designer«.

  • Increase the time period in 0x2836:5 | 0x3036:5.

  • Restart manual jog dialog.


Response: Interference
0xFF19

Internal error during identification
Cause:

Internal error during identification.



Remedy:

Please contact Lenze.
Response: Warning
0xFF20

The check of the Replacement Protection has failed
Cause:

The check of the Replacement Protection has failed.



Remedy:

  • Enter correct Replacement Protection ID.

  • Replace device by an OEM device.

  • Reprogram Replacement Protection ID.
0xFF21

Time-out – holding brake feedforward control
Cause:

The given feedforward control torque could not be built up within one second.



Remedy:

–
0xFF22

Speed error occurred
Cause:

The speed error exceeds the limit from 0x2D51:1 / 0x3551:1 for a time period > 0x2D51:2 / 0x3551:2.



Remedy:

  • Increase time-out in 0x2D51:2 or 0x3551:2.

  • Increase limit in 0x2D51:1 or 0x3551:1.

  • Increase speed controller gain.

  • Increase torque and/or current limit.
0xFF23

Position error occurred
Cause:

The check of the Replacement Protection has failed.



Remedy:

  • Increase time-out in 0x2D51:4 or 0x3551:4.

  • Increase limit in 0x2D51:2 or 0x3551:2.

  • Increase position controller gain.
0xFF24

Sync0 cycle time is invalid
Cause:

The requested Sync0 cycle on the Ethercat is not within the limits 125 µs ≤ x ≤ 10 ms anymore supported by this device.



Remedy:

Select another Sync0 cycle in the control for this bus interconnection that is within the limits 125 µs ≤ x ≤ 10 ms.
0xFF25

The hardware is not supported
Cause:

Internal error.



Remedy:

Exchange software with older version (< 1.10.xx).
0xFF26

Cable Check – motor movement too great
Cause:

During the Cable Check, the motor “jumps” to a new position.



Remedy:

  • Phase shifter in the motor cable: Swap two phases of the motor cable.

  • Axis was moved manually: Stop axis.

  • Motor parameters (number of pole pairs, motor type) are not set correctly: Set motor parameters correctly.

  • Synchronous machine – the pole position is set incorrectly: Set pole position correctly.

  • Motor with brake – the brake was released early by an external source: Prevent the brake to be released by an external source.
0xFF27

Cable Check – incorrect direction of rotation
Cause:

During the wiring test, the motor cannot follow the specified angle.



Remedy:


  • Motor and encoder cable do not lead to the same motor:

    • Up to Softwarestand V02.10.xx: Identify a common motor and encoder cable.

    • From V02.11.xx: Switch off current supply, correct wiring, then switch on and execute Cable Check again.




  • Phase shifter in the motor cable:

    • Up to Softwarestand V02.10.xx: Switch off current supply, swap two phases of motor cable.

    • From V02.11.xx: Switch off current supply, swap two phases, then switch on and execute Cable Check again.



  • Missing motor phase(s): Check motor phase(s).

  • Motor without brake: Test current is not high enough or machine is blocked. Check mechanics.

  • Motor with brake: Brake is so strong no movement is detected. Ensure motor can rotate freely.

  • Incorrect pole position: Switch off current supply, correct wiring. Switch on, carry out pole position identification, then execute Cable Check again.

  • Motor and encoder data possibly incorrect: Compare parameter data with nameplate and correct if necessary.
0xFF28

Master password entered incorrectly 4 times
Cause:

An incorrect master password was used for the log-in too frequently.



Remedy:

  • Use the correct master password for the log-in.

  • Switch mains to delete the warning.