View Single Post
  #5   Spotlight this post!  
Unread 05-04-2014, 16:25
Alan Anderson's Avatar
Alan Anderson Alan Anderson is offline
Software Architect
FRC #0045 (TechnoKats)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Kokomo, Indiana
Posts: 9,112
Alan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond repute
Re: Wrong Field Measurements and Bad FMS

Quote:
Originally Posted by sarahg2543 View Post
Another issue that we encountered was that the FMS tended to malfunction, especially in the red alliance driver station. I saw a lot of robots lose their communication. The field crew said that it was due to the robot most of the time instead of replaying the match.
Loss of communication is due to the robot most of the time. If it isn't the robot, then it's almost always the Operator Console. If it looks like one particular alliance station spot has problems for several matches in a row, it's most likely just a coincidence.

I've been a CSA at many events over the past few years, and I'm pretty confident about this. One team's mentor came up to me at the Boilermaker regional and told me their scouting group had identified the Blue 3 position as having a problem, with three robots not working there before their own robot had control issues in their most recent match. I had just come from their pit where I showed the team the loose battery connection on their robot, and I informed him that the three previous robots had suffered 1) an unplugged battery, 2) a shorted power wire on the cRIO, and 3) a disconnected joystick.