Annex
207/223
PC Cards cifX PCI, PCIe, Low Profile PCIe | Installation, Operation and Hardware Description
DOC120204UM46EN | Revision 46 | English | 2015-12 | Relelased | Public
© Hilscher, 2008-2015
11.5 Notes on earlier Hardeware Revisions
11.5.1 Failure in 10 MBit/s Half Duplex Mode and Workaround
The note is only valid for the PC cards cifX up to serial numbers indicated:
PC Cars cifX
Part No
up to Serial Number
CIFX 50-RE
1250.100 22414
CIFX 50E-RE
1251.100 20167
Failure of the Network Communication
!
Do not operate hardware with the communication controllers netX 50,
netX100 or netX 500 with the protocols Ethernet TCP/UDP/IP,
EtherNet/IP or Modbus TCP at 10 MBit/s in half-duplex mode, otherwise
failure of the network communication can occur.
!
Use only switches or 10/100 MBit/s dual-speed hubs and ensure that
the network operates at 100 MBit/s and in full-duplex mode.
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
