Go to Post Cue all the jokes about natural selection in the Darwin division - TDav540 [more]
Home
Go Back   Chief Delphi > Technical > Programming
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Closed Thread
 
Thread Tools Rate Thread Display Modes
  #1   Spotlight this post!  
Unread 21-08-2015, 10:19
thatprogrammer's Avatar
thatprogrammer thatprogrammer is offline
Registered User
AKA: Ahad Bawany
no team (None)
Team Role: Programmer
 
Join Date: Apr 2014
Rookie Year: 2014
Location: Florida
Posts: 610
thatprogrammer has a reputation beyond reputethatprogrammer has a reputation beyond reputethatprogrammer has a reputation beyond reputethatprogrammer has a reputation beyond reputethatprogrammer has a reputation beyond reputethatprogrammer has a reputation beyond reputethatprogrammer has a reputation beyond reputethatprogrammer has a reputation beyond reputethatprogrammer has a reputation beyond reputethatprogrammer has a reputation beyond reputethatprogrammer has a reputation beyond repute
Re: A more autonomous teleop?

Quote:
Originally Posted by Monochron View Post
I'll give an example; in last year's game we realized that our ball-pickup mechanism was rather slow so we decided to automate a lot of the process. The operator would hold down a button to drop our grabber and turn on our intake roller and then release the button to stop the roller and return to a "carry" position. In general it worked well but would occasionally cause us to have problems if the ball was falling out of our grabber, if we didn't approach the ball straight-on, or even if we were getting defended while trying to pick up. Basically it gave our drivers even more tasks to be mindful of (making sure to kill the automation if it was going to make us drop the ball or miss the ball, etc.)
.
A lot of teams automated their pick ups in 2014. I think what might have not been done in this case was designing with that automation in mind. 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?
My point is: Automation should be considered during the design process, doing it too late is often sloppy.
  #2   Spotlight this post!  
Unread 21-08-2015, 10:32
Monochron's Avatar
Monochron Monochron is online now
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: 906
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.
Closed Thread


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 16:36.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi