Lenze i950 cabinet Servo Drive

Lenze i950 cabinet Servo Drive Fault Codes:

Fault Code and MeaningCause and Remedy
0x00000000
No error
Cause: No error.


Remedy:

  • For information only. No remedy necessary.
0x20092320
Short circuit or earth leakage at the motor end
Cause:

  • Short circuit/earth fault of motor cable.

  • Capacitive charging current of the motor cable too high.




Remedy:

  • Check motor cable.

  • Check length of the motor cable.

  • Use shorter or lower-capacitance motor cable.

  • Note: The event can only be reset after a blocking time (5 s).
0x20092340
Short circuit at the motor end
Cause: Short circuit of motor cable.


Remedy:

  • Check motor cable for short circuit.

  • Note: The event can only be reset after a blocking time (5 s).
0x20092351
Motor utilization too high (i²xt)
Cause: Motor thermally overloaded, e.g. by an impermissible continuous current or by frequent or too long acceleration processes.


Remedy:

  • Check drive sizing.

  • Check the setting in the warning threshold or error threshold.
0x20092380
Trouble – utilization of the power section (ixt) too high
Cause: Power section overloaded.


Remedy:

  • Check drive sizing.
0x20092381
Warning – Utilization of the power section (ixt) too high
Cause: Power section overloaded.


Remedy:

  • Check drive sizing.
0x20092382
Fault – Device utilization (ixt) too high
Cause: Device utilisation (ixt) too high by frequent and too long acceleration processes.


Remedy:

  • Check drive sizing.

  • Reduce the maximum current of the inverter (0x6073).

  • In case of high mass inertias, reduce maximum current of the inverter (0x6073) to 150 %.

  • Note: The inverter is disabled immediately. Blocking time: 3 s.
0x20092383
Warning – Device utilization (ixt) too high
Cause: Device utilisation (ixt) too high by frequent and too long acceleration processes.


Remedy:

  • Check drive dimensioning.
0x20092384
Ultimate motor current reached
Cause: Ultimate motor current reached.


Remedy:

  • Reduce the maximum current of the inverter (0x6073).

  • Optimize the current controller (0x2942).
0x20092385
Parameterized max. motor current > max. device current
Cause: Parameterized max. motor current 0x6073 > max. device current 0x2DDF:002.


Remedy:

  • Reduce max. motor current (0x6073).
0x20092386
Clamp is active
Cause: Max. device current has been reached (Display in 0x2DDF:002).


Remedy:

  • Select a flatter speed ramp.

  • Reduce the load.

  • Set Imax controller more dynamically (0x2B08).
0x20092387
Clamp responded too often
Cause: Maximum current of the axis (display in 0x2DDF:002) has been reached too often in succession.


Remedy:

  • Select a flatter speed ramp.

  • Reduce the load.

  • Set Imax controller more dynamically.
0x20092389
Warning – device utilization (ixt) too high
Cause: Frequent and too long acceleration processes with overcurrent.


Remedy:

  • Check drive sizing.
0x2009238B
Trouble – Device utilization (ixt) too high
Cause: Frequent and too long acceleration processes with overcurrent.


Remedy:

  • Check drive sizing.
0x20093181
Mains failure
Cause: The motor was decelerated to standstill via the mains failure control without an undervoltage fault occurring.


Remedy:

  • Check mains voltage.

  • Check mains settings.

  • Check fuses.
0x20093210
Fault – DC bus overvoltage
Cause: DC-bus voltage has exceeded the error threshold for overvoltage due to a too high braking energy or a too high mains voltage. The error threshold results from the setting of the rated mains voltage.


Remedy:

  • Reduce dynamic performance of the load profile.

  • Check mains voltage.

  • Check settings for brake energy management.

  • Connect brake resistor to the power unit and activate the integrated brake chopper (0x2541:001 = [0]).
0x20093220
Fault – DC bus undervoltage
Cause: DC-bus voltage has fallen below the error threshold for undervoltage.


Remedy:

  • Check mains voltage.

  • Check DC-bus voltage.

  • Check mains settings.

  • Check fuses.

  • Note: The event can only be reset after a blocking time (5 s).
0x20094210
Fault – Power unit overtemperature
Cause: The heatsink temperature of the power unit has exceeded the fixed error threshold (100 °C).

  • Ambient temperature too high.

  • Fan or ventilation slots are polluted.

  • Fan is defective.




Remedy:

  • Check mains voltage.

  • Provide for a sufficient cooling of the device (In case of a 100% load, 60°C to +70°C are normal).

  • Clean fan and ventilation slots. If required, replace fan.

  • Reduce switching frequency (0x2939).
0x20094280
Fault – Heat sink temperature sensor
Cause: Sensor for the temperature monitoring of the power unit is defective. The failure of the temperature monitoring function poses the risk of overheating!


Remedy:

  • Hardware error: it is necessary to contact the manufacturer, since the device must be replaced.
0x20094281
Heat sink fan warning
Cause: Warning of the heatsink fan.


Remedy:

  • Clean fan and ventilation slots.

  • If required, replace fan. The fans can be unlocked via locking hooks and can then be removed.
0x20094282
Thermal overload of control unit
Cause:

  • Control card temperature > 100 °C.

  • Ambient temperature too high.




Remedy:

  • Provide for better cooling.

  • Reduce ambient temperature.
0x20094310
Motor overtemperature
Cause: The motor temperature sensor measures a too high motor temperature.

  • Motor too hot by impermissibly high currents.

  • Motor too hot by frequent and too long acceleration processes.




Remedy:

  • Check drive dimensioning.

  • Check motor temperature sensor and wiring.

  • Blocking time: 5 s.
0x20094380
Fault – Motor temperature sensor
Cause: Motor PTC error.


Remedy:

  • Connect PTC or switch off monitoring.
0x20094381
Error – Motor temperature monitoring (PTC)
Cause: Motor PTC error.


Remedy:

  • Connect PTC or switch off monitoring.
0x20095112
External supply voltage critical
Cause: External supply voltage failed or too low.


Remedy:

  • Check external 24V voltage supply (terminal X5/24E).

  • Check mains voltage.
0x20096010
Internal error
Cause: Internal error.


Remedy:

  • Restart the device.

  • If the error persists, contact the manufacturer.
0x2009618A
Warning – Internal fan
Cause: Warning of the internal fan.


Remedy:

  • Check/replace internal fan.
0x20096310
Incorrect parameter set download
Cause: CRC error in the parameter set detected. Vendor, product code or OBD revision are different. The parameter set is unknown.


Remedy:

  • Recreate parameter set.

  • Repeat parameter set download.
0x20096320
Parameter error in object
Cause: Unknown index in the parameter set.


Remedy:

  • Recreate parameter set.
0x20097081
Fault – Analog input 1
Cause: The monitoring function of the input signal configured for analog input 1 in and has been triggered.


Remedy:

  • Check input signal at analog input 1.

  • Check configuration of the monitoring function.
0x20097082
Analog input 2 fault
Cause: The monitoring function of the input signal configured for analog input 2 in and has been triggered.


Remedy:

  • Check input signal at analog input 2.

  • Check configuration of the monitoring function.
0x200970B0
Connected network option is not supported
Cause: The network option plugged into the inverter is not supported by the firmware.


Remedy:

  • Update the firmware to a version that supports the network option.

  • Use the network option supported by the current firmware version.
0x20097121
Fault – Pole position identification
Cause:

  • Too many deviations during the pole position identification.

  • Compared to the inverter, the rated motor current is too high or too low.




Remedy:

  • Check setting of the motor data.

  • Ensure that the motor is at a standstill during the pole position identification process.

  • Ensure that the motor and inverter match each other in terms of power.
0x20097303
Fault – Motor feedback
Cause: Defective encoder cable. Defective encoder.


Remedy:

  • Check encoder cable.

  • Check encoder.

  • Switch off monitoring if no encoder is used.
0x20097304
Error – Load encoder/master encoder
Cause: Defective encoder cable. Defective encoder.


Remedy:

  • Check encoder cable.

  • Check encoder.

  • Switch off monitoring if no encoder is used.
0x20097380
Motor encoder – Communication error
Cause: The communication to an encoder is disturbed.


Remedy:

  • Check the supply voltage of the encoder (0x2C42:002).

  • Check encoder cable.
0x20097381
Motor encoder – wrong absolute value because motor speed is too high
Cause: The absolute encoder position cannot be accepted as the motor rotates too fast.


Remedy:

  • Let the motor coast.
0x20097382
Load encoder/master encoder – Communication error
Cause: The communication to an encoder is disturbed.


Remedy:

  • Check the supply voltage of the encoder (0x2C42:002).

  • Check encoder cable.
0x20097383
Load encoder/master encoder – wrong absolute value
Cause: The absolute encoder position cannot be accepted as the motor rotates too fast.


Remedy:

  • Let the motor coast.
0x2009FF00
Fatal internal error
Cause: Internal error.


Remedy:

  • Restart the device.

  • If the error persists, contact the manufacturer.
0x2009FF02
Fault – Motor holding brake
Cause: Brake fault due to short circuit or cable break.


Remedy:

  • Check brake.

  • Check wiring.
0x2009FF05
Safe torque off (STO) activated
Cause: “Safe Torque Off (STO)” has been activated via Safety. The movement is interrupted although the controller is still enabled.


Remedy:

  • Enable “Safe Torque Off (STO)” again or disable controller.

  • In the event of false tripping, check the wiring at connection X1.
0x2009FF06
Motor overspeed
Cause: The motor speed has reached the error threshold for overspeed set in 0x2D44:001.


Remedy:

  • Adapt the maximum motor speed (0x6080) and the warning/error threshold (0x2D44:001).
0x2009FF09
Motor phase missing
Cause: A failure of several motor phases has been detected.


Remedy:

  • Check wiring between inverter and motor.

  • In case of a false tripping, adapt the settings for the motor phase failure detection.
0x2009FF0D
No resolver connected – command cannot be executed
Cause: An attempt was made to identify a resolver fault. But the V/f control without feedback system is selected as the control mode.


Remedy:

  • The resolver error can only be identified if a resolver is used as a feedback system.
0x2009FF12
Inverter error too large
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.
537526042 0x2009FF1A
Connected HIPERFACE® load encoder/master encoder is not supported
Cause: The HIPERFACE® encoder has a type code that is neither stored in the firmware nor corresponds to the type code set under 0x2C41:002.


Remedy:

  • Enter correct type code under 0x2C41:002.

  • Setting parameters: 0x2C51:004
537526043 0x2009FF1B
Connected HIPERFACE® load encoder/master encoder is not supported – command cannot be executed
Cause: The HIPERFACE® encoder has a type code that is not stored in the firmware. Hence, no data can be detected.


Remedy:

  • Connect an encoder with a supported type code.
537526044 0x2009FF1C
No resolver as load encoder/master encoder connected – command cannot be executed
Cause: An attempt was made to identify a resolver fault. But there is an encoder available as a feedback system.


Remedy:

  • The resolver error can only be identified if a resolver is used as a feedback system.
537526045 0x2009FF1D
No HIPERFACE® absolute value encoder as load encoder/master encoder connected – command cannot be executed
Cause: An attempt was made to read out HIPERFACE® data although no HIPERFACE® encoder is connected. No HIPERFACE® encoder is selected in 0x2C50.


Remedy:

  • Connect HIPERFACE® encoder.

  • A HIPERFACE® encoder must be selected in 0x2C50.
537526046 0x2009FF1E
FIQ runtime error
Cause: The monitoring of the FIQ by the FPGA has triggered.


Remedy:

  • Connect an encoder with a supported type code.
537526048 0x2009FF20
Brand protection – check failed
Cause: The review of brand protection has failed.


Remedy:

  • Enter correct pin.

  • Replace device with OEM device and reprogram pin.
537526049 0x2009FF21
Time-out holding brake feedforward control
Cause: The specified feedforward control torque could not be built up within one second.


Remedy:

  • Check 0x2820:009 (Starting torque source) = [0] (Last torque saved):

    • The load to be braked is too large.

    • Control the stored torque (0x2820:021).



  • Check 0x2820:009 (Starting torque source) = [1] (Torque in 0x2820:010):

    • The set torque is too high.

    • Reduce torque.
537526050 0x2009FF22
Velocity error
Cause: The speed error exceeds the limit from 0x2D51:001 for a time duration > 0x2D51:002.


Remedy:

  • Increase timeout in 0x2D51:002.

  • Increase limit in 0x2D51:001.

  • Increase gain of the speed controller.

  • Increase torque limit and/or current limit.
537526051 0x2009FF23
Position error
Cause: The following error exceeds the limit from 0x2D51:004 for a time duration > 0x2D51:005.


Remedy:

  • Increase timeout in 0x2D51:005.

  • Increase limit in 0x2D51:004.

  • Increase gain of the position controller.
537526054 0x2009FF26
Cable check – Motor movement too large
Cause: Phases in the motor cable reversed. The axis was moved manually. Motor parameters are set incorrectly. For synchronous motors: The pole position is set incorrectly. For motors with holding brake: The brake was opened prematurely by an external source.


Remedy:

  • Check motor cabling.

  • Avoid manual movement.

  • Check number of pole pairs and motor type.

  • Carry out the pole position identification.

  • Do not open the brake until you have checked the wiring.
537526055 0x2009FF27
Cable check – Wrong motor angle detected
Cause: The determined angle between rotor and resolver differs from the setting in 0x2C03:002. The determined angle between rotor and encoder differs from the setting in 0x2C03:004.


Remedy:

  • Check encoder cabling.

  • Check motor cabling.

  • If appropriate, Carry out the pole position identification.
537526062 0x2009FF2E
Connected motor encoder is not supported
Cause: Motor encoder configuration issue.


Remedy:

  • Connect a supported motor encoder or check configuration.
537526063 0x2009FF2F
Connected load encoder/master encoder is not supported
Cause: Load/Master encoder configuration issue.


Remedy:

  • Connect a supported load/master encoder or check configuration.
537526070 0x2009FF36
Warning – Brake resistor overload
Cause: The calculated thermal load of the brake resistor has reached the warning threshold set in 0x2550:008. The regenerative energy is too high.


Remedy:

  • Check drive dimensioning.

  • Check settings for the brake energy management.

  • Note: The warning status is reset if the thermal load falls below the warning threshold of -20 %.
537526076 0x2009FF3C
Backup created via device command
Cause: Backup created via device command.


Remedy:

  • For information only. No remedy necessary.
537526077 0x2009FF3D
Backup restored via device command
Cause: Backup restored via device command.


Remedy:

  • For information only. No remedy necessary.
537526080 0x2009FF40
Error – Brake transistor
Cause: The short-circuit monitoring of the brake transistor has triggered.


Remedy:

  • Use brake resistor with a greater resistance value.

  • Use external brake chopper.

  • Use regenerative module.
537526081 0x2009FF41
Error – Charging circuit
Cause: The monitoring of the charge relay has responded.


Remedy:

  • Acknowledge error. If the error persists, contact the manufacturer.
537526082 0x2009FF42
Mains phase failure
Cause: The mains phase monitoring has triggered.


Remedy:

  • Check mains connection.
537526083 0x2009FF43
Motor encoder requires restart of the device
Cause: Motor encoder configuration changed or error requires restart.


Remedy:

  • Restart the device.
537526084 0x2009FF44
Load encoder requires restart of the device
Cause: Load encoder configuration changed or error requires restart.


Remedy:

  • Restart the device.
537526096 0x2009FF50
General error (see manual)
Cause: An error has been triggered in the technology application, the PLC or in the network, which requires a direct error response from the drive.


Remedy:

  • Search logbook for the triggering error in the other component.

  • Eliminate the triggering error.

  • The error message can now be acknowledged. If this is not possible, contact the manufacturer.
537526097 0x2009FF51
Internal communication to PLC failed
Cause: The internal communication between the application and the base firmware is disturbed.


Remedy:

  • Restart device.
537526110 0x2009FF5E
Invalid module combination in slot A and slot B
Cause: The modules in slot A and slot B cannot be combined.


Remedy:

  • Remove a module.

  • Plug a valid module combination.

  • The event can only be reset by mains switching.
671158529 0x28011101
Initialization – Parameter value could not be written
Cause: Initialization – Parameter value could not be written.


Remedy:

  • For information only. No remedy necessary.
671158530 0x28011102
Load default setting – Parameter value could not be written
Cause: Write access denied with corresponding error message.


Remedy:

  • Evaluate parameter value based on the error message in the logbook.

  • Correct parameter value accordingly.
671158785 0x28011201
Parameters – Initialization failed
Cause: Not all parameters could be initialized.


Remedy:

  • See related entries in the logbook.
671158786 0x28011202
Parameters – Loading default values failed
Cause: Not all presets could be written.


Remedy:

  • See related entries in the logbook.
671158787 0x28011203
Parameters – Loading TA default values failed
Cause: Not all presets of the technology application could be written.


Remedy:

  • See related entries in the logbook.
671159298 0x28011402
Opening the parameter description failed
Cause: Parameter description is missing or faulty.


Remedy:

  • Update boot project or device firmware.
671159299 0x28011403
Opening the parameter set failed
Cause: Parameter set file is missing or faulty.


Remedy:

  • Update boot project or restart device.
671219713 0x28020001
Logbook: Corrupt restore data
Cause: Logbook: Corrupt restore data.


Remedy:

  • For information only. No remedy necessary.
671219773 0x2802003D
Logbook cleared
Cause: Logbook cleared.


Remedy:

  • For information only. No remedy necessary.
671219776 0x28020040
Logbook: Timeout restoring data
Cause: Logbook: Timeout restoring data.


Remedy:

  • For information only. No remedy necessary.
671219777 0x28020041
Logbook: Error restoring data
Cause: Logbook: Error restoring data.


Remedy:

  • For information only. No remedy necessary.
671219778 0x28020042
First boot with this firmware version
Cause: First boot with this firmware version.


Remedy:

  • For information only. No remedy necessary.
671219779 0x28020043
Logbook was restored
Cause: Logbook was restored.


Remedy:

  • For information only. No remedy necessary.
671219780 0x28020044
Logbook: Error reading persistent data
Cause: Logbook: Error reading persistent data.


Remedy:

  • For information only. No remedy necessary.
671263317 0x2802AA55
The chronology of the logbook is not consistent
Cause: The chronology of the logbook is not consistent.


Remedy:

  • For information only. No remedy necessary.
671354881 0x28041001
CmpLenzeErrorManagementAccess loaded without errors
Cause: CmpLenzeErrorManagementAccess loaded without errors.


Remedy:

  • For information only. No remedy necessary.
671420673 0x28051101
Test-Mode – More Application Credit required, application is starting delayed
Cause: The “Application-Credit” is not sufficient for the application. The start of the application is delayed.


Remedy:

  • Use SD card with sufficient “Application-Credit”.
671420674 0x28051102
Application-Credit – Invalid license data
Cause: Faulty license data was detected when the “Application-Credit” was loaded.


Remedy:

  • Use SD card with valid license data.
671420675 0x28051103
Application-Credit – License data missing
Cause: No license data was found on the SD card when then the “Application-Credit” was loaded.


Remedy:

  • Use SD card with valid license data.
671421185 0x28051301
Boot application – More Application Credit required
Cause: The “Application-Credit” is not sufficient for the boot application. Booting is delayed.


Remedy:

  • Use SD card with sufficient “Application-Credit”.
671809799 0x280B0107
Application was downloaded
Cause: Application was downloaded.


Remedy:

  • For information only. No remedy necessary.
704663680 0x2A005080
Internal error – AIS
Cause: Internal error.


Remedy:

  • Restart the device. If the error persists, replace the device.
704663681 0x2A005081
Internal error – AIE
Cause: Internal error.


Remedy:

  • Restart the device. If the error persists, replace the device.
704663682 0x2A005082
Internal error – Button S82
Cause: Internal error.


Remedy:

  • Restart the device. If the error persists, replace the device.
704663683 0x2A005083
IRS – Internal error
Cause: Internal error.


Remedy:

  • Restart the device. If the error persists, replace the device.
704663684 0x2A005084
IRL – Internal error
Cause: Internal error.


Remedy:

  • Restart the device. If the error persists, replace the device.
704663691 0x2A00508B
SD-Inx/CLx – Error
Cause: Internal error.


Remedy:

  • Restart the device. If the error persists, replace the device.
704663692 0x2A00508C
Internal switch-off path – Error
Cause: Internal error.


Remedy:

  • Restart the device. If the error persists, replace the device.
704663693 0x2A00508D
Internal switch-off path – Test pulse error
Cause: Internal error.


Remedy:

  • Restart the device. If the error persists, replace the device.
704663694 0x2A00508E
SBC – Test pulse error
Cause: Internal error.


Remedy:

  • Restart the device. If the error persists, replace the device.
704663695 0x2A00508F
SBC – Remains stuck at LOW
Cause: Error in the safe brake control.


Remedy:

  • Check the supply voltage of the brake.

  • Check the wiring of the brake.
704663696 0x2A005090
Faulty internal adjustment data
Cause: Internal error.


Remedy:

  • Restart the device. If the error persists, replace the device.
704663828 0x2A005114
Reference voltage error
Cause: Internal error.


Remedy:

  • Restart the device. If the error persists, replace the device.
704663829 0x2A005115
6 V voltage error
Cause: Internal error.


Remedy:

  • Restart the device. If the error persists, replace the device.
704663830 0x2A005116
5 V voltage error
Cause: Internal error.


Remedy:

  • Restart the device. If the error persists, replace the device.
704663831 0x2A005117
3.3 V voltage error
Cause: Internal error.


Remedy:

  • Restart the device. If the error persists, replace the device.
704668032 0x2A006180
Internal error – STO activated
Cause: Internal error.


Remedy:

  • Restart the device. If the error persists, replace the device.
704668037 0x2A006185
Communication error – Basic device
Cause: Internal error.


Remedy:

  • Restart the device. If the error persists, replace the device.
704668038 0x2A006186
Synchronization error – Basic device
Cause: Internal error.


Remedy:

  • Restart the device. If the error persists, contact the manufacturer.
704668039 0x2A006187
SBC – Device configuration incompatible
Cause: Device configuration incompatible.


Remedy:

  • Warning only. Check device configuration.
704668544 0x2A006380
F-parameter error
Cause: Error in the PROFIsafe parameter setting. The F-PLC is parameterized incorrectly.


Remedy:

  • Check PROFIsafe component.

  • Check network cable.

  • Analyze the error history of the higher-level controller.
704668545 0x2A006381
F_Dest_Add unequal F-address
Cause: The safety address F_Dest_Add in the higher-level controller and the F address in the device are different.


Remedy:

  • Adapt safety addresses.
704668546 0x2A006382
F_Dest_Add = 0 or FFFFhex
Cause: The safety address F_Dest_Add in the higher-level controller is invalid.


Remedy:

  • Adapt safety address.
704668547 0x2A006383
F_Source_Add = 0 or FFFFhex
Cause: The safety address F_Source_Add in the higher-level controller is invalid.


Remedy:

  • Adapt safety address.
704668548 0x2A006384
F_WD_Time = 0 ms
Cause: The monitoring time F_WD_Time in the higher-level controller is invalid.


Remedy:

  • Adapt parameter setting.
704668549 0x2A006385
F_SIL exceeds technical SIL
Cause: The SIL parameterized in the higher-level controller is greater than the technically possible SIL of the device.


Remedy:

  • Adapt parameter setting in the higher-level controller.
704668550 0x2A006386
F_CRC_Length error
Cause: The data length of the F_CRC in the higher-level controller is faulty.


Remedy:

  • Check safety parameter in the higher-level controller.
704668551 0x2A006387
Wrong F-parameter version
Cause: The F parameter version is not supported by the device.


Remedy:

  • Select supported F parameter version in the higher-level controller.
704668552 0x2A006388
F_Block_ID not supported
Cause: F_Block_ID not supported.


Remedy:

  • Information only.
704668553 0x2A006389
Safety parameter set deleted
Cause: Safety parameter set deleted.


Remedy:

  • For information only. No remedy necessary.
704668554 0x2A00638A
New safety parameter set loaded
Cause: New safety parameter set loaded.


Remedy:

  • For information only. No remedy necessary.
704668555 0x2A00638B
Memory module – Access error
Cause: Error accessing the safe parameter set on the SD card.


Remedy:

  • Reset safe parameter set in the device.

  • Reload safe parameter set.
704668556 0x2A00638C
Different safety parameter sets
Cause: The safe parameter sets on the SD card and in the device are different.


Remedy:

  • Load a safe parameter set from the SD card into the device.

  • Acknowledge modification with confirmation button S82.
704668557 0x2A00638D
Extended Safety – No safety parameter set
Cause: No safe parameter set was found in the device.


Remedy:

  • Load safe parameter set into the device.

  • Acknowledge modification with confirmation button S82.
704668558 0x2A00638E
Extended Safety – Safety parameter set defect
Cause: The safe parameter set in the device is faulty.


Remedy:

  • Load safe parameter set into the device.

  • Acknowledge modification with confirmation button S82.
704668559 0x2A00638F
Safety parameter set – Format error
Cause: Format error in the safe parameter set.


Remedy:

  • Reset the safe parameter set in the device and load it again.

  • Acknowledge modification with confirmation button S82.
704668560 0x2A006390
Safety parameter set – Plausibility error
Cause: The set safety parameters are not plausible.


Remedy:

  • Determine the error number in 0x2115:005 and analyze it using the table of plausibility errors.

  • Correct error.

  • Reload safe parameter set.

  • Acknowledge modification with confirmation button S82.
704668561 0x2A006391
Safety parameter set – Communication error
Cause: A communication error has occurred while loading the safe parameter set.


Remedy:

  • Check communication settings.

  • Check SD card.

  • Reload safe parameter set. Acknowledge modification with confirmation button S82.
704668562 0x2A006392
Different safety addresses detected
Cause: The safety addresses in the device and on the SD card are different.


Remedy:

  • Adapt safety addresses.

  • Reload safe parameter set. Acknowledge modification with confirmation button S82.
704668563
0x2A006393

SSM – Wrong PDO version
Cause:

Safe speed monitoring is faulty because the PDO version of the data protocol is incompatible.


Remedy:

Only devices with firmware > V1.0 support Extended Safety.
704668564
0x2A006394

Memory module release information – access error
Cause:

No release information is available on the memory module.


Remedy:

After transferring an application with the “Application Loader”, the release information for the safe parameter set must be generated separately for each device with the »EASY Starter« or »PLC Designer« via the +Safety parameter list+ and transferred to the device. After transmission, the safe parameter set must be saved in the device using the “Save” command.
704676234
0x2A00818A

PROFIsafe passivated
Cause:

Error in the PROFIsafe communication. PROFIsafe was passivated.


Remedy:

  • Check PROFIsafe component.

  • Check network cable.

  • Analyze the error history of the higher-level controller.
704676235
0x2A00818B

PROFIsafe has left data exchange
Cause:

Error in the PROFIsafe communication. PROFIsafe has left data exchange.


Remedy:

  • Check PROFIsafe component.

  • Check network cable.

  • Analyze the error history of the higher-level controller.
704676237
0x2A00818D

PROFIsafe – CRC1 error
Cause:

The F-Parameter-CRC is faulty.


Remedy:

  • Check F-Parameter-CRC (CRC1) in the higher-level controller.

  • Check device description file (GSDML).
704676238
0x2A00818e

PROFIsafe – Device specific error
Cause:

(See Severity/Response)


Remedy:

–
704676239
0x2A00818f

iParameters – Saving, watchdog expired
Cause:

(See Severity/Response)


Remedy:

–
704676245
0x2A008195

FSoE – Unexpected command
Cause:

Unexpected FSoE command received.


Remedy:

  • Check FSoE configuration.

  • Restart communication.
704676246
0x2A008196

FSoE – Unknown command
Cause:

Unknown FSoE command received.


Remedy:

  • Check FSoE configuration.

  • Restart communication.
704676247
0x2A008197

FSoE – Invalid connection ID
Cause:

FSoE frame with invalid connection ID received.


Remedy:

  • Check FSoE configuration.

  • Restart communication.
704676248
0x2A008198

FSoE – CRC error
Cause:

The check of the CRC in the FSoE frames reports errors.


Remedy:

  • Check FSoE configuration.

  • Restart communication.
704676249
0x2A008199

FSoE – Watchdog expired
Cause:

FSoE watchdog elapsed.


Remedy:

Check set watchdog time in FSoE master and adapt if necessary.
704676252
0x2A00819C

FSoE – Invalid communication parameter data
Cause:

Invalid communication parameter data received.


Remedy:

Check setting of the communication parameters.
704676253
0x2A00819D

FSoE – Invalid application parameter length
Cause:

The length of the application parameters transmitted by the FSoE master differs from the expected length.


Remedy:

Check setting of the communication parameters.
704676254
0x2A00819E

FSoE – Invalid application parameter data
Cause:

Invalid application parameter data received.


Remedy:

Check setting of the communication parameters.
704676255
0x2A00819F

FSoE – Passivated
Cause:

Due to an error, FSoE was passivated.


Remedy:

  • Check FSoE configuration.

  • Reset error.
704676264
0x2A0081A8

FSoE – Invalid slave address
Cause:

The slave address transmitted by the FSoE master differs from the slave address set in the device.


Remedy:

  • Check slave address in the FSoE master.

  • Check parameter setting in the device.
704676265
0x2A0081A9

FSoE – Invalid communication parameter length
Cause:

The length of the communication parameter transmitted by the FSoE master differs from the expected length.


Remedy:

Check setting of the communication parameters.
704676266
0x2A0081AA

FSoE – Data exchange left
Cause:

Due to an error FSoE has left the data exchange.


Remedy:

  • Check FSoE configuration.

  • Reset error.
704680064
0x2A009080

Discrepancy check or function check error – SD-In1
Cause:

Signal error at safe input SD-In1.


Remedy:

  • Check parameter setting.

  • Check wiring.
704680065
0x2A009081

Discrepancy check or function check error – SD-In2
Cause:

Signal error at safe input SD-In2.


Remedy:

  • Check parameter setting.

  • Check wiring.
704680066
0x2A009082

Discrepancy check or function check error – SD-In3
Cause:

Signal error at safe input SD-In3.


Remedy:

  • Check parameter setting.

  • Check wiring.
704680067
0x2A009083

Discrepancy check or function check error – SD-In4
Cause:

Signal error at safe input SD-In4.


Remedy:

  • Check parameter setting.

  • Check wiring.
704680068
0x2A009084

Disabled SD-In1 = HIGH
Cause:

Initialization error or parameterization error. HIGH level detected at the deactivated safe input.


Remedy:

  • Check parameter setting.

  • Check wiring.
704680069
0x2A009085

Disabled SD-In2 = HIGH
Cause:

Initialization error or parameterization error. HIGH level detected at the deactivated safe input.


Remedy:

  • Check parameter setting.

  • Check wiring.
704680070
0x2A009086

Disabled SD-In3 = HIGH
Cause:

Initialization error or parameterization error. HIGH level detected at the deactivated safe input.


Remedy:

  • Check parameter setting.

  • Check wiring.
704680071
0x2A009087

Disabled SD-In4 = HIGH
Cause:

Initialization error or parameterization error. HIGH level detected at the deactivated safe input.


Remedy:

  • Check parameter setting.

  • Check wiring.
704680072
0x2A009088

SD-Out1 – Channel A remains stuck at HIGH
Cause:

Channel A of SD_Out1 cannot be deactivated.


Remedy:

Check wiring for short circuit.
704680073
0x2A009089

SD-Out1 – Channel A remains stuck at LOW
Cause:

Channel A of SD_Out1 cannot be activated.


Remedy:

  • Check wiring.

  • Check supply voltage.
704680074
0x2A00908A

SD-Out1 – Channel B remains stuck at HIGH
Cause:

Channel B of SD_Out1 cannot be deactivated.


Remedy:

Check wiring for short circuit.
704680075
0x2A00908B

SD-Out1 – Channel B remains stuck at LOW
Cause:

Channel B of SD_Out1 cannot be activated.


Remedy:

  • Check wiring.

  • Check supply voltage.
704680076
0x2A00908C

SD-In1 – Channel A remains stuck at HIGH
Cause:

Channel A of SD_In1 cannot be deactivated.


Remedy:

  • Check wiring for short circuit.

  • Check configuration of the safe input.
704680077
0x2A00908D

SD-In1 – Channel B remains stuck at HIGH
Cause:

Channel B of SD_In1 cannot be deactivated.


Remedy:

  • Check wiring for short circuit.

  • Check configuration of the safe input.
704680078
0x2A00908E

SD-In2 – Channel A remains stuck at HIGH
Cause:

Channel A of SD_In2 cannot be deactivated.


Remedy:

  • Check wiring for short circuit.

  • Check configuration of the safe input.
704680079
0x2A00908F

SD-In2 – Channel B remains stuck at HIGH
Cause:

Channel B of SD_In2 cannot be deactivated.


Remedy:

  • Check wiring for short circuit.

  • Check configuration of the safe input.
704680080
0x2A009090

SD-In3 – Channel A remains stuck at HIGH
Cause:

Channel A of SD_In3 cannot be deactivated.


Remedy:

  • Check wiring for short circuit.

  • Check configuration of the safe input.
704680081
0x2A009091

SD-In3 – Channel B remains stuck at HIGH
Cause:

Channel B of SD_In3 cannot be deactivated.


Remedy:

  • Check wiring for short circuit.

  • Check configuration of the safe input.
704680082
0x2A009092

SD-In4 – Channel A remains stuck at HIGH
Cause:

Channel A of SD_In4 cannot be deactivated.


Remedy:

  • Check wiring for short circuit.

  • Check configuration of the safe input.
704680083
0x2A009093

SD-In4 – Channel B remains stuck at HIGH
Cause:

Channel B of SD_In4 cannot be deactivated.


Remedy:

  • Check wiring for short circuit.

  • Check configuration of the safe input.
704680084
0x2A009094

CLA/CLB – Short circuit
Cause:

Short circuit at the CLA/CLB clock outputs.


Remedy:

Check wiring.
704708488
0x2A00FF88

SS1/SS2 – Stop time exceeded
Cause:

The speed threshold “n = 0” was not reached within the stopping time.


Remedy:

  • Increase SS1/SS2- stopping time.

  • Reduce delay time in drive.
704708489
0x2A00FF89

SLS1 – Nlim1 exceeded
Cause:

The safely limited speed SLS1 has been exceeded.


Remedy:

  • Adapt the speed-dependent parameters in the drive.

  • Increase safely limited speed.
704708490
0x2A00FF8A

SLS2 – Nlim2 exceeded
Cause:

The safely limited speed SLS2 has been exceeded.


Remedy:

  • Adapt the speed-dependent parameters in the drive.

  • Increase safely limited speed.
704708491
0x2A00FF8B

SLS3 – Nlim3 exceeded
Cause:

The safely limited speed SLS3 has been exceeded.


Remedy:

  • Adapt the speed-dependent parameters in the drive.

  • Increase safely limited speed.
704708492
0x2A00FF8C

SLS4 – Nlim4 exceeded
Cause:

The safely limited speed SLS4 has been exceeded.


Remedy:

  • Adapt the speed-dependent parameters in the drive.

  • Increase safely limited speed.
704708493
0x2A00FF8D

SLS/SMS – Error stop not executed
Cause:

A safely limited speed (SLS1-SLS4) or the maximum speed (SMS) has been exceeded. The error was not reported within the parameterized response time.


Remedy:

  • Adapt the speed-dependent parameters in the drive.

  • Increase response time.
704708494
0x2A00FF8E

SDIpos – Wrong direction
Cause:

The drive has moved too far in the wrong direction.


Remedy:

  • Adapt the parameterization of the higher-level controller.

  • Increase 0x28BA:003 tolerance threshold.
704708495
0x2A00FF8F

SDIneg – Wrong direction
Cause:

The drive has moved too far in the wrong direction.


Remedy:

  • Adapt the parameterization of the higher-level controller.

  • Increase 0x28BA:003 tolerance threshold.
704708496
0x2A00FF90

SMS – Nmax exceeded
Cause:

The drive has exceeded the parameterized safe maximum speed (SMS).


Remedy:

Adapt the maximum speed in the drive.
704708497
0x2A00FF91

SOS – Tolerance limit exceeded
Cause:

The position change during SOS is greater than the parameterized tolerance window 0x289F:001.


Remedy:

  • Increase tolerance window.

  • Adapt response time of encoder monitoring.
704708498
0x2A00FF92

No feedback system configured
Cause:

An attempt was made to call up a speed-based or position-based safety function although no feedback is configured.


Remedy:

Configure suitable feedback.
704708499
0x2A00FF93

CAS – Round trip time exceeded
Cause:

The maximum allowed time between activation of the cascading and the feedback of the nodes was exceeded.


Remedy:

  • Set the input delay of SD-In4 0x211A:004 to ≤ 10 ms.

  • Check wiring between the nodes.
704708500
0x2A00FF94

CAS – Hardware or discrepancy error
Cause:

The hardware did not turn off the cascading output fast enough. A discrepancy error has occurred at the cascading input.


Remedy:

Check wiring between the nodes.
704708501
0x2A00FF95

SS1/SS2 – Speed ramp exceeded
Cause:

Ramp monitoring has responded because monitoring limits have been exceeded.


Remedy:

  • Adapt parameters for ramp monitoring (0x2894).

  • Deactivate ramp monitoring.
704708502
0x2A00FF96

SLI – Safely limited increment exceeded
Cause:

The maximum permissible position change (0x28CA:001, 0x28CA:003) was exceeded.


Remedy:

Adapt parameters for SLI.
704708503
0x2A00FF97

SLP1 – Position limits exceeded
Cause:

The upper or lower position limit of SLP1 has been exceeded.


Remedy:

  • Adapt parameters for SLP1.

  • Increase the distance to the position limits in the application.
704708504
0x2A00FF98

SLP2 – Position limits exceeded
Cause:

The upper or lower position limit of SLP2 has been exceeded.


Remedy:

  • Adapt parameters for SLP2.

  • Increase the distance to the position limits in the application.
704708505
0x2A00FF99

SLP3 – Position limits exceeded
Cause:

The upper or lower position limit of SLP3 has been exceeded.


Remedy:

  • Adapt parameters for SLP3.

  • Increase the distance to the position limits in the application.
704708506
0x2A00FF9A

SLP4 – Position limits exceeded
Cause:

The upper or lower position limit of SLP4 has been exceeded.


Remedy:

  • Adapt parameters for SLP4.

  • Increase the distance to the position limits in the application.
704708507
0x2A00FF9B

SLP – No home position
Cause:

SLP has been commissioned, but the home position is unknown.


Remedy:

Check status of the safe reference (0x2882:006).
704708509
0x2A00FF9D

PDSS – Velocity exceeded
Cause:

The drive has exceeded the current allowed speed for PDSS.


Remedy:

  • Check parameters for PDSS.

  • Reduce speeds in the application.

  • Increase distance to PDSS limit values.
704708510
0x2A00FF9E

PDSS – Creep velocity SCS exceeded
Cause:

The drive has exceeded the currently permitted SCS creeping speed.


Remedy:

  • Check parameters for PDSS.

  • Reduce speeds in the application.

  • Increase distance to PDSS limit values.
704708511
0x2A00FF9F

PDSS – No diagnostic mark detected
Cause:

No diagnostic marker for PDSS was detected.


Remedy:

  • Adapt parameters for the diagnostic marker.

  • Check the function of the diagnostic sensors.

  • Correct position of the diagnostic sensors.
704708512
0x2A00FFA0

PDSS – Diagnostic mark detected at invalid position
Cause:

A diagnostic marker for PDSS was detected at an invalid position.


Remedy:

  • Adapt parameters for the diagnostic marker.

  • Correct position of the diagnostic sensors.
704708518
0x2A00FFA6

SHom – Time-out
Cause:

After SHom_Start, the home position was not detected within the timeout set in 0x2882:002.


Remedy:

  • Adapt timeout.

  • Check configuration of triggers for SHom_Start and SHom_Load.
704708519
0x2A00FFA7

SHom – Home position deleted
Cause:

The home position was deleted by acknowledging a position error or manually via 0x2114:014.


Remedy:

Execute SHom again.
704708520
0x2A00FFA8

SHom – Maximum slip value exceeded
Cause:

The maximum permissible slip has been exceeded.


Remedy:

  • Evaluate slip monitoring in 0x2870:2.

  • Check the wear-prone drive components and replace them if necessary.
704708521
0x2A00FFA9

SHom – Tolerance of start position exceeded
Cause:

The tolerance for the starting position has been exceeded.


Remedy:

  • Do not move drive components while the mains voltage is switched off.

  • Execute SHom again.
704708522
0x2A00FFAA

SHom – Tolerance of position comparison exceeded
Cause:

The tolerance for the position comparison has been exceeded.


Remedy:

  • Check gearbox factor and mounting direction.

  • Check the wear-prone drive components and replace them if necessary.

  • Execute SHom again.
704708523
0x2A00FFAB

SSM – Invalid safe velocity
Cause:

No safe speed could be determined. The encoder is not initialized or the status transmitted by the encoder is invalid.


Remedy:

  • Check encoder.

  • A certified motor/encoder combination must be used.
704708524
0x2A00FFAC

SSM – Encoder error
Cause:

The monitoring of the safe speed via encoder is faulty.


Remedy:

  • Check encoder.

  • Check configuration of the encoder.
704708525
0x2A00FFAD

SSM – Resolver error
Cause:

The monitoring of the safe speed via resolver is faulty.


Remedy:

  • Check encoder.

  • Check configuration of the encoder.
704708526
0x2A00FFAE

SSM – Error in standard device data
Cause:

Safe speed monitoring is faulty because the device is transmitting incorrect data.


Remedy:

  • Check encoder.

  • Check configuration of the encoder.
704708527
0x2A00FFAF

SSM – Speed deviation too high
Cause:

The difference between the internally calculated speed and the speed transmitted by the encoder is too large.


Remedy:

  • Check configuration of the encoder.

  • Check gearbox factor.

  • Check tolerance for the deviation.
704708528
0x2A00FFB0

SSM – Synchronization error
Cause:

Internal error.


Remedy:

Restart the device. If the error persists, contact the manufacturer.
704708529
0x2A00FFB1

MUT – Muting function active
Cause:

MUT – Muting function active


Remedy:

For information only. No remedy necessary.
704708530
0x2A00FFB2

MUT – Muting function completed
Cause:

MUT – Muting function completed


Remedy:

For information only. No remedy necessary.
704708531
0x2A00FFB3

MUT – Muting function aborted
Cause:

Communication error. The muting function was canceled.


Remedy:

  • Reconnect to the device.

  • Restart the muting function.
704708536 0x2A00FFB8

HDSL encoder – ID was set
Cause: The encoder ID of the connected HIPERFACE DSL® encoder has been set to the correct value. The error “Different encoder ID” has been fixed. The status bit has been reset: 0x2878:050, bit 13.



Remedy: Check whether the encoder-axis assignment is now correct.
805306384 0x30000010

Internal error
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805306385 0x30000011

Internal error
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805306386 0x30000012

Internal error
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805306387 0x30000013

Internal error
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805306570 0x300000CA

Internal error
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805306571 0x300000CB

Internal error
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311368 0x30001388

Internal error
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311369 0x30001389

CTRL – Feature not supported
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311370 0x3000138A

CTRL – Invalid index
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311371 0x3000138B

ISW – Invalid offset
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311373 0x3000138D

CTRL – Invalid size
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311374 0x3000138E

ISW – Invalid data
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311375 0x3000138F

ISW – Not ready
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311376 0x30001390

CTRL – Busy
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311377 0x30001391

ISW – Cannot queue acyclic EtherCAT command
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311378 0x30001392

CFG – No memory left
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311379 0x30001393

CTRL – Invalid parameter
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311380 0x30001394

CTRL – Not found
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311382 0x30001396

ISW – Invalid state
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311383 0x30001397

ISW – Cannot add slave to timer list
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311384 0x30001398

SLV – Time-out
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311385 0x30001399

ISW – Open failed
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311386 0x3000139A

LLA – Send failed
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311387 0x3000139B

CFG – Error when queuing a mailbox command
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311388 0x3000139C

ISW – Invalid mailbox command
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311389 0x3000139D

ISW – Unknown mailbox protocol command
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311390 0x3000139E

ISW – Access denied
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311394 0x300013A2

CFG – Invalid product key
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311395 0x300013A3

PRJ – Wrong format of master XML file
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311396 0x300013A4

CTRL – Function disabled
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311398 0x300013A6

PRJ – Mismatch of bus configuration and number of connected slaves
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311399 0x300013A7

PRJ – Error reading master XML file
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311401 0x300013A9

PRJ – Configurator error – cyclic commands are missing in master XML file
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311402 0x300013AA

PRJ – AL_STATUS register read command is missing in master XML file
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311403 0x300013AB

ISW – Fatal internal McSm error
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311404 0x300013AC

SLV – Slave error
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311405 0x300013AD

SLV – Frame lost, IDX mismatch
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311406 0x300013AE

SLV – At least one EtherCAT command is missing in the received frame
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311408 0x300013B0

CTRL – IOCTL EC_IOCTL_DC_LATCH_REQ_LTIMVALS not possible in DC Latching auto read mode
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311409 0x300013B1

SLV – Auto increment address – increment mismatch (slave missing)
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311410 0x300013B2

CTRL – Slave in invalid state, e.g. not in OP (API not callable in this state)
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311411 0x300013B3

SLV – Fixed station address lost or slave missing – FPRD to AL_STATUS failed
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311412 0x300013B4

PRJ – Too many cyclic commands in XML configuration file
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311414 0x300013B6

RAP – Master core not accessible
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311415 0x300013B7

SLV – COE mailbox send – WKC error
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311416 0x300013B8

SLV – COE mailbox receive – WKC error
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311417 0x300013B9

CTRL – No mailbox support
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311418 0x300013BA

CoE – Protocol not supported
Cause: Slave does not support CoE.



Remedy: Use slave that supports CoE.
805311419 0x300013BB

PRJ – EoE protocol not supported
Cause: Slave does not support EoE.



Remedy: Use slave that supports EoE.
805311420 0x300013BC

FoE . Protocol not supported
Cause: Slave does not support FoE.



Remedy: Use slave that supports FoE.
805311421 0x300013BD

PRJ – SoE protocol not supported
Cause: Slave does not support SoE.



Remedy: Use slave that supports SoE.
805311422 0x300013BE

PRJ – VoE protocol not supported
Cause: Slave does not support VoE.



Remedy: Use slave that supports VoE.
805311423 0x300013BF

PRJ – Configuration violates evaluation limits
Cause: Not specified.



Remedy: Not specified.
805311424 0x300013C0

CFG – Evaluation time expired
Cause: Not specified.



Remedy: Not specified.
805311431 0x300013C7

COE – invalid slave state
Cause: The slave status is invalid.



Remedy: Check if slave is at least PreOperational. Check other access rights.
805311432 0x300013C8

CoE – SDO Abort ‘Toggle bit not alternated (0x05030000)’
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311433 0x300013C9

CoE – SDO Abort ‘SDO protocol time-out (0x05040000)’
Cause: SDO protocol timeout



Remedy: Check if timeout is set too low.
805311434 0x300013CA

CoE – SDO Abort ‘Client/server command specifier not valid or unknown (0x05040001)’
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311435 0x300013CB

CoE – SDO Abort ‘Invalid block size (block mode only) (0x05040002)’
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311436 0x300013CC

CoE – SDO Abort ‘Invalid sequence number (block mode only) (0x05040003)’
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311437 0x300013CD

CoE – SDO Abort ‘CRC error (block mode only) (0x05040004)’
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311438 0x300013CE

CoE – SDO Abort ‘Out of memory (0x05040005)’
Cause: Internal error



Remedy: Restart the device. If the error persists, contact the manufacturer.
805311439 0x300013CF

CoE – SDO Abort ‘Unsupported access to an object (0x06010000)’
Cause: Access denied.



Remedy: Check access authorization.
805311440 0x300013D0

CoE – SDO Abort ‘Attempt to read a write only object (0x06010001)’
Cause: Access denied.



Remedy: Check access authorization.
805311441 0x300013D1

CoE – SDO Abort ‘Attempt to write a read only object (0x06010002)’
Cause: Access denied.



Remedy: Check access authorization.
805311442 0x300013D2

CoE – SDO-Abort ‘Object does not exist in the object dictionary (0x06020000)’
Cause: Access denied.



Remedy: Check access authorization. Check if object exists.
805311443 0x300013D3

CoE – SDO Abort ‘Object cannot be mapped to the PDO (0x06040041)’
Cause: Access denied.



Remedy: Check access authorization. Check if object exists.
805311444 0x300013D4

CoE – SDO Abort ‘Number and length of objects to be mapped exceed PDO length (0x06040042)’
Cause: Access denied.



Remedy: Check the length of the objects to be mapped.
805311445 0x300013D5

CoE – SDO Abort ‘General parameter incompatibility (0x06040043)’
Cause: Access denied.



Remedy: Check access authorization.
805311446 0x300013D6

CoE – SDO Abort ‘General internal incompatibility in the device (0x06040047)’
Cause: Access denied.



Remedy: Check access authorization.
805311447 0x300013D7

CoE – SDO Abort ‘Access failed due to an hardware error (0x06060000)’
Cause: Access denied.



Remedy: Check access authorization. Check object properties.
805311448 0x300013D8

CoE – SDO Abort ‘Data type or length of service parameters do not match (0x06070010)’
Cause: Access denied.



Remedy: Check access authorization. Check object properties.
805311449 0x300013D9

CoE – SDO Abort ‘Data type does not match, service parameter too high (0x06070012)’
Cause: Access denied.



Remedy: Check access authorization. Check object properties.
805311450 0x300013DA

CoE – SDO Abort ‘Data type does not match, service parameter too low (0x06070013)’
Cause: Access denied.



Remedy: Check access authorization. Check object properties.
805311451 0x300013DB

CoE – SDO Abort ‘Subindex does not exist (0x06090011)’
Cause: Access denied.



Remedy: Check access authorization. Check object properties.
805311452 0x300013DC

CoE – SDO Abort ‘Write access – Parameter value exceeds limits (0x06090030)’
Cause: Access denied.



Remedy: Check access authorization. Check object properties.
805311453 0x300013DD

CoE – SDO Abort ‘Write access – Parameter value too high (0x06090031)’
Cause: Access denied.



Remedy: Check access authorization. Check object properties.
805311454 0x300013DE

CoE – SDO Abort ‘Write access – Parameter value too low (0x06090032)’
Cause: Access denied.



Remedy: Check access authorization. Check object properties.
805311455 0x300013DF

CoE – SDO Abort ‘Maximum value less than minimum value (0x06090036)’
Cause: Access denied.



Remedy: Check access authorization. Check object properties.
805311456 0x300013E0

CoE – SDO Abort ‘General error (0x08000000)’
Cause: Access denied.



Remedy: Check access authorization. Check object properties.
805311457 0x300013E1

CoE – SDO Abort ‘Data cannot be transferred/stored in application (0x08000020)’
Cause: Access denied.



Remedy: Check access authorization. Check object properties.
805311458 0x300013E2

CoE – SDO Abort ‘Local control – Data cannot be transferred/stored in application (0x08000021)’
Cause: Access denied.



Remedy: Check access authorization. Check object properties.
805311459 0x300013E3

CoE- SDO Abort ‘Actual device state – Data cannot be transferred/stored in application (0x08000022)’
Cause: Access denied.



Remedy: Check access authorization. Check object properties.
805311460 0x300013E4

CoE – SDO Abort ‘Object dictionary – Dynamic generation fails or object dictionary is missing (0x08000023)’
Cause: Access denied.



Remedy: Check access authorization. Check object properties.
805311461 0x300013E5

CoE – SDO Abort ‘Unknown abort code’
Cause: Access denied.



Remedy: Check access authorization. Check object properties.
805311462 0x300013E6

CoE – Invalid parameter
Cause: Access denied.



Remedy: Check access authorization. Check object properties. Check transfer properties.
805311463 0x300013E7

CoE – CoE protocol not supported
Cause: Access denied.



Remedy: Check access authorization. Check object properties. Check transfer properties.
805311464 (0x300013E8)

CoE – Unknown FoE error
Cause: Access denied.


Remedy: Check access authorization. Check file. Check transfer properties.
805311465 (0x300013E9)

CoE – FoE error ‘Not found’
Cause: Access denied.


Remedy: Check access authorization. Check file. Check transfer properties.
805311466 (0x300013EA)

CoE – FoE error ‘Access denied’
Cause: Access denied.


Remedy: Check access authorization. Check file. Check transfer properties.
805311467 (0x300013EB)

CoE – FoE error ‘Disk full’
Cause: Access denied.


Remedy: Check access authorization. Check file. Check transfer properties.
805311468 (0x300013EC)

CoE – FoE error ‘Illegal’
Cause: Access denied.


Remedy: Check access authorization. Check file. Check transfer properties.
805311469 (0x300013ED)

CoE – FoE error ‘Wrong packet number’
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311470 (0x300013EE)

CoE – FoE error ‘Already existing’
Cause: Access denied.


Remedy: Check access authorization. Check file. Check transfer properties.
805311471 (0x300013EF)

CoE – FoE error ‘User missing’
Cause: Access denied.


Remedy: Check access authorization. Check file. Check transfer properties.
805311472 (0x300013F0)

CoE – FoE error ‘Only possible in bootstrap’
Cause: Access denied.


Remedy: Check access authorization. Check file. Check transfer properties.
805311473 (0x300013F1)

CoE – FoE error ‘No bootstrap’
Cause: Access denied.


Remedy: Check access authorization. Check file. Check transfer properties.
805311474 (0x300013F2)

CoE – FoE error ‘No access rights’
Cause: Access denied.


Remedy: Check access authorization. Check file. Check transfer properties.
805311475 (0x300013F3)

CoE – FoE error ‘Program error’
Cause: Access denied.


Remedy: Check access authorization. Check object properties.
805311476 (0x300013F4)

CoE – FoE error ‘Invalid parameter’
Cause: Access denied.


Remedy: Check access authorization. Check file. Check transfer properties.
805311480 (0x300013F8)

CTRL – Master configuration not found
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311481 (0x300013F9)

SLV – Command error while EEPROM upload
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311482 (0x300013FA)

SLV – Command error while EEPROM download
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311483 (0x300013FB)

PRJ – Cyclic command too long
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311484 (0x300013FC)

PRJ – Invalid input offset in cyc cmd, please check InputOffs
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311485 (0x300013FD)

PRJ – Invalid output offset in cyc cmd, please check OutputOffs
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311753 (0x30001509)

RAP – Invalid cookie
Cause:


Remedy:
805311754 (0x3000150A)

RAP – Watchdog expired
Cause:


Remedy:
805311755 (0x3000150B)

RAP – Connecting 2nd server denied, multi server support is disabled
Cause:


Remedy:
805311756 (0x3000150C)

RAP – Logon aborted
Cause:


Remedy:
805311757 (0x3000150D)

RAP – Invalid version
Cause:


Remedy:
805311769 (0x30001519)

RAP – Server stopped
Cause:


Remedy:
805311770 (0x3000151A)

RAP – Watchdog expired
Cause:


Remedy:
805311771 (0x3000151B)

RAP – Reconnect time expired
Cause:


Remedy:
805311772 (0x3000151C)

RAP – Client logged on
Cause:


Remedy:
805311773 (0x3000151D)

RAP – Client reconnected
Cause:


Remedy:
805311774 (0x3000151E)

RAP – Socket changed after reconnect
Cause:


Remedy:
805311817 (0x30001549)

DCM – Init function not called or call not successful
Cause:


Remedy:
805311818 (0x3000154A)

DCM – Controller error – synchronization out of limit
Cause:


Remedy:
805311819 (0x3000154B)

DCM – Not enough memory
Cause:


Remedy:
805311820 (0x3000154C)

DCM – Hardware layer – (BSP) invalid
Cause:


Remedy:
805311821 (0x3000154D)

DCM – Hardware layer – Error while modifying the timer
Cause:


Remedy:
805311822 (0x3000154E)

DCM – Hardware layer – Timer is not running
Cause:


Remedy:
805311823 (0x3000154F)

DCM – Hardware layer – Function is called on wrong CPU
Cause:


Remedy:
805311881 (0x30001589)

EtherCAT – State change of master successful
Cause: EtherCAT – State change of master successful.


Remedy: For information only. No remedy necessary.
805311882 (0x3000158A)

EtherCAT – Bus scan successful
Cause: EtherCAT – Bus scan successful.


Remedy: For information only. No remedy necessary.
805311883 (0x3000158B)

EtherCAT – Bus scan error
Cause: Error in the network topology.


Remedy: Check network topology.
805311884 (0x3000158C)

EtherCAT – Distributed clocks state
Cause:


Remedy:
805311885 (0x3000158D)

EtherCAT – Distributed clocks – Latching state
Cause:


Remedy:
805311886 (0x3000158E)

CoE – SDO download failure
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311887 (0x3000158F)

CoE – SDO upload failure
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311888 (0x30001590)

CoE – OD-list upload failure
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311889 (0x30001591)

CoE – Object description upload failure
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311890 (0x30001592)

CoE – Object entry description upload failure
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311891 (0x30001593)

CoE – Emergency transfer failure
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311892 (0x30001594)

CoE – Emergency request
Cause: Internal error during transmission of emergency messages.


Remedy: Check the documentation of the slave device for this emergency message. Detailed information about the coding of error messages can be found in the documentation of the corresponding slave device/module.
805311893 (0x30001595)

Cyclic command WKC error
Cause: WKC error.


Remedy: Check slave status. Check network topology.
805311894 (0x30001596)

Master init command WKC error
Cause: WKC error.


Remedy: Check slave status. Check network topology.
805311895 (0x30001597)

Slave init command WKC error
Cause: WKC error.


Remedy: Check slave status. Check network topology.
805311896 (0x30001598)

EoE receive WKC error
Cause: WKC error.


Remedy: Check slave status. Check network topology.
805311897 (0x30001599)

CoE receive WKC error
Cause: WKC error.


Remedy: Check slave status. Check network topology.
805311898 (0x3000159A)

FoE receive WKC error
Cause: WKC error.


Remedy: Check slave status. Check network topology.
805311899 (0x3000159B)

SoE receive – WKC error
Cause: WKC error.


Remedy: Check slave status. Check network topology.
805311900 (0x3000159C)

EoE send WKC error
Cause: WKC error.


Remedy: Check slave status. Check network topology.
805311901 (0x3000159D)

CoE send WKC error
Cause: WKC error.


Remedy: Check slave status. Check network topology.
805311902 (0x3000159E)

FoE send WKC error
Cause: WKC error.


Remedy: Check slave status. Check network topology.
805311903 (0x3000159F)

SoE send – WKC error
Cause: WKC error.


Remedy: Check slave status. Check network topology.
805311904 (0x300015A0)

Retry sending a frame
Cause:


Remedy:
805311905 (0x300015A1)

Response on Ethernet frame
Cause:


Remedy:
805311906 (0x300015A2)

Additional error information
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311907 (0x300015A3)

EtherCAT command – IDX actual value
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311908 (0x300015A4)

EtherCAT command – IDX set value
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311909 (0x300015A5)

Init command response error – No response
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311910 (0x300015A6)

Init command response error – Validation error
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311911 (0x300015A7)

Init command response error – Failed
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311912 (0x300015A8)

Master init command response error – No response
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311913 (0x300015A9)

Master init command response error – Validation error
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311914 (0x300015AA)

Missing EtherCAT command in Ethernet frame
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311915 (0x300015AB)

Mailbox init command timeout
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311916 (0x300015AC)

At least one EtherCAT slave not in ‘Operational’
Cause: Master is “Operational”. At least one slave is not “Operational”.


Remedy: Check slave status. Check network topology.
805311917 (0x300015AD)

EtherCAT cable connected
Cause: EtherCAT cable connected.


Remedy: For information only. No remedy necessary.
805311918 (0x300015AE)

EtherCAT cable not connected
Cause: Network cabling is faulty.


Remedy: Check network cabling.
805311919 (0x300015AF)

Cyclic commands – Time-out
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311920 (0x300015B0)

Redundant operation – Ethernet cable is missing at 2nd EtherCAT interface
Cause: Network cabling is faulty.


Remedy: Check network cabling.
805311921 (0x300015B1)

At least one slave is in state ‘Error’
Cause: At least one slave is in the “Error” state.


Remedy: Check slave status. Check network topology.
805311922 (0x300015B2)

Slave error
Cause: A slave reports an error.


Remedy: Analyze detailed error message in the logbook. Check slave status. Check network topology.
805311923 (0x300015B3)

Communication to device interrupted
Cause: The connection to the slave is interrupted. The slave does not respond. The slave is no longer available.


Remedy: Check slave status. Check network topology.
805311924 (0x300015B4)

SDO abort
Cause: CoE access denied.


Remedy: Analyze detailed error message in the logbook. Check object properties. Check transfer properties.
805311925 (0x300015B5)

DC slaves are ‘in-sync’
Cause: DC slaves are ‘in-sync’.


Remedy: For information only. No remedy necessary.
805311926 (0x300015B6)

DC slaves are ‘out-of-sync’
Cause: The DC deviation is outside the permissible limits.


Remedy: Check slave status. Check slave properties. Check network topology.
805311927 (0x300015B7)

DC single latch on slave
Cause: Internal message.


Remedy: For information only. No remedy necessary.
805311928 (0x300015B8)

MbxTferRcv – file upload failure
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311929 (0x300015B9)

MbxTferRcv – file download failure
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311930 (0x300015BA)

Client registration lost
Cause: Internal error.


Remedy: Restart the device. If the error persists, contact the manufacturer.
805311931 (0x300015BB)

Redundant operation – Ethernet cable connected
Cause:


Remedy:
805311932 (0x300015BC)

SoE write error init command mbox
Cause:


Remedy:
805311960 (0x300015D8)

Hot Connect – all groups detected
Cause:
N/A (Warning only)


Remedy:
N/A
805311961 (0x300015D9)

Hot Connect – all group errors detected
Cause:
N/A (Warning only)


Remedy:
N/A
805311962 (0x300015DA)

Slave removed from bus
Cause:
A slave has been removed from the network topology.


Remedy:
For information only. No remedy necessary.
805311963 (0x300015DB)

Slave added to bus
Cause:
A slave has been added to the network topology.


Remedy:
For information only. No remedy necessary.
805311964 (0x300015DC)

Topology was changed
Cause:
The network topology has been changed.


Remedy:
For information only. No remedy necessary.
805311965 (0x300015DD)

Port closed
Cause:
“Border Close” has been executed on the port.


Remedy:
Analyze detailed error message in the logbook.
805311966 (0x300015DE)

MbxTferRcv – Write IDN failure
Cause:
IDN – Write error.


Remedy:
Analyze detailed error message in the logbook.
805311967 (0x300015DF)

MbxTferRcv – Read IDN failure
Cause:
IDN – read error.


Remedy:
Analyze detailed error message in the logbook.
805311968 (0x300015E0)

SoE – Emergency transfer failure
Cause:
SoE – emergency transfer error.


Remedy:
Analyze detailed error message in the logbook.
805311969 (0x300015E1)

SoE – Emergency request
Cause:
SoE – emergency request.


Remedy:
Analyze detailed error message in the logbook.
805311970 (0x300015E2)

SoE – Notification transfer failure
Cause:
SoE – transfer error during a notification.


Remedy:
Analyze detailed error message in the logbook.
805311971 (0x300015E3)

SoE – Notification request
Cause:
SoE – notification has been requested.


Remedy:
Analyze detailed error message in the logbook.
805311972 (0x300015E4)

FoE abort
Cause:
FoE has been aborted.


Remedy:
Check file. Check transfer properties. Analyze detailed error message in the logbook.
805312069 (0x30001645)

Bus scan state
Cause:
Bus scan state.


Remedy:
For information only. No remedy necessary.
805312071 (0x30001647)

Latch/Edge – No edge
Cause:
No edge.


Remedy:
Analyze detailed error message in the logbook.
805312072 (0x30001648)

Remote API diagnosis port – Connection established
Cause:
Remote API diagnosis port – Connection established.


Remedy:
For information only. No remedy necessary.
805312073 (0x30001649)

Remote API diagnosis port – Connection disconnected
Cause:
Remote API diagnosis port – Connection disconnected.


Remedy:
For information only. No remedy necessary.
805312074 (0x3000164A)

Client registered from cookie
Cause:
Client has registered with cookie.


Remedy:
Analyze detailed error message in the logbook.
805312075 (0x3000164B)

Client unregistered from cookie
Cause:
Client logged out from cookie.


Remedy:
Analyze detailed error message in the logbook.
805312076 (0x3000164C)

Unknown notification
Cause:
Internal error.


Remedy:
Restart the device. If the error persists, contact the manufacturer.
805312077 (0x3000164D)

Slave latched
Cause:
Internal error.


Remedy:
Restart the device. If the error persists, contact the manufacturer.
805312078 (0x3000164E)

Bus scan – Error
Cause:
Internal error.


Remedy:
Restart the device. If the error persists, contact the manufacturer.
805312079 (0x3000164F)

Invalid number of slaves
Cause:
The number of detected slaves differs from the number of expected slaves.


Remedy:
Analyze detailed error message in the logbook. Check network topology.
805312080 (0x30001650)

Cannot get SlaveInfo
Cause:
Internal error.


Remedy:
Restart the device. If the error persists, contact the manufacturer.
805312081 (0x30001651)

Deviation of slave
Cause:
Internal error.


Remedy:
Restart the device. If the error persists, contact the manufacturer.
805312082 (0x30001652)

Slave is not configured
Cause:
The slave is not configured.


Remedy:
Check slave status. Check network topology.
805312083 (0x30001653)

SlaveInfo
Cause:
Internal error.


Remedy:
Restart the device. If the error persists, contact the manufacturer.
805312084 (0x30001654)

SLV – Error retrieving configuration data
Cause:
Internal error.


Remedy:
Restart the device. If the error persists, contact the manufacturer.
805312085 (0x30001655)

Bus scan – Deviation
Cause:
Internal error.


Remedy:
Restart the device. If the error persists, contact the manufacturer.
805312086 (0x30001656)

Communication to device interrupted
Cause:
Communication interruption.


Remedy:
Check slave status. Check network topology.
805312087 (0x30001657)

Slave is not in expected status
Cause:
Detected slave status differs from expected slave status.


Remedy:
Analyze detailed error message in the logbook. Check slave status. Check network topology.
805312090 (0x3000165A)

Wrong response on ‘configured fix address request’ for slave
Cause:
Wrong response to the request.


Remedy:
Check slave status. Check network topology.
805312091 (0x3000165B)

Wrong response on ‘alias address’ request for slave
Cause:
Wrong response to the request.


Remedy:
Check slave status. Check network topology.
805312092 (0x3000165C)

Cannot execute EC_IOCTL_DC_SLV_SYNC_DEVLIMIT_GET
Cause:
The command cannot be executed.


Remedy:
Analyze detailed error message in the logbook.
805312093 (0x3000165D)

Cannot read latch timer
Cause:
Read error.


Remedy:
Analyze detailed error message in the logbook.
805312094 (0x3000165E)

Cannot execute EC_IOCTL_DC_SLV_SYNC_RESTART
Cause:
The command cannot be executed.


Remedy:
Analyze detailed error message in the logbook.
805312097 (0x30001661)

RAP – Invalid parameter size
Cause:
RAP – Invalid parameter size.


Remedy:
For information only. No remedy necessary.
805312098 (0x30001662)

RAP – Marshaling error
Cause:
Order error.


Remedy:
Analyze detailed error message in the logbook.
805312099 (0x30001663)

Unable to enqueue (missing calls to ProcessNotificationJobs)
Cause:
N/A (Warning only)


Remedy:
N/A
805312100 (0x30001664)

No connection to slaves
Cause:
Possibly the network cable is missing.


Remedy:
Check slave status. Check network topology.
805312101 (0x30001665)

ecatSetTargetState cannot set EtherCAT master into target state, master is busy (time-out)
Cause:
Internal error.


Remedy:
Restart the device. If the error persists, contact the manufacturer.
805312102 (0x30001666)

ecatStop() returns ‘Busy’, retry…
Cause:
Internal error.


Remedy:
Restart the device. If the error persists, contact the manufacturer.
805312103 (0x30001667)

Mailbox transfer request – Error
Cause:
Internal error.


Remedy:
Restart the device. If the error persists, contact the manufacturer.
805312104 (0x30001668)

Mailbox transfer
Cause:
Internal error.


Remedy:
Restart the device. If the error persists, contact the manufacturer.
805312105 (0x30001669)

Waiting for mailbox transfer from master…
Cause:
Internal error.


Remedy:
Restart the device. If the error persists, contact the manufacturer.
805312106 (0x3000166A)

Mailbox transfer – Fatal time-out error
Cause:
Internal error.


Remedy:
Restart the device. If the error persists, contact the manufacturer.
805312107 (0x3000166B)

Bus cycle and Sync period are different
Cause:
Incorrect setting.


Remedy:
Check bus cycle. Check sync period.
805312108 (0x3000166C)

Error getting the bus scan state
Cause:
Internal error.


Remedy:
Restart the device. If the error persists, contact the manufacturer.
805312109 (0x3000166D)

Wrong response on DC supported request or slave
Cause:
Internal error.


Remedy:
Restart the device. If the error persists, contact the manufacturer.
805312110 (0x3000166E)

Unable to set ‘DC slave sync disable’
Cause:
Internal error.


Remedy:
Restart the device. If the error persists, contact the manufacturer.
805312111 (0x3000166F)

Error when restarting bus scan
Cause:
Internal error.


Remedy:
Restart the device. If the error persists, contact the manufacturer.
805312112 (0x30001670)

Bus scan timeout
Cause:
The bus scan was aborted due to timeout.


Remedy:
Analyze detailed error message in the logbook. Check network topology.
805312568 (0x30001838)

Configuration error – Check of VendorID failed
Cause:
The vendor ID could not be checked.


Remedy:
Analyze detailed error message in the logbook. Check network topology.
805312569 (0x30001839)

Configuration error – Check of ProductCode failed
Cause:
The product code could not be checked.


Remedy:
Analyze detailed error message in the logbook. Check network topology.
805312570 (0x3000183A)

Configuration error – Check of Revision failed
Cause:
The revision could not be checked.


Remedy:
Analyze detailed error message in the logbook. Check network topology.
805312571 (0x3000183B)

Configuration error – Check of VendorID failed
Cause:
The vendor ID could not be checked.


Remedy:
Analyze detailed error message in the logbook. Check network topology.
805312572 (0x3000183C)

Configuration error – Odd device at bus end
Cause:
A surplus device was detected at the end of the bus.


Remedy:
Analyze detailed error message in the logbook. Check network topology.
805312578 (0x30001842)

Internal error counter resetted
Cause:
Internal error counter resetted.


Remedy:
For information only. No remedy necessary.
805312580 (0x30001844)

All slaves ‘Operational’ again
Cause:
All slaves ‘Operational’ again.


Remedy:
For information only. No remedy necessary.
805312581 (0x30001845)

Cyclic command WKC error
Cause:
WKC error.


Remedy:
Analyze detailed error message in the logbook. Check slave status. Check network topology.
805312582 (0x30001846)

Frame response error
Cause:
Frame response error.


Remedy:
Analyze detailed error message in the logbook. Check slave status. Check network topology.
805312583 (0x30001847)

Not all slaves are ‘Operational’
Cause:
Not all slaves have been set to ‘Operational’.


Remedy:
Analyze detailed error message in the logbook. Check slave status. Check network topology.
805312584 (0x30001848)

Emergency message – Overflow, further messages blocked
Cause:
Too many emergency messages.


Remedy:
Check if slave sends too many emergency messages. Eliminate cause.
805312588 (0x3000184C)

New configuration loaded
Cause:
New configuration loaded.


Remedy:
For information only. No remedy necessary.
805312589 (0x3000184D)

New configuration loaded, no slaves defined
Cause:
New configuration loaded, no slaves defined.


Remedy:
For information only. No remedy necessary.
805312590 (0x3000184E)

Master – Start failed, configuration error
Cause:
Internal error.


Remedy:
See related entries in the logbook.
805312591 (0x3000184F)

New configuration loaded from slaves EEPROM
Cause:
New configuration loaded from slaves EEPROM.


Remedy:
For information only. No remedy necessary.
805312598 (0x30001856)

Master – Start failed
Cause:
Internal error.


Remedy:
See related entries in the logbook.
805312599 (0x30001857)

Master – Start failed, bus configuration error
Cause:
Bus configuration error.


Remedy:
Check network topology.
805312600 (0x30001858)

Master – Start failed, EtherCAT cable disconnected
Cause:
Network cabling is faulty.


Remedy:
Check network cabling.
805312601 (0x30001859)

Master – Start failed, DC/DCM configuration
Cause:
Internal error.


Remedy:
Restart the device. If the error persists, contact the manufacturer.
805312602 (0x3000185A)

Master – Start failed, cannot set slaves to ‘Pre-Operational’
Cause:
Slaves cannot be set to ‘Pre-Operational’.


Remedy:
See related entries in the logbook.
805312608 (0x30001860)

Master – Set ‘Operational’ failed
Cause:
Operational’ could not be set.


Remedy:
See related entries in the logbook.
805312609 (0x30001861)

Master – Set ‘Operational’ failed, Master not initialized
Cause:
Master not initialized.


Remedy:
See related entries in the logbook.
805312610 (0x30001862)

Master – Set ‘Operational’ failed, EtherCAT cable disconnected
Cause:
Network cabling is faulty.


Remedy:
Check network cabling.
805312611 (0x30001863)

Master – Set ‘Operational’ failed, DCM not in-sync
Cause:
Internal error.


Remedy:
See related entries in the logbook.
805312612 (0x30001864)

Master – Set ‘Operational’ failed, bus cycle and DC different
Cause:
Incorrect setting.


Remedy:
Check bus cycle. Check sync period.
805312613 (0x30001865)

Master – Set ‘Operational’ takes some time…
Cause:
Master – Set ‘Operational’ takes some time…


Remedy:
For information only. No remedy necessary.
805312614 (0x30001866)

Master – Set ‘Operational’ failed, time-out
Cause:
Time-out occurred.


Remedy:
See related entries in the logbook. Check slave status. Check network topology.
805312615 (0x30001867)

Master – Set ‘Operational’ failed, slave error
Cause:
Slave error.


Remedy:
See related entries in the logbook.
805312616 (0x30001868)

Master – Set ‘Operational’ aborted by reset command
Cause:
Master – Set ‘Operational’ aborted by reset command.


Remedy:
For information only. No remedy necessary.
805312618 (0x3000186A)

Master – Stopping failed
Cause:
Master cannot be stopped.


Remedy:
See related entries in the logbook.
805312619 (0x3000186B)

Master – Stopping failed, cannot set Slaves ‘Pre-Operational’
Cause:
Slave error.


Remedy:
See related entries in the logbook.
805312628 (0x30001874)

Master – Shutdown failed
Cause:
Master – Shutdown failed.


Remedy:
For information only. No remedy necessary.
805312638 (0x3000187E)

Remote API Server – Start failed
Cause:
Internal error.


Remedy:
Restart the device. If the error persists, contact the manufacturer.
805312648 (0x30001888)

Start Download Service
Cause:
Start Download Service.


Remedy:
For information only. No remedy necessary.
805312649 (0x30001889)

Download Service done
Cause:
Download Service done.


Remedy:
For information only. No remedy necessary.
805312668 (0x3000189C)

MMC – Internal error
Cause:
Internal error.


Remedy:
Restart the device. If the error persists, contact the manufacturer.
805312669 (0x3000189D)

MMC – ‘Modular Machine Configuration’ is active
Cause:
MMC – “Modular Machine Configuration” is active.


Remedy:
For information only. No remedy necessary.
805312670 (0x3000189E)

MMC – Service started
Cause:
MMC – Service started.


Remedy:
For information only. No remedy necessary.
805312671 (0x3000189F)

MMC – Service stopped
Cause:
MMC – Service stopped.


Remedy:
For information only. No remedy necessary.
805312672 (0x300018A0)

MMC – Error in configuration files
Cause:
MMC configuration file is faulty.


Remedy:
Check MMC configuration file.
805312673 (0x300018A1)

MMC – File does not exist
Cause:
MMC – File does not exist.


Remedy:
For information only. No remedy necessary.
805312674
0x300018A2

MMC – Parsing error
Cause: MMC configuration file is faulty.



Remedy:


Check MMC configuration file.
805312675
0x300018A3

MMC – parsing of file successful
Cause: MMC – parsing of file successful.



Remedy:


For information only. No remedy necessary.
805312676
0x300018A4

MMC – Devices not sorted in ascending order or devices missing
Cause: MMC configuration file is faulty.



Remedy:


Check MMC configuration file.
805312677
0x300018A5

MMC – Number of devices in device tree differs
Cause: MMC configuration file is faulty.



Remedy:

  • Check MMC configuration file.

  • Check network topology.
805312678
0x300018A6

MMC – Device type mismatch for Alias Address
Cause: MMC configuration file is faulty.



Remedy:

  • Check MMC configuration file.

  • Analyze detailed error message in the logbook.
805312679
0x300018A7

MMC – Invalid Alias Address
Cause: Incorrect alias address.



Remedy:

  • Check SSA addresses of the slaves.

  • Analyze detailed error message in the logbook.
805312680
0x300018A8

MMC – Duplicated Alias Address
Cause: Double alias address.



Remedy:

  • Check SSA addresses of the slaves.

  • Analyze detailed error message in the logbook.
805312681
0x300018A9

MMC – No configuration checks
Cause: MMC – No configuration checks.



Remedy:


For information only. No remedy necessary.
805312682
0x300018AA

MMC – Invalid configuration
Cause: Internal error.



Remedy:


Restart the device. If the error persists, contact the manufacturer.
805312683
0x300018AB

MMC – Mandatory slave missing
Cause:

  • MMC configuration file is faulty.

  • Network topology is faulty.




Remedy:

  • Check MMC configuration file.

  • Check network topology.
805312684
0x300018AC

MMC – Optional slave is present, but not allowed
Cause:

  • MMC configuration file is faulty.

  • Network topology is faulty.




Remedy:

  • Check MMC configuration file.

  • Check network topology.
805312685
0x300018AD

MMC – No valid service active
Cause: MMC – No valid service active.



Remedy:


For information only. No remedy necessary.
805312686
0x300018AE

MMC – Address assignment error, less slaves connected than configured
Cause:

  • MMC configuration file is faulty.

  • Network topology is faulty.




Remedy:

  • Analyze detailed error message in the logbook.

  • Check MMC configuration file.

  • Check network topology.
805312687
0x300018AF

MMC – Address assignment error, more slaves connected than configured
Cause:

  • MMC configuration file is faulty.

  • Network topology is faulty.




Remedy:

  • Analyze detailed error message in the logbook.

  • Check MMC configuration file.

  • Check network topology.
805312688
0x300018B0

MMC – Address assignment error, invalid device
Cause:

  • MMC configuration file is faulty.

  • Network topology is faulty.




Remedy:

  • Analyze detailed error message in the logbook.

  • Check MMC configuration file.

  • Check network topology.
805312689
0x300018B1

MMC – Address assignment successful
Cause: MMC – Address assignment successful.



Remedy:


For information only. No remedy necessary.
805312690
0x300018B2

MMC – Address assignment failed
Cause:

  • MMC configuration file is faulty.

  • Network topology is faulty.




Remedy:

  • Analyze detailed error message in the logbook.

  • Check MMC configuration file.

  • Check network topology.
805312691
0x300018B3

MMC – Address assignment done
Cause: MMC – Address assignment done.



Remedy:


For information only. No remedy necessary.
805312692
0x300018B4

MMC – Address assignment error, writing address by CoE
Cause: MMC – Address assignment error, writing address by CoE.



Remedy:


For information only. No remedy necessary.
805312693
0x300018B5

MMC – Slave identification error
Cause:

  • MMC configuration file is faulty.

  • Network topology is faulty.




Remedy:

  • Analyze detailed error message in the logbook.

  • Check MMC configuration file.

  • Check network topology.
805312694
0x300018B6

MMC – Slave identification error, slave ident data failed
Cause:

  • MMC configuration file is faulty.

  • Network topology is faulty.




Remedy:

  • Analyze detailed error message in the logbook.

  • Check MMC configuration file.

  • Check network topology.
805312695
0x300018B7

MMC – Service state cannot be changed, set bus to ‘INIT’ first
Cause: Service request rejected because master not in “Init” status.



Remedy:

  • Check status of the master.

  • Set status of the master to “Init”.
805312768
0x30001900

CoE – Emergency request
Cause: Information.



Remedy:


Information.
805312867
0x30001963

Last ETC message
Cause: –



Remedy:


–
805405056
0x30018180

EtherCAT – DC synchronization required
Cause: EtherCAT Distributed Clock (DC) not activated.



Remedy:


Activate DC mode.
805405057
0x30018181

EtherCAT – Communication error
Cause: EtherCAT communication interrupted.



Remedy:

  • Check bus cable.

  • Increase watchdog time.
805405312
0x30018280

EtherCAT – Wrong sync manager address
Cause: Wrong Sync Manager setting from EtherCAT master.



Remedy:

  • Check node.

  • Check the sequence of the nodes.

  • Check bus cable.
805405313
0x30018281

EtherCAT – Wrong sync manager size
Cause: Wrong Sync Manager setting from EtherCAT master.



Remedy:

  • Check node.

  • Check the sequence of the nodes.

  • Check bus cable.
805405314
0x30018282

EtherCAT – Wrong sync manager settings
Cause: Wrong Sync Manager setting from EtherCAT master.



Remedy:

  • Check node.

  • Check the sequence of the nodes.

  • Check bus cable.
805405315
0x30018283

PDO mapping: Unknown object
Cause: Unknown index in the PDO mapping.



Remedy:


Correct PDO mapping.
805405316
0x30018284

No PDO mapping object
Cause: The index cannot be mapped as PDO.



Remedy:


Correct PDO mapping.
805405317
0x30018285

Too many objects mapped
Cause: More than 64 objects are mapped.



Remedy:


Reduce number of objects in PDO mapping.
805405318
0x30018286

PDO mapping error
Cause: PDO mapping is faulty.



Remedy:


Check PDO mapping.
805405320
0x30018288

PDO mapping object is already used by PLC
Cause: The object to be mapped is already used by the PLC.



Remedy:


Remove object from mapping.
805406464
0x30018700

EtherCAT – Sync error
Cause:

  • EtherCAT Sync0 has failed.

  • PDO was sent or received too late.




Remedy:

  • Check in the EtherCAT master configuration whether Distributed Clock is activated.

  • Restart EtherCAT configuration.

  • Shift PDO reception time via user shift time.

  • Increase telegram failure error counter.
805406465
0x30018701

Sync PLL – Time-out
Cause: Error during state change Pre-Operational → Safe-Operational:

  • EtherCAT Sync0 has failed.

  • The Sync0 jitter is too high.




Remedy:

  • Check DC deviation in EtherCAT master.

  • Restart EtherCAT configuration.
805437220
0x3001FF24

Invalid Sync0 cycle time
Cause: The requested Sync0 cycle is outside the supported limits.



Remedy:


Correct Sync0 cycle.
805437270
0x3001FF56

Check OUT-port of EtherCAT master
Cause: The Ethernet connector is plugged into the IN port.



Remedy:


Correct wiring.
805437271
0x3001FF57

Check IN-port of EtherCAT slave
Cause: The Ethernet connector is plugged into the OUT port.



Remedy:


Correct wiring.
822313234
0x31038112

Network – Time-out explicit message
Cause:

  • Within the time-out period for explicit messages, which has been parameterised by the scanner, no “explicit message” was received.

  • The connection to the scanner has been interrupted.

  • Failure of an explicit connection.




Remedy:

  • Check cables and terminals.

  • Plug network cables into the Ethernet port.

  • Check the requested package interval (RPI) of the explicit connection.

  • Increase time limit for explicit messages in the scanner.
822313236
0x31038114

Network – Overall communication time-out
Cause:

  • EtherNet/IP: the maximum permissible time-out period for the CIP communication set in 0x23A1:010 has been exceeded.

  • Modbus TCP/IP: the maximum permissible time-out period for the TCP communication set in has been exceeded.




Remedy:

  • Check cables and terminals.

  • Connect network cable.
822313346
0x31038182

CAN: bus off
Cause: Too many faulty frames have been received.

  • Defective cable (e. g. loose contact).

  • Two nodes with the same node address.




Remedy:

  • Check wiring of the network.

  • Check bus terminating resistor.

  • Set the identical baud rate for each node of the network.

  • Assign a unique node address to each node of the network.

  • Eliminate EMC interferences.
822313347
0x31038183

CAN: warning
Cause: Too many faulty frames have been received.

  • Defective cable (e. g. loose contact).

  • Two nodes with the same node address.




Remedy:

  • Check wiring of the network.

  • Check bus terminating resistor.

  • Set the identical baud rate for each node of the network.

  • Assign a unique node address to each node of the network.

  • Eliminate EMC interferences.
822313348
0x31038184

CAN: heartbeat time-out consumer 1
Cause: Within the heartbeat time, no heartbeat telegram was received by node 1 to be monitored.



Remedy:

  • Check communication with the heartbeat producer.

  • Reactivate heartbeat producer.
822313349
0x31038185

CAN: heartbeat time-out consumer 2
Cause: Within the heartbeat time, no heartbeat telegram was received by node 2 to be monitored.



Remedy:

  • Check communication with the heartbeat producer.

  • Reactivate heartbeat producer.
822313350
0x31038186

CAN: heartbeat time-out consumer 3
Cause: Within the heartbeat time, no heartbeat telegram was received by node 3 to be monitored.



Remedy:

  • Check communication with the heartbeat producer.

  • Reactivate heartbeat producer.
822313351
0x31038187

CAN: heartbeat time-out consumer 4
Cause: Within the heartbeat time, no heartbeat telegram was received by node 4 to be monitored.



Remedy:

  • Check communication with the heartbeat producer.

  • Reactivate heartbeat producer.
822313360
0x31038190

Network – Watchdog time-out
Cause: Time-out during cyclic data reception, e.g. due to an interrupted communication link to the master or missing cyclic data.



Remedy:

  • Check wiring of the network.

  • Eliminate EMC interferences.
822313361
0x31038191

Network – Disruption of cyclic data exchange
Cause: The communication partner has interrupted the cyclic data exchange.



Remedy:

  • Check wiring of the network.

  • The slave must receive new parameterisation and configuration files by the master, in order to be able to exchange data again.
822313362
0x31038192

Network – Initialization error
Cause: The initialisation of the communication stack has been interrupted due to an incorrect address setting or communication configuration.



Remedy:


Check master/slave configuration and restart the devices.
822313363
0x31038193

Network – Invalid cyclic process data
Cause: The cyclic process data received are invalid.



Remedy:


Check cyclic process data sent by the master.
822313370
0x3103819A

Network – Initialization with safety option failed
Cause: Communication with the safety option could not be initialized correctly.



Remedy:


Check safe parameter set.
822313371
0x3103819B

Network – Communication time-out with safety option
Cause: Communication with the safety option is disturbed.



Remedy:


Check status of the safety option.
822313607
0x31038287

Network – Invalid configuration
Cause: Network configuration is faulty.



Remedy:


Check network configuration.
822313617
0x31038291

CAN: RPDO1 time-out
Cause: RPDO1 was not received within the time-out period set in 0x2304:045 or with the sync configured.



Remedy:


–
822313618
0x31038292

CAN: RPDO2 time-out
Cause: RPDO2 was not received within the time-out period set in 0x2304:055 or with the sync configured.



Remedy:


–
822313619
0x31038293

CAN: RPDO3 time-out
Cause: RPDO3 was not received within the time-out period set in 0x2304:065 or with the sync configured.



Remedy:


–
822313620
0x31038294

CAN: RPDO4 time-out
Cause: RPDO4 was not received within the time-out period set in 0x2304:075 or with the sync configured.



Remedy:


–