Hi Derek,
I would like to see the graph to cross out the possibility of a communication problem.
We made the communication latency view to see how much time do the communication cycles take, so the user can see if there is a problem with the communication.
How it works is the PC side software sends a packet and receives the response and it measures the time between the two.
For problemless operation it is a requirement to receive the answers within 20msec.
If the response times are longer means somekind of issue with the communication.
With USB controllers it can be that the USB hub is overloaded, e.g. some other USB devices connected to the same hub using too much bandwidth and so the UCxxx controller do not have enough bandwidth to do it's own communication fast enough.
With ethernet controllers it can be a problem with the network card or with it's drivers or it can be a problem with the router if a LAN connection was made.
I want to cross out the possibility of a communication problem, because if it is a comm. latency problem then the issue is outside the UCCNC and then you will have to look at the network components instead of debugging the UCCNC. So, it would be good to verify this first.