Troubleshooting

All errors of the EtherCAT Master also exist in the IEC application. The function block instance for each EtherCAT Master has a property to read 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 possible between PLC and first device More than 100 consecutive packets are not 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 you use sync unit groups and at least one device in the sync unit group does not work, then the entire group is displayed as faulty. Not all EtherCAT Slaves transmit the 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. The devices after the first devices 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 do not communicate as expected. The inputs are not transmitted or the outputs are not used. Possible causes: The EtherCAT device is no longer ready for use because synchronization has been lost or another error has occurred in the device (excessive temperature, excessive voltage). 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 using "Distributed Clock", the time of the first EtherCAT device with "Distributed Clock" is used to synchronize the other devices and the PLC. This error message is displayed when the time value is always the same. Possible causes: The input and output connection of the EtherCATdevices is incorrect. Possible solution: Change the input and output connector of the first device with the "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 could be found, then 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 for 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 returns 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 corrections.