View Single Post
  #1   Spotlight this post!  
Unread 07-01-2014, 17:17
Nuttyman54's Avatar
Nuttyman54 Nuttyman54 is offline
Mentor, Tactician
AKA: Evan "Numbers" Morrison
FRC #5803 (Apex Robotics) and FRC #0971 (Spartan Robotics)
Team Role: Mentor
 
Join Date: Jan 2005
Rookie Year: 2005
Location: Seattle, WA/Mountain View, CA
Posts: 2,138
Nuttyman54 has a reputation beyond reputeNuttyman54 has a reputation beyond reputeNuttyman54 has a reputation beyond reputeNuttyman54 has a reputation beyond reputeNuttyman54 has a reputation beyond reputeNuttyman54 has a reputation beyond reputeNuttyman54 has a reputation beyond reputeNuttyman54 has a reputation beyond reputeNuttyman54 has a reputation beyond reputeNuttyman54 has a reputation beyond reputeNuttyman54 has a reputation beyond repute
Send a message via AIM to Nuttyman54
Re: Suggestions for resolving stuck balls

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.
__________________
Reply With Quote