Thread: Best Drivetrain
View Single Post
  #32   Spotlight this post!  
Unread 29-04-2008, 15:44
Lil' Lavery Lil' Lavery is online now
TSIMFD
AKA: Sean Lavery
FRC #1712 (DAWGMA)
Team Role: Mentor
 
Join Date: Nov 2003
Rookie Year: 2003
Location: Philadelphia, PA
Posts: 6,600
Lil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond repute
Send a message via AIM to Lil' Lavery
Re: Best Drivetrain

Quote:
Originally Posted by CraigHickman View Post
Yeah, I am offering to teach this ROOKIE team how to properly use this system. It's only as simple as using CAD to design your chain runs, and CAD is supplied free to all teams (in any flavor you want, too...). I agree that it's safer for you to avoid giving advice that may result in a bit of failure, but at the same time, if you don't start reaching for the sky early, it takes longer to get there.
CAD isn't going to make the average rookie team have an entirely straight frame, properly aligned sprockets and axles, proper chain tensioning, or the general machining precision necessary to have a fully reliable #25 chain drive. While everything may work fine in the computer, it doesn't always translate to the real robot.
#35 chain is plenty reliable and competitive for any team, not just rookies. While #25 has its advantages, I'd suggest rookies spend their resources and times developing other aspects of the drive and whole robot rather than worrying about #25 chain just yet. Spend more of those resources on better wheels, transmissions, electronics, or manipulators (or about anything else). Get done with your drive a little bit quicker with the supplied #35 and let your programmers have more time.

The best thing for a rookie to do is come up with a reliable, fully-functioning, usable drive with enough time for their programmers and other sub-systems to have access to the bot to do what work they need to do. That way they can spend more time programming, testing, de-bugging, and integrating the systems, as well as the all important training of the drivers.
__________________
Being correct doesn't mean you don't have to explain yourself.