Re: Holding Down Buttons on the Remote
 

Isn't holding the button down outputting the same thing as rapidly pressing the button? The remote is emitting pulses even if you hold it down...

Re: Holding Down Buttons on the Remote
 

that is exactly what i was thinking.
it is sending out pulses. that would be the same as pushing the button really fast.
like for example: if you are sending pulses that drive your robot forward but making the robot "pulse" forward. wouldnt that be legal? because each pulse it doing one action that drives the robot forward a little but. so holding it or pressing it really fast would be the same and drive the bot forward.

Re: Holding Down Buttons on the Remote
 

one of our earlier autonomous modes worked like this:

it had two vectors: the forward vector and the angular vector
these vectors constantly return to 0 using a linear ramping technique
when a forward signal is received from the IR board, it ramps the speed up 20%. further presses of the button will yield more speed (linearly, 20 40 60 80 100)
when a turn left/right signal is received, it ramps up the turning vectors inverse-exponentially (to improve turning)
there is also a stop command which would reverse the robot for a couple ticks

we ended up ditching it because it was too borderline within the rules, the IR signal dropped out at the other end, and we made a better autonomous mode after that.

I dunno about the rules though... a single button press always does the same "add 20%" thing, and they arent held down in order to do it. any thoughts?

Re: Holding Down Buttons on the Remote
 

Uberbots,
Seems okay - changing orientation by a fixed amount is legal, and I guess the ramping back would be an autonomous thing.

seanl,
I agree that you could use semantics to get around the "no holding buttons down" rule, but it would be nice to stay within the spirit of GDC's decisions as well as the letter.