Go to Post "By three ways we may learn wisdom: first is by reflection, which is noblest; second by imitation, which is easiest; and third by experience , which is the bitterest." - bEdhEd [more]
Home
Go Back   Chief Delphi > Technical > Technical Discussion
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #24   Spotlight this post!  
Unread 14-02-2011, 17:44
EricH's Avatar
EricH EricH is online now
New year, new team
FRC #1197 (Torbots)
Team Role: Engineer
 
Join Date: Jan 2005
Rookie Year: 2003
Location: SoCal
Posts: 19,752
EricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond repute
Re: Building a claw post-ship

It is not the intent of the GDC. I agree with you on that, Al.

Quote:
UPGRADE PARTS - a COMPONENT or MECHANISM intended to provide additional functionality not currently available on the ROBOT. UPGRADE PARTS may be COTS items or custom FABRICATED ITEMS, and may either add to or replace existing functionality. Example: A HOSTBOT is designed with a c-channel frame. The system works well, but can be misshapen if hit aggressively. The team adds two more pieces of c-channel to brace the frame and prevent this problem. The c-channel is identical to that already on the HOSTBOT. The new pieces of c-channel would be considered UPGRADE PARTS even though they are the same as the ones already in place, as they alter the functionality of the HOSTBOT and provide new capability.
So, I can add functionality, or replace it, or otherwise make it better.

Quote:
<R23> During the BUILD SEASON, teams are to design and fabricate all the COMPONENTS and MECHANISMS required to complete their ROBOT. When the ROBOT shipment deadline arrives, all work on the ROBOT must cease and the ROBOT must be placed in a “hands-off” condition. The entire ROBOT (including all FABRICATED ITEMS intended for use during the competition in alternative configurations of the ROBOT) must be crated or bagged (as appropriate for your event), and out of team hands by the shipment deadline specified in the FRC Administrative Manual, Section 5 (with the exception of the items covered by the WITHHOLDING ALLOWANCE). Teams are encouraged to use all the materials, sources and resources available to them that are in compliance with the rules of the 2011 FRC during the BUILD SEASON. There is no limit to the amount of time that may be put into this effort during the BUILD SEASON, other than via the realities of the calendar.

Stop work on the robot and ship it at or before the deadline; you have all the calendar time in the build season. Design and fabricate everything.

Quote:
<R24> During the period between ship date and the competitions, all teams may manufacture SPARE, REPLACEMENT, and UPGRADE PARTS, and develop software for their ROBOT at their home facility.
Teams may continue development of any items retained under the WITHHOLDING ALLOWANCE during this period, and then bring them to the competition events. The primary intent of this rule is to allow teams to withhold the ROBOT control system, the OPERATOR CONSOLE, and selected relevant subsystems and access them after the shipping deadline. This will allow teams to have the maximum time possible prior to each competition event to develop and complete the software for their ROBOT while maximizing the potential capabilities provided by the control system.
Between ship/bag and competition, I can build stuff for the robot--spare, replacement, upgrade--without limitation, but I have to bring it in in compliance with <R33>.

The intent is, don't bring in brand-new stuff (arm, deployment system, etc.) that was built after ship. The problem is, it is not prohibited to do so. So, if I were to build a brand-new, not-designed-during-build arm, claw, deployment system, electronics box, or other similar item, that fit into the <R33> allowance, but was built after ship,
I can't be stopped under the current version of the Manual, unless it's over the weight of the allowance (and I can probably take it apart to get into that if I need to). Intent of the GDC can't stop anything unless it's in the Manual as a rule, and while it is expressed, it isn't a rule.

I think we're starting to get over into something like the "What is a robot" debate from 2008, so I'll stop there, with the note that I would expect a slightly clearer "intent note" in the Manual next year.
__________________
Past teams:
2003-2007: FRC0330 BeachBots
2008: FRC1135 Shmoebotics
2012: FRC4046 Schroedinger's Dragons

"Rockets are tricky..."--Elon Musk

 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 01:00.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi