BECKHOFF ET1100 - Manual (Page 11)

General Issues
Slave Controller – Application Note FAQ 7
3.12.3 Basic error counter interpretation
At first, check the ESC configuration, e.g. by viewing the POR registers 0x0E00:0x0E01 or the IP Core
configuration in the User RAM 0x0F80. If the configuration is wrong, check the strapping options and
power-on signal values during POR sampling.
Then, check the link status in the ESC DL Status register 0x0110. If there is something wrong with the
link status, check the LINK_MII signal. If this is also ok, the problem is in the area PHY
– connector –
cable – connector – PHY.
If an RX Error counter (0x0301, 0x0303, 0x0305, 0x0307) is increasing, there is a problem in the area
PHY
– connector – cable – connector – PHY. Measure the RX_ERR signal from the PHY to prove the
error counter: if it is sometimes high, check the cabling, connectors, and PHY. Measure the RX_ERR
signal from the PHY. The ESC is not the source of the problem.
If there is no RX Error, there is probably a master issue. Use a proven master, attach also proven
slaves. Remove DUT; move the DUT in the network by swapping positions and check if the error is
moving with the DUT.
If the issue is not a master issue, it must be in the area PHY – ESC – PHY, i.e., check the interface
configuration of the PHY, the connections itself, the configuration of the ESC, and – in case of the IP
Core –, if the ESC is correctly constrained and the timing is achieved.
Also think of power supply break-down, clock jitter, and glitches on the reset signal.