View Single Post
  #22   Spotlight this post!  
Unread 23-03-2010, 18:59
kjohnson's Avatar
kjohnson kjohnson is offline
Insert Clever Title Here
AKA: Kyle J.
FRC #1610 (BOT)
Team Role: Mentor
 
Join Date: Jan 2004
Rookie Year: 2004
Location: Virginia
Posts: 575
kjohnson has a reputation beyond reputekjohnson has a reputation beyond reputekjohnson has a reputation beyond reputekjohnson has a reputation beyond reputekjohnson has a reputation beyond reputekjohnson has a reputation beyond reputekjohnson has a reputation beyond reputekjohnson has a reputation beyond reputekjohnson has a reputation beyond reputekjohnson has a reputation beyond reputekjohnson has a reputation beyond repute
Re: Take an exit with dignity

Quote:
Originally Posted by mrmummert View Post
We think the gaming adapter cord was loose for two matches. but on saturday we double checked (don did ,remember he had to keep loading the default drive code back in when other code did'nt work) and it would work fine in the pit and it would'nt move at all on the feild two times we were on red. Is it also possible it could have been a combination of both the feild and something on the robot that when each are checked nothing shows but combined together they cause trouble? I'm not saying it was the feild or the robot, but something weird was going on.
The game adapter power cord being loose was very likely the source of your sluggish communications. The match where communication dropped during the match was either the game adapter cord or a voltage drop caused by the drive-train. If the battery voltage drops low enough, it will cause the cRIO to reboot, and will not reconnect to FMS for the remainder of the match. We saw this happen in quite a few teams throughout the three days of competition.

The match where 1610 never moved at all was absolutely because of bad robot code, and just happened to also be on the red alliance.
Reply With Quote