View Single Post
  #14   Spotlight this post!  
Unread 03-12-2012, 09:57
Andrew Schreiber Andrew Schreiber is offline
Joining the 900 Meme Team
FRC #0079
 
Join Date: Jan 2005
Rookie Year: 2000
Location: Misplaced Michigander
Posts: 4,060
Andrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond reputeAndrew Schreiber has a reputation beyond repute
Re: Balancing an Arm

Quote:
Originally Posted by DampRobot View Post
I hate to pull out the old "you can always slow it down in software," but I feel like I need to. Most beneficial effects of large reductions (non-backdrivability, high resolution) are the kind that can be essentially duplicated with good software. The only benefit mentioned in this thread that cannot be duplicated with a balanced arm , self righting, is really not a huge advantage 99.5% of the time. Sure, it's nice, but I'd much rather have a quick arm.
Yes, you can "always slow it down in software" but personally I would prefer a mechanical reduction. Reducing speed in software is going to make your motor run harder. Maybe not an issue if you are using something like a CIM but if you are running the FP/BB style motors which are actively cooled by a fan when running you may be asking for trouble running them slower. Additionally, as much as I hate to admit it, software isn't perfect. Sometimes we get weird edge cases that are inadequately tested and an arm that moves physically slower means we have more of a chance to kill the power before it breaks something.
__________________




.