View Single Post
  #5   Spotlight this post!  
Unread 17-03-2011, 09:30
Racer26 Racer26 is offline
Registered User
no team
Team Role: Alumni
 
Join Date: Apr 2003
Rookie Year: 2003
Location: Beaverton, ON
Posts: 2,229
Racer26 has a reputation beyond reputeRacer26 has a reputation beyond reputeRacer26 has a reputation beyond reputeRacer26 has a reputation beyond reputeRacer26 has a reputation beyond reputeRacer26 has a reputation beyond reputeRacer26 has a reputation beyond reputeRacer26 has a reputation beyond reputeRacer26 has a reputation beyond reputeRacer26 has a reputation beyond reputeRacer26 has a reputation beyond repute
Re: Minibot TRIGGERing

As far as I understand it, the situation is this:

Week 0 events (like Suffield Shakedown) were having issues, where a HOSTBOT colliding with the TOWER base with sufficient force could TRIGGER the TOWER.

FIRST HQ sent the message to Week 1 events to turn down a sensitivity setting on the TOWERs, which resulted in the TOWER requiring a signal lasting longer than X ms to TRIGGER.

At Week 1 events, many of the fastest MINIBOTs, while imparting the 2-4N force required to TRIGGER the TOWERs specified in the manual, did not dwell at the top of the TOWER for long enough to TRIGGER the TOWER, given the change that was made.

FIRST HQ made the call and told the refs at Week 1 events to manually score the TOWERs.

For Week 2, FIRST HQ sent out a parts kit to each event, which the setup team at each event had to apply to the TOWERs. This kit was supposed to change how the TOWERs work, in order to eliminate the dwell time that was required in Week 1.

The refs at Week 2 events were still scoring TOWERs manually, in the event that they did not score automatically.

Now in TU18, FIRST HQ has handed down the decision that refs are not to score manually anymore.
Reply With Quote