View Single Post
  #24   Spotlight this post!  
Unread 04-02-2008, 11:55
Jon Stratis's Avatar
Jon Stratis Jon Stratis is offline
Mentor, LRI, MN RPC
FRC #2177 (The Robettes)
Team Role: Mentor
 
Join Date: Feb 2007
Rookie Year: 2006
Location: Minnesota
Posts: 3,839
Jon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond reputeJon Stratis has a reputation beyond repute
Re: Start/Stop as one IR function?

Quote:
Originally Posted by SlimBoJones View Post
This is all based on the Q&A response Steve W quoted above at: http://forums.usfirst.org/showthread.php?t=8460

Start/Stop as a single RoboCoach command can be achieved if you use encoders (or any other sensor) to track whether your robot is in motion or not. You can then write a command that will stop a robot in motion, or start a stationary robot, but the RC's decision must be based on input from a sensor on the robot.

You cannot simply save a state in software that keeps track of whether your robot is moving based on when or how many times you've sent the RoboCoach command. i.e. 1st push start, 2nd push stop, toggling back and forth.

It's an important distinction to make between those two scenarios. It is possible to achieve the behaviour you're looking for, but you need to be mindful of how to go about doing it.
According to the GDC, such a thing may not be against the letter of the rules, but it is certainly against the spirit. So, if you're thinking of employing such a system, you should question what is more important for a FIRST team: following the letter and intent of the rules, or finding a sneaky way around them to perform better in the competition? I guess it really comes down to a question of what your teams goal is - to have the best performing robot, or to have the best performing team.

Quote:
Question:

All of the Robocoach rulings I have read seem to outlaw the notion of software state... the action conveyed by the press of a button should be independent of any previous button presses. However, the actions are allowed to be dependent on sensor readings. Is a hardware device solely intended to keep track of state (such as a servo coupled to a multi-position switch which feeds back to the RC) in order to address a larger set of commands in violation of the letter or spirit of any rules?

Answer:
This would be a violation of the spirit, but not necessarily the letter, of the rules.