2012 Field Comm. Issue Logs

[DonRotolo]

Some data points:

At Rutgers to a small extent and at NYC to a much greater extent, we were seeing the robot stop responding for a second to several seconds, somewhat randomly. This would occur both tethered and via radio (!)

Reviewing the logs from NYC we found our latency was around 170 mSec ('good' would be <10 mSec).

Our 8-slot cRio showed a CPU usage of 50-60%, which is reasonable.

Carefully working to recreate the issue on our prototype robot, we ultimately found that out driver station CPU was maxing out.

We have not yet deemed this issue resolved, but we believe we're almost there. We'll find out when we unbag this week in anticipation of Mount Olive.

(I don't have the details requested in the OP, but can get them if that will help. All our cRios are 8-slot, we use LabView, and our radios are all Rev A).