View Single Post
  #36   Spotlight this post!  
Unread 01-06-2016, 15:52
Cherry254 Cherry254 is offline
Registered User
FRC #0254 (The Cheesy Poofs)
Team Role: Mechanical
 
Join Date: Dec 2014
Rookie Year: 2014
Location: San Jose, CA
Posts: 9
Cherry254 has much to be proud ofCherry254 has much to be proud ofCherry254 has much to be proud ofCherry254 has much to be proud ofCherry254 has much to be proud ofCherry254 has much to be proud ofCherry254 has much to be proud ofCherry254 has much to be proud ofCherry254 has much to be proud of
Re: Team 254 Presents: Dropshot Technical Binder 2016

Quote:
Originally Posted by caume View Post
Why did you decide to go with #35 chain this year, instead of the usual #25?


Why did you use a servo in place of the pistons you used in 2014? I'm guessing it was for theoretically infinite hood positions, but I would think 4 or so would be enough. I guess it could possibly require some motor speed modification, but I would think that would be fairly easy...


Isn't a bag motor with a 5-stage gearbox a bit overkill...? I would think having some mechanism like a piston ball loader would be enough, or at least a bag motor with a (planetary?) gearbox with fewer stages

Thanks in advance for any response.
We bagged Dropshot with #25 chain but during driver practice we broke chain often. We modified the drive train and made the change to #35 chain at CVR (our first event) and did not have any issues during the season.

A servo was used for that very reason. Having a large range of hood positions allowed us to have an accurate shot from anywhere in the Courtyard.

We initially had a delrin basket that was pulled up by pneumatic cylinders to feed the ball into the shooter. The system had many issues leading to inconsistent shots. A custom gearbox was necessary because a planetary did not package inside the hood. The feeder roller and gearbox drastically helped our accuracy along with the other shooter modifications between Week 2 and Week 6.

Last edited by Cherry254 : 01-06-2016 at 16:00.
Reply With Quote