View Single Post
  #3   Spotlight this post!  
Unread 06-04-2014, 14:55
walruspunch walruspunch is offline
It's time for SCIENCE!
FRC #1977 (Power Squids)
Team Role: Leadership
 
Join Date: Jan 2014
Rookie Year: 2012
Location: USA
Posts: 4
walruspunch is an unknown quantity at this point
Re: Wrong Field Measurements and Bad FMS

Team 1977 was wondering about the FMS too....By our count, somewhere between 10 and 20 teams had issues during matches. Some of that is likely coincidence, but there was way too much interference to mark it all as something from a team. Our robot worked perfectly on the practice matches and in the pit while tethered, but for the first day of qualifiers, we could do nothing. No autonomous, no teleop, nothing. As soon as we put it on the field, we went dead, with no robots hitting us or interference. When we brought it back to the pit, it worked perfectly every time. We had several officials look it over and find no explanation. We also had several people check over the code and find no explanation. We finally made it work, albeit with lag, by disabling the autonomous feature and switching out the CRIO. However, other teams that had communication issues had been cleared up on their own, leading to the possibility that making these changes was coincidence. Our robot was the worst off, losing a full day of competition, but another team was only able to run for half of every match before losing connection. Several times, a team would be dead at the start of a match and gain connection about 10 seconds into teleop mode. Rebooting the CRIO helped for a time, but it takes a lot of time within each match and only seems to be a temporary fix. It seems too big of a deal involving too many teams to be marked down as an error on every team. (Unsure, but it may have happened to a team in the finals as well. Last 10 seconds they were not moving, but it could have been driver error.)