Thread: #25 Chain
View Single Post
  #27   Spotlight this post!  
Unread 29-02-2016, 15:46
cadandcookies's Avatar
cadandcookies cadandcookies is online now
Director of Programs, GOFIRST
AKA: Nick Aarestad
FTC #9205 (The Iron Maidens)
Team Role: College Student
 
Join Date: Jan 2012
Rookie Year: 2009
Location: Minnesnowta
Posts: 1,550
cadandcookies has a reputation beyond reputecadandcookies has a reputation beyond reputecadandcookies has a reputation beyond reputecadandcookies has a reputation beyond reputecadandcookies has a reputation beyond reputecadandcookies has a reputation beyond reputecadandcookies has a reputation beyond reputecadandcookies has a reputation beyond reputecadandcookies has a reputation beyond reputecadandcookies has a reputation beyond reputecadandcookies has a reputation beyond repute
Re: #25 Chain

Quote:
Originally Posted by Ginger Power View Post
The best way to fix #25 chain is to use #35 chain. People claim that if you use it correctly, #25 is perfectly fine. It's that first part that's hard. If you have the weight, I highly reccomend #35.


*Disclaimer: I hate #25 chain with a fiery passion because it cost us over 12 hours during RI3D this year. We would've been done a solid 12 hours earlier if we had used #35.
To be fair, your Ri3D robot had some massive, exposed chain runs that are exactly where using #25 chain would cause issues.

This is a good case example: #25 chain needs to be used with care and precision. If you aren't confident in your ability to provide that, or want to push your chain to its limits (small sprockets on big wheels, lots of torque or speed), you really should be using #35, just due to the fault tolerance.

This year lends itself well to very fault-tolerant, robust robots. While #25 can live up to that challenge, it requires a lot more care and effort to make it do so, especially after build season.
__________________

Never assume the motives of others are, to them, less noble than yours are to you. - John Perry Barlow
tumblr | twitter
'Snow Problem CAD Files: 2015 2016
MN FTC Field Manager, FTA, CSA, Emcee
FLL Maybe NXT Year (09-10) -> FRC 2220 (11-14) -> FTC 9205(14-?)/FRC 2667 (15-16)
VEXU UMN (2015-??)
Volunteer since 2011
2013 RCA Winner (North Star Regional) (2220)
2016 Connect Award Winner (North Super Regional and World Championship) (9205)
Reply With Quote