View Single Post
  #40   Spotlight this post!  
Unread 07-01-2008, 13:01
Bongle's Avatar
Bongle Bongle is offline
Registered User
FRC #2702 (REBotics)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2002
Location: Waterloo
Posts: 1,069
Bongle has a reputation beyond reputeBongle has a reputation beyond reputeBongle has a reputation beyond reputeBongle has a reputation beyond reputeBongle has a reputation beyond reputeBongle has a reputation beyond reputeBongle has a reputation beyond reputeBongle has a reputation beyond reputeBongle has a reputation beyond reputeBongle has a reputation beyond reputeBongle has a reputation beyond repute
Send a message via MSN to Bongle
Re: Robocoach signals loophole?

Disclaimer: These are just my interpretations, the official QA forum is a better place for discussions like this.

Quote:
Originally Posted by Uberbots View Post
yeah, but the distinct commands are flipping the bits...
But by flipping the bits, you're still doing a different action depending on your robot's state. Suppose button 1 flips bit 1. If bit 1 is 0, then button 1 sets bit 1 = 1. If bit 1 is 1, then button 1 sets bit 1 to 0. So there, you have two possible actions for button 1: "set bit 1 to 0" and "set bit 1 to 1".

I think you may also conflict with this clause from R65:
Quote:
Signalling devices may
...
• not use changes in the signal states to encode or transmit larger messages
So by doing this bit-flipping stuff, you'd essentially be transmitting a larger message by remembering the robot state in your bitstring.

Another way to look at it is to look at your button press sequence as a large message. Let's say you used buttons 1, 2, and 3 to modify bits, and button 4 as a 'end of command' button. Then your keypress sequence would essentially end up being button-button-button-<enter>, which seems clearly against the spirit of the rules.

Just like dave said at the kickoff, you're not supposed to be able to drive the robot with the remote, you're supposed to give it high level commands and then it does some heavy autonomous work. You shouldn't need 8 commands since there really aren't that many things to do. Plus, you have to consider that driving the robot by IR will probably be impossible anyway. Other robots, 3-foot-wide balls, and parts of your own robot will obscure your IR board, making driving it accurately pretty much impossible.

Last edited by Bongle : 07-01-2008 at 13:07.