View Single Post
  #22   Spotlight this post!  
Unread 21-08-2015, 10:32
Monochron's Avatar
Monochron Monochron is offline
Engineering Mentor
AKA: Brian O'Sullivan
FRC #4561 (TerrorBytes)
Team Role: Engineer
 
Join Date: Feb 2007
Rookie Year: 2002
Location: Research Triangle Park, NC
Posts: 914
Monochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond repute
Re: A more autonomous teleop?

Quote:
Originally Posted by thatprogrammer View Post
Perhaps you could have optimized it more by adding a beam break to tell when the ball was in, and made the intake go back to 'carry' by itself?
We did use a sensor to tell us when the ball was in, but that didn't eliminate the problem of the ball unseating itself, getting defended against, or otherwise losing grasp while going back to "carry". A more complete solution would have to constantly react to the current state of the ball throughout the back-to-carry maneuver, because the likelihood of losing the ball with our grabber was too high.

My point was that the way we designed our ball carrier didn't match the automation we tried to use, not that automation shouldn't be done on ball pick-ups. Because our back-to-carry maneuver was so slow (on the order of couple seconds after first acquiring the ball) automating that portion made no sense.