'Extended Diagnostics' tab (EtherCAT Slave Online Functions)

The following information refers to a specific, typical device type. Your screen may differ.

This help topic describes the 'Extended Diagnostics' editor of the EtherCAT 'Online Functions'. In the 'Online Functions' editor, select the EtherCAT slave station to be evaluated in the tree on the left and click the 'Extended Diagnostics' tab on top of the editor on the right.

This editor tab is only available for EtherCAT slaves but not for the master.

The editor tab provides diagnostic information about the EtherCAT communication of the selected station. Which information is displayed depends on the slave type (for instance, the number of ports the slave has).

This topic contains the following sections:

'Common Error Counter'

Element Description

Processing Unit Error The processing unit error counter is located at register offset 0x030C. The counter logs the number of non-EtherCAT frames (i.e., which are invalid in the EtherCAT segment) the slave has received.

PDI Error The processing unit error counter is located at register offset 0x030D. The counter logs the number of Process Data Interface errors in the slave. These are physical errors which were detected by the PDI at the EtherCAT bus.

Clear Error Counters Clicking this button resets all counters displayed.

Element	Description
Processing Unit Error	The processing unit error counter is located at register offset 0x030C. The counter logs the number of non-EtherCAT frames (i.e., which are invalid in the EtherCAT segment) the slave has received.
PDI Error	The processing unit error counter is located at register offset 0x030D. The counter logs the number of Process Data Interface errors in the slave. These are physical errors which were detected by the PDI at the EtherCAT bus.
Clear Error Counters	Clicking this button resets all counters displayed.

'Port y Counters'

Which ports are actually listed depends on the slave. Errors are only counted if the corresponding port is enabled.

y represents the port number.

Element Description

Invalid Frames, CRC Error This counter is located at register 0x300 + y*2.
The counter logs the number of corrupted frames transmitted via this port (detected due to an invalid CRC). This counter provides the following information:

Physical layer errors (e.g. when receiving invalid symbols). These errors can occur both inside and outside the frames (if inside, then they are also counted as frame errors).

Frame errors (e.g. due to corrupted bit sequence within a frame)

RX Error This counter is located at register 0x300 + y*2 + 8 bit.
The counter logs the number of RX errors at this port. An increment in this counter indicates that the received hardware signal has been corrupted and the transported data has been discarded by the slave.
The most common causes of signal distortion are:

External EMC interferences (normally result in sporadic counter increments).

Damaged devices or connections (usually result in rapid and systematic meter increments).

Lost Link This counter is located at register 0x310 + y.
The counter logs the number of lost connections at this port. An increment of this counter indicates that the hardware communication channel has been interrupted. During a "LinkDown", the frames are not forwarded to the neighboring device.
The most common causes of link loss are:

Temporary or permanent loss of power supply or reset of a device.

Damaged cables, defective/loose connectors or loose contacts.

EMC interference.

Forwarded RX Error This counter is located at register 0x380 + y.
The counter logs the number of Forwarded RX errors at this port.

Element	Description
Invalid Frames, CRC Error	This counter is located at register 0x300 + y*2. The counter logs the number of corrupted frames transmitted via this port (detected due to an invalid CRC). This counter provides the following information: Physical layer errors (e.g. when receiving invalid symbols). These errors can occur both inside and outside the frames (if inside, then they are also counted as frame errors). Frame errors (e.g. due to corrupted bit sequence within a frame)
RX Error	This counter is located at register 0x300 + y*2 + 8 bit. The counter logs the number of RX errors at this port. An increment in this counter indicates that the received hardware signal has been corrupted and the transported data has been discarded by the slave. The most common causes of signal distortion are: External EMC interferences (normally result in sporadic counter increments). Damaged devices or connections (usually result in rapid and systematic meter increments).
Lost Link	This counter is located at register 0x310 + y. The counter logs the number of lost connections at this port. An increment of this counter indicates that the hardware communication channel has been interrupted. During a "LinkDown", the frames are not forwarded to the neighboring device. The most common causes of link loss are: Temporary or permanent loss of power supply or reset of a device. Damaged cables, defective/loose connectors or loose contacts. EMC interference.
Forwarded RX Error	This counter is located at register 0x380 + y. The counter logs the number of Forwarded RX errors at this port.