Ben from Panda Cubs asks about pushing a button on the Robot multiple times
in the Launch Area.
In his example, pushing the button the first time does not make the robot
GO, so it isn't a Launch (Rule 08), and the second push isn't an
Interruption, since the Robot wasn't Launched (Rule 09).
The second button push makes the robot GO, so it is the actual Launch of
As a referee, I've definitely seen Technicians appear to push a button and
nothing happens, so the Technician pushes the button again and the robot
starts moving. Referees will keep waiting until the robot moves. We can't
assume anything, because we don't know what sequence of buttons the team
needs to press to start the robot on its way.
Virginia-DC FLL Referee Advisor
On Sun, Nov 3, 2019 at 8:45 PM Panda Cubs 38690 <[log in to unmask]>
> My team has a question about the use of a reminder message during launch.
> Let’s say at the start of a program, before the robot has moved, text
> appears on the brick screen, reminding the operator to verify something,
> then waiting for a button press before proceeding. If all is well, the
> button is pressed and the program continues. If not, the appropriate
> adjustment is made (keeping the robot in the launch area) before the button
> is pressed.
> How would this be viewed under update RG07? Is touching a button (or
> more) after starting a program considered an interruption, thus requiring
> that the program be stopped and restarted from the beginning? If so, the
> operator would essentially find themselves stuck in an endless “loop”,
> forced to restart each time they responded to the message.
> Thank you,
> Ben Clark
> Panda Cubs 38690
-- To UNSUBSCRIBE or CHANGE your settings, please visit https://listserv.jmu.edu/archives/vadcfll-l.html and select "Join or leave the list".
-- VADCFLL administrative announcements are sent via VADCFLL-ANNOUNCEMENTS-L. Visit https://listserv.jmu.edu/archives/vadcfll-ANNOUNCEMENTS-l.html to subscribe.