Quote:
Originally Posted by Chickenonastick
We had a similar issue at Davis in which our comms were dropping after a few seconds into the match. It turned out that absolutely nothing was wrong with our radio -- the resolution of our camera feed, when using dual cameras, was simply too high, causing the memory on either the cRIO or driver station computer (I'll get back to you on which one) to overload, which resulted in packet loss and a lost connection.
|
Along these lines....... The only time in ~30 matches this year we were dead on the field, was NOT because of comms loss. We had errors that continued to accumulate on the DS. Now I am not certain the exact mechanism that caused us to sit dead on the field, but we suspect that we had filled up a buffer, HD space, or.... Whatever it was, as soon as we cleared the error queue, or robot was able to move again.
Once we figured this out, clearing the queue became part of our start up routine for every match.
After this, we also found the root cause of 2 out of the three errors that kept happening and corrected it. That reduced the number of errors being logged.
Whether this is related to what other teams were experiencing or not, I don't know. I put it out there to add to the clues that might help get to the bottom of the "comm errors".