Team 5096 had two matches during the Wisconsin Regional - Qualification 39 and 70 where we connected to the FMS but were unable to communicate with our robot during some or all of the match. This occurred with two different Classmate computers running DS version 09021500. The error logs are characterized by lost packets, especially in match 70. I think we restarted the drivers station in match 39 and were able to compete during half of the match. We never experienced problems tethered or using Wifi during development.
The LabVIEW rep at the match looked at our code and helped us find a problem that was slowing our motor loop, but did not feel this would have completely disrupted our communications with the field. He would not speculate on the root cause, but suggested we restart the DS if it happened again. On other forums I saw several suggestions - like changing the team number to 1 and then back to 5096, etc., but no solutions.
Naturally, the team was extremely disappointed with being completely disabled on the field during the few matches available to us. I would like some suggestions for how we could duplicate or troubleshoot this problem. I attached the logs. I am wondering if our team should switch from LabVIEW to C++ or Java next year in order to avoid this problem, but all our indications are that the problem is between the Driver Station software and the Field Management System.
By the way, we are using a RoboRIO controller.
