|
Re: Looking for Last Minute Fixes on a Possible "Comm" Error
Did you ever figure it out?
My guess it is a code issue.
When you say it works "wired", did you ever take it through a "practice match" simulation while wired?
It could be in the FMS signals to the RoboRio, which continuously activates various routines (teleop_continuous, teleop_periodic, etc.). It may not be the same set of activations that you get when you merely "enable" when wired.
Some things that might be happening:
1) Two or more routines start conflicting, and it takes time for the conflict to manifest.
2) Memory leak somewhere, and the roborio has to stop and do some garbage collection.
|