Troubleshooting
39/86
netTAP NT 50 | Gateway Devices
DOC091202UM09EN | Revision 9 | English | 2013-02 | Released | Public
© Hilscher, 2010-2013
7.1
Failure in 10 MBit/s Half Duplex Mode and Workaround
Only devices NT 50-xx-EN respectively NT 50 xx-RS are affected that were
produced before 2011 and have a serial number below the serial number
listed in the following table:
Device Type NT 50
Serial Number below
NT 50-CC-EN
20023
NT 50-CC-RS
20022
NT 50-CO-EN
20023
NT 50-CO-RS
20019
NT 50-DN-EN
20019
NT 50-DN-RS
20019
NT 50-DP-EN
20025
NT 50-DP-RS
20026
NT 50-RS-EN
20023
Affected Hardware
Hardware with the communication controller netX 50, netX 100 or
netX 500; netX/Internal PHYs.
When can this Failure occur?
When using standard Ethernet communication with 10 MBit/s half duplex
mode, the PHY gets stuck in case of network collisions. Then no further
network communication is possible. Only device power cycling allows
Ethernet communication again.
This problem can only occur with Ethernet TCP/UDP IP, EtherNet/IP or
Modbus TCP protocols when using hubs at 10 MBit/s. The issue described
above is not applicable for protocols which use 100 MBit/s or full duplex
mode.
Solution / Workaround:
Do not use 10 MBit/s-only hubs. Use either switches or 10/100 MBit/s Dual
Speed hubs, to make sure the netX Ethernet ports are connected with 100
MBit/s or in full duplex mode.
This erratum is fixed with all components of the ‘Y’ charge (9 digit charge
number shows ‘Y’ at position 5 (nnnnYnnnn).
Reference
“Summary of 10BT problem on EthernetPHY”,
RenesasElectronics Europe, April 27, 2010
