Thread: Team Update #18
View Single Post
  #78   Spotlight this post!  
Unread 16-03-2011, 10:51
martin417's Avatar
martin417 martin417 is offline
Opinionated old goat
AKA: Martin Wilson
no team
Team Role: Mentor
 
Join Date: Feb 2008
Rookie Year: 2008
Location: Buford, GA
Posts: 719
martin417 has a reputation beyond reputemartin417 has a reputation beyond reputemartin417 has a reputation beyond reputemartin417 has a reputation beyond reputemartin417 has a reputation beyond reputemartin417 has a reputation beyond reputemartin417 has a reputation beyond reputemartin417 has a reputation beyond reputemartin417 has a reputation beyond reputemartin417 has a reputation beyond reputemartin417 has a reputation beyond repute
Re: Team Update #18

Quote:
Originally Posted by squirrel View Post
The spec is TRIGGERING the TOWER. The spec is not getting there first.

If 254's official towers use the design in the published field drawings, and the minibot does work on them, but not on the modified design tower switches, then I'd say we have a problem.
Quote:
G67> The RACE SCORE is assigned to each ALLIANCE based on the place of finish in the MINIBOT RACE (ties each receive the points for that place):
1st MINIBOT to TRIGGER the TARGET
30 points
2nd MINIBOT to TRIGGER the TARGET
20 points
3rd MINIBOT to TRIGGER the TARGET
15 points
4th MINIBOT to TRIGGER the TARGET
10 points
OK fine. Let's throw out the last paragraph of my post and concentrate on the rest. What is required to TRIGGER the TARGET? If I don't know the answer to that question, how do I design a minibot to reliably TRIGGER the TARGET? Does it take 4N of force? Does it take some force for a specified period of time? Do I need to hit the plate in a certain area? Do I need to tap out morse code on the plate when I get there? I don't care what the specs are, just let us know so we can design a device that meets those specs.
__________________
Former Mentor Team 1771
Former mentor Team 4509
Reply With Quote