|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Team Update #13
http://usfirst.org/uploadedFiles/Rob...pdate%2013.pdf
Tower triggering clarification and Week 0 Observations |
|
#2
|
|||
|
|||
|
Re: Team Update #13
I'm really not a fan of the <R74> clarification. It limits innovation for no reason. 1075 has used the exact configuration described in several past FRC games, and experienced no problems, even going so far as to win a Rockwell Automation Innovation in Control award for it at the 2007 GTR.
I can understand limiting innovation for safety reasons, but theres no reason to outlaw a number of different ways to accomplish multi-position pneumatic control. |
|
#3
|
||||
|
||||
|
Re: Team Update #13
so we have solenoids controling air to other solenoids, is that a loophole? In reality the solenoid is controling the other solenoid not cylinders... Honestly First is really making this years game a game with exact robots and little variety. We based our whole arm lifting off of this! HELP OUR TEAM!
|
|
#4
|
|||||
|
|||||
|
Re: Team Update #13
In regards to <G23>, does a tower include the pole AND the base, or only the metal pole?
|
|
#5
|
|||||
|
|||||
|
Re: Team Update #13
Quote:
Quote:
|
|
#6
|
|||||
|
|||||
|
Re: Team Update #13
Quote:
|
|
#7
|
|||
|
|||
|
Re: Team Update #13
"Remember that all parts of the ROBOT must fit in STARTING CONFIGURATION volume before the start of the MATCH, even if POSSESSING an UBERTUBE."
Can a tube be outside the starting volume? |
|
#8
|
||||
|
||||
|
Re: Team Update #13
A tube can be outside the starting volume as long as no parts of the robot are.
I.e., if your claw opens to hold a tube, and the claw open fits in Starting Configuration, it's okay even if your tube is out of it. |
|
#9
|
||||
|
||||
|
Re: Team Update #13
Quote:
How can they expect teams to fix the problem if they give out the change the day all robots need to be sealed? Ours was crated saturday and put in the shipping room. I wonder how many inspectors will read into that rule like that; a good speaker could easily explain how this particular two solenoid setup is legal. Well it looks like we have to go talk to another team to order three more cylinders... good luck to the rest of you. Edit: but still looking at the rule, it gave the example of cutting off the exhaust when we are cutting off all the air in general... "Rule <R74>... For example, one solenoid may not be used to provide pressurized air through one port of a cylinder while a second solenoid is used to close the exhaust port of that cylinder..." Last edited by bobosalad : 22-02-2011 at 23:58. |
|
#10
|
||||
|
||||
|
Re: Team Update #13
Quote:
I'll try and take picture of what we have through the bag if you want, but you can get the idea from this: http://www.youtube.com/user/wilsonmw04?feature=mhum Take this as a challange instead of a setback. It changed the way we approached this new problem. It turned out that this new system made control so much easier than what we had planned to do. |
|
#11
|
||||
|
||||
|
Re: Team Update #13
Maybe it's just a little late to be assigning new penalties?
|
|
#12
|
||||
|
||||
|
Re: Team Update #13
Quote:
And anyway, it's never too late to make the rules harsher, doesn't gracious professionalism say that you shouldn't try to break rules? Especially with red and yellow cards. I think they added it to discourage teams from encouraging alliance partners from getting a yellow/red card if it's a "good cause" |
|
#13
|
||||
|
||||
|
Re: Team Update #13
Quote:
I can concede that in this sort of risk calculus, one should factor in the possibility that FIRST will change the rules—but knowing that something like this could be changed isn't at all the same as being enthusiastic when that change is made. Quote:
Or maybe they wanted to make sure that teams don't provoke their opponents into being carded (<G61> doesn't apply if there's no penalty). I see that sort of provocation as being a fairly legitimate strategy—because it's a team's own responsibility to avoid violations, irrespective of the trickery of their opponents. But maybe the most likely case would be that FIRST simply overlooked that aspect of the penalty structure, and wanted to remedy the omission. In that case, maybe the lesson to be learned is to proofread early and often? Basically, someone presumably made a determination that the benefits of amending the rules outweigh the detriments of subjecting teams to those same amendments at this point in the season. I don't really see a combination of circumstances that would justify a change with relatively little practical effect upon the behaviour of offenders, but which imposes additional burdens (relatively minor, though they may be) on the rest of the teams at this late date. Edit: As updates go, this isn't really worth any outrage, and it's by no means one of the most significant rule changes in the history of FIRST. It's really only the inauspicious timing that makes it worth commenting upon—this is more than six weeks into the season, after all. Last edited by Tristan Lall : 23-02-2011 at 04:05. Reason: Adding a comment. |
|
#14
|
||||
|
||||
|
Re: Team Update #13
While I'm glad they added the penalties to the cards, I do not see a single situation where intentionally getting a yellow or red card is a good idea even before this update!
|
|
#15
|
|||
|
|||
|
Re: Team Update #13
The number of rule changes, not just clarifications, so late in the process bothers me. It's not any rule in particular, just the magnitude of the changes.
A successful game needs to be easy. It need to be easy to understand, easy to play, easy to ref and easy on the rookies. I'm not seeing that this year. When you get to your competition, give your refs and inspectors a hug. They will need it. Find the rookie teams and see how they are doing. It will be especially hard on them this year. I hope we will not look back on this game and rename it "Red Card" Last edited by JohnBoucher : 23-02-2011 at 07:13. Reason: Inspectors also |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|