Thread: definition of "balancing robot"
View Single Post
  #5   Spotlight this post!  
Unread 24-06-2002, 01:24
archiver archiver is offline
Forum Archival System
#0047 (ChiefDelphi)
  
Join Date: May 2001
Location: Pontiac, MI
Posts: 21,214
archiver has a reputation beyond reputearchiver has a reputation beyond reputearchiver has a reputation beyond reputearchiver has a reputation beyond reputearchiver has a reputation beyond reputearchiver has a reputation beyond reputearchiver has a reputation beyond reputearchiver has a reputation beyond reputearchiver has a reputation beyond reputearchiver has a reputation beyond reputearchiver has a reputation beyond repute
Re: definition of "balancing robot"
Posted by Mike Soukup at 02/24/2001 2:51 PM EST


Engineer on team #111, Wildstang, from Rolling Meadows & Wheeling and Motorola.


In Reply to: definition of "balancing robot"
Posted by bill whitley on 02/24/2001 1:51 PM EST:



My team has been struggling with questions like this for weeks because we're working on WASH, a scouting system for palms (shameless plug here: we're looking for help scouting other divisions at nationals, follow the link at the bottom). We went back and forth, but finally decided that it doesn't matter how the team balances, just as long as they balance.

One team could have an excellent driver that balances the bridge every time in 5 seconds. Another team could have a robot that uses an automated process with a balance button, but fails half the time & it takes 10 seconds minimum. In this case I would want the team that does it manually. If the case were reversed (good automation vs bad manual) I would want the automated robot.

There is no inherent advantage or disadvantage to either manual or automatic balancing. In the end, the only thing that matters is if the team can balance quickly & reliabliy, regardless of how it's done.

Mike



__________________
This message was archived from an earlier forum system. Some information may have been left out. Start new discussion in the current forums, and refer back to these threads when necessary.