|
Re: Team Fusion #364, Bayou Regional, FMS Woes
Yep, we had a very similar issue several times on the field at Bayou.
We never had any issues connecting to the field before the match began. BUT, after running autonomous, we'd still be "connected" but the driver station would display "No Robot Code." When this happened the first time during a practice match on Thursday, we waited to see if it would find the code; never did. The FTA suggested that next time we try to reboot the cRIO in the middle of the match and see what happened. So we listened: every time we "lost robot code" on the field (which happened at least 4 times over the course of Friday and Saturday), we would immediately reboot the cRIO. What would happen:
1) Auto works fine
2) Teleop begins: "No Robot Code"
3) Driver immediately reboots cRIO = lose connection with FMS temporarily
4) Regain connection within ~5/10 secs.
5) "No Robot Code" displays again
6) Regain comm ("find" code) with about 20 sec. left in match
So ultimately, reboting the cRIO worked for us (if I can really say that... We were still out most of the match, obviously). Did you guys ever try this?
But you're right, this still doesn't answer the question of why this occurred in the first place. Our losses were more sporradic than yours, so not sure why ours worked most of the time. When we talked to the FTA about this issue during quals, he blamed it on our robot, too (and you know, who knows, it very well may be the robot). When it happened again during elims, FTA said it still looked like FMS was fine; they said there were no issues on their end, and when the code was "lost" after auto, everything was still reading fine in relation to their connection with our bot. Who knows.
Hope someone can figure this out soon.... We're also attending Lone Star in a few weeks.
__________________
Georgia Institute of Technology
BS Mechanical Engineering '16
2012-2014 | Volunteer
2012-____ | Dean's List Finalist, Lone Star Regional
2008-2012 | 624: CRyptonite
Last edited by Elizabeth Waters : 19-03-2012 at 00:22.
|