Go to start pageConfiguration and programmingConfiguration in Automation Builder...PLC devices and componentsEtherCAT configurator Troubleshooting
Troubleshooting Permalink

All EtherCAT Master errors are also available in the IEC application. The function block instance of each EtherCAT Master provides a property for reading the last error as an enumeration.

For more information, see: ‎⮫ IoDrvEtherCAT.LastError and ‎⮫ ETC_LASTERROR

Problem

Possible Solution

EtherCAT Master with red triangle in device tree

Logger message: ‎Error: more than 100 packets lost, perhaps communication lost! check the cables !‎

No communication is possible between the PLC and the first device.

More than 100 consecutive packets have not been received.

Possible causes:

  • The network cable between the PLC and the first device is disconnected or unstable.

  • The power supply of the first device is disconnected or unstable.

  • The first device does not respond to EtherCATpackets.

Possible solution:

  • Check the cables and the link LED.

  • Check the power supply to the devices.

  • Exchange the EtherCAT device.

Some devices may have a red triangle in the device tree.

Logger message: ‎Working counter for sync unit group x is wrong! Group is set to nonoperational!‎

If sync unit groups are used and at least one device in the sync unit group is not operating correctly, the entire group is indicated as faulty. Not all EtherCAT Slaves transmit process data as expected. Input or output data may be missing.

Possible causes:

  • Some slaves no longer communicate. The network cable between the EtherCAT devices is disconnected or unstable.

  • The power supply of the devices is disconnected or unstable.

  • Devices downstream of the first affected device do not respond as expected.

Possible solution:

  • Check the cables and the link LED.

  • Check the power supply to the devices.

  • Exchange the EtherCAT device.

Some devices may have a red triangle in the device tree.

Logger message: ‎Warning unexpected working counters: number of slaves has changed or is different to the configuration!‎

One or more devices are not communicating as expected. The inputs are not transmitted or the outputs are not used.

Possible causes:

  • The EtherCAT device is no longer operational because synchronization has been lost or another error has occurred (for example, overtemperature or overvoltage).

Possible solution:

  • Check the status page of the slave and also the device diagnostic page (if available).

Logger message: ‎Distributed clock is always same value! Change in and out connector of slave‎

When "Distributed Clock" is used, the time of the first EtherCAT device with “Distributed Clock” enabled is used to synchronize the other devices and the PLC.

This error message is displayed when the time value does not change.

Possible causes:

  • The input and output connections of the EtherCATdevices is incorrect.

Possible solution:

  • Swap the input and output connections of the first device with "Distributed Clock" option enabled.

EtherCAT Master with red triangle in device tree

Logger message: ‎Checking slaves: perhaps slave(s) missing, mismatch to configuration or no communication at all. Use scan for devices to check‎

When the EtherCAT devices are started, the number of available devices is determined and the EEPROM of all devices is read. If no devices sre detected, this message is displayed.

Possible causes:

  • The network cable is not connected or the wrong EtherCAT adapter is configured.

  • The power supply of the EtherCAT devices is switched off of disconnected.

Possible solution:

  • Check the cables and the link LED.

  • Check the power supply to the devices.

  • Check the configuration of the network adapter in CODESYS.

  • Exchange the EtherCAT device.

Logger message: ‎SysEthernet: packet could not be sent, error code‎

The PLC runtime system could not transfer an EtherCAT packet.

Possible causes:

  • The network cable is not connected or the wrong EtherCAT adapter is configured.

  • The power supply of the EtherCAT devices is switched off or disconnected.

Possible solution:

  • Check the cables and the link LED.

  • Check the power supply to the devices.

  • Check the configuration of the network adapter in CODESYS.

  • Exchange the EtherCAT device.

Logger message: ‎AL Status read from slave address…‎

The device detects an error and reports various error causes.

Possible causes:

  • Error in the configuration or the input or output settings

  • Error in “Distributed Clock”.

Possible solution:

  • Check the logger message for possible causes and corrective actions.