View Single Post
  #64   Spotlight this post!  
Unread 14-01-2008, 09:43
Gary Dillard's Avatar Unsung FIRST Hero
Gary Dillard Gary Dillard is offline
Generator of Entropy
AKA: you know, the old bald guy
FRC #2973 (The Mad Rockers)
Team Role: Engineer
 
Join Date: Nov 2001
Rookie Year: 1998
Location: Huntsville, AL
Posts: 1,582
Gary Dillard has a reputation beyond reputeGary Dillard has a reputation beyond reputeGary Dillard has a reputation beyond reputeGary Dillard has a reputation beyond reputeGary Dillard has a reputation beyond reputeGary Dillard has a reputation beyond reputeGary Dillard has a reputation beyond reputeGary Dillard has a reputation beyond reputeGary Dillard has a reputation beyond reputeGary Dillard has a reputation beyond reputeGary Dillard has a reputation beyond repute
Send a message via AIM to Gary Dillard
Re: Beware of R16 your robot design may be too big.

Quote:
Originally Posted by StevenB View Post
Until you do it on the field though, there isn't any penalty. They can't fail your inspection because of it, any more than they would be able to fail you for being able to violently ram another robot. The most they could do is make a list of robots to watch.
Very true; it is not on the inspection checklist. But this is:
Team Compliance Statement
We, the Team Mentor and Team Captain, attest by our signing below, that our team’s robot was built after the 2008 Kickoff on January 5, 2008 and in accordance with all of the 2008 FRC rules, including all Fabrication Schedule rules (reference Section 8.3.3). We have conducted our own inspection and determined that our robot satisfies all of the 2008 FRC rules for robot design.

Last year when I noticed some a couples of team that looked like they were exceeding the allowable envelope, I pointed it out to them. They were not aware of it, and made the appropriate corrections to stay within the envelope. From my experience, no one in this competition wants to cheat or try to get away with an obvious violation of the rules that everyone else had followed, so usually it's a team that was unaware of the requirement or who misunderstood the requirement and they want to make it right when it is pointed out.
__________________
Close enough to taste it, too far to reach it