Hi everyone,
I want to clarify some things that have been going around the listserv today...
 
First of all, according to the "Active Robot Touched" rule, anytime a robot is touched (other than to start it), it is considered inactive, no matter where it is, and must be returned to base if it is not already there.  According to the "Muscle Action" rule, dropping/loading something on an active robot is considered an indirect touch and forces a restart.  Although this would not incur a touch penalty if done in base, it would force you to restart the robot by an approved method ("Start Procedure" lists these as touching a button or signal a sensor).  This would dis-allow the use of a simple pause to reload your robot (however it would be legal to place something in front of the robot as long as the robot is not actually contacted and that object is completely in base).
 
In other questions asked, if the robot is only partially out of the base (any part of the robot still breaks the plane of the base), there is no touch penalty, but it must be returned to the base and restarted. 
 
If the robot encounters a model out of base (not one being moved from the base) and is touched while in contact with that model, then that model/strategic object is removed from play. If the robot has left the model/strategic object and moved on (and is no longer making contact) then the action done stands. 
 
This is completely separate from the touch penalty question.  Touch penalty only has to do with whether or not the robot is still partially in base or completely out of base when touched.  Again, if any part of it breaks the plane of base, the robot is in base and there is no touch penalty but a restart will be required. 
 
Hope this helps clarify the questions.
 
Karen
VA/DC FLL Head Referee
 
-------- Original Message --------
Subject: [VADCFLL-L] Moving robot in base while program pauses
From: Annette Holloway <[log in to unmask]>
Date: Thu, November 13, 2008 10:21 am
To: [log in to unmask]

I have a mission question.

Is it legal to start mission #1 from base (touch the brick to start the
program),
have it do mission #1 COMPLETELY,
have it automatically come back to base (or it never leaves the base),
(the program then pauses for 3 seconds while the driver repositions the
robot for the next mission and lets go without initiating another program),
then the robot performs mission #2 by going out of and coming back to
base? (A touch sensor is not an option right now)

The driver would be touching the robot in base while the program itself
pauses autonomously - the driver would not have to press a button to
initiate the next program.

I would think this could be done for all missions if a team wanted to.
Then they would have one big program and not have to hit any buttons if
they timed the transition correctly.
Instead of being illegal, shouldn't a team be praised for being
creative? :)

Annette Holloway

______________________________________________________________
To UNSUBSCRIBE or CHANGE YOUR SETTINGS, please visit https://listserv.jmu.edu/archives/vadcfll-l.html and select "Join or leave the list".

If you want to join the VADCFLL-ADMIN-L mailing list - to which FLL administrative announcements will be distributed - visit https://listserv.jmu.edu/archives/vadcfll-admin-l.html and select "Join or leave the list".
 ______________________________________________________________ ______________________________________________________________ To UNSUBSCRIBE or CHANGE YOUR SUBSCRIPTION, please visit https://listserv.jmu.edu/archives/vadcfll-l.html and select "Join or leave the list". If you want to join the VADCFLL-ADMIN-L mailing list - to which FLL administrative announcements will be distributed - visit https://listserv.jmu.edu/archives/vadcfll-admin-l.html and select "Join or leave the list".