Commissioning
5.5 Using QuickConnect
5.5.4
Troubleshooting and optimization
Delayed connection time
Many factors can cause the controller connection time to be slower than expected. These
factors include the following:
● RPI (I/O cycle time)
● Time slice percentage
● Timer set in the application logic
● EtherNet/IP traffic
● Controller task load
If you cannot achieve optimum connection time with the recommended settings, you may
need to evaluate alternate EtherNet/IP configurations or controller requirements.
Timing errors
Once you initially configure your system, you should test whether the connection timing is
within your required timeframe. A QuickConnect I/O device issues a gratuitous ARP
message on the network every 25 ms for a maximum of 40 times (1 second) until an I/O
connection is established. If you experience periodic missed connections, it is recommended
that you:
● Analyze network traffic for the root cause.
● Extend the timer in your application logic to a value greater than 650 ms if necessary.
64
ET 200pro distributed I/O EtherNet/IP interface module
Manual, 03/2016, A5E32861915-AB