Thread: #25 Chain
View Single Post
  #10   Spotlight this post!  
Unread 02-29-2016, 03:23 PM
gblake's Avatar
gblake gblake is offline
6th Gear Developer; Mentor
AKA: Blake Ross
no team (6th Gear)
Team Role: Mentor
 
Join Date: May 2006
Rookie Year: 2006
Location: Virginia
Posts: 1,933
gblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond repute
Re: #25 Chain

Quote:
Originally Posted by Sh1ine View Post
Hi Folks,

Typically we use belt for our drive train. This year with the bigger wheels we are decided that we wanted a stronger transfer method so we switched to #25 chain. We are running 8" AndyMark Pneumatic wheels, with a WCP Dual Speed Gearbox. Our low end is about 6 fps and the high is about 12 fps. We keep breaking chain. Is anyone else having problems with the large wheels breaking the chain? Some on the team want to switch to #35 chain, but that seems like overkill to me. I feel like we must be doing something wrong, not that the chain is too weak.

Thanks!
Search through the past Chief Delphi discussions about the relative merits of #25 and #35 chains and you will find plenty of facts, experiments, opinions and anecdotes.

One thing that should become apparent during your search is that your machine is a system made of many parts, that it is operating in varying environments, and that it is being asked (by its operators & software) to do more than one thing. That makes it easy to reach the conclusion that you have to ask the right question (one that takes into account all the important independent variables) before you can answer whether #25 or #35 is the right chain for your machine.

I don't say this to make the topic sound too hard. I say it to help you quickly reach a valid, complete answer. Answers to incomplete questions are incomplete answers, and letting incomplete answers churn your design is not good.

Bottom Line: As is often the case, the right place to start is by learning what has already been recorded; so that you can stand on the shoulders of the ones who have gone before you.

Blake

PS: Some engineers and shade-tree mechanics might just decide to do a quick experiment. That would be adding some dead weight and/or rotating mass to your robot to approximate the effects of switching to #35 chain+sprockets, and then (using the current #25) deciding if the robot is likely to perform well enough when it has to move the the more massive, and stronger, #35 chain+sprockets. If it does still perform well enough, switch to the stronger and "more forgiving" chain this season (before next season do more sophisticated experiments).

PPS: There is more than one type of #25 chain ..., and more than one type of #35 chain.
__________________
Blake Ross, For emailing me, in the verizon.net domain, I am blake
VRC Team Mentor, FTC volunteer, 5th Gear Developer, Husband, Father, Triangle Fraternity Alumnus (ky 76), U Ky BSEE, Tau Beta Pi, Eta Kappa Nu, Kentucky Colonel
Words/phrases I avoid: basis, mitigate, leveraging, transitioning, impact (instead of affect/effect), facilitate, programmatic, problematic, issue (instead of problem), latency (instead of delay), dependency (instead of prerequisite), connectivity, usage & utilize (instead of use), downed, functionality, functional, power on, descore, alumni (instead of alumnus/alumna), the enterprise, methodology, nomenclature, form factor (instead of size or shape), competency, modality, provided(with), provision(ing), irregardless/irrespective, signage, colorized, pulsating, ideate

Last edited by gblake : 02-29-2016 at 03:50 PM.
Reply With Quote