|
Re: Suggestions for resolving stuck balls
Quote:
Originally Posted by Nuttyman54
I think the robot needs to be e-stopped or disabled by the field in order for the ball to be declared dead, since a radio or cRIO reset could result in the robot becoming active at a later point if not expressly disabled. This doesn't address if the ball comes loose after the disable (eg a mechanism sags, or a forceful hit on the ball later).
The issue is not just how to determine when a ball is "dead" but also deal with what happens if the ball returns to play, since the game is only designed to track one ball at a time in teleop.
I think with how rarely a ball will get stuck on top of the truss, the best recourse is to declare a field fault, similar to jammed nets in 2012.
|
+1 on every point.
__________________
CalGames 2009 Autonomous Champion Award winner
Sacramento 2010 Creativity in Design winner, Sacramento 2010 Quarter finalist
2011 Sacramento Finalist, 2011 Madtown Engineering Inspiration Award.
2012 Sacramento Semi-Finals, 2012 Sacramento Innovation in Control Award, 2012 SVR Judges Award.
2012 CalGames Autonomous Challenge Award winner ($$$).
2014 2X Rockwell Automation: Innovation in Control Award (CVR and SAC). Curie Division Gracious Professionalism Award.
2014 Capital City Classic Winner AND Runner Up. Madtown Throwdown: Runner up.
2015 Innovation in Control Award, Sacramento.
2016 Chezy Champs Finalist, 2016 MTTD Finalist
|