|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: Beware of R16 your robot design may be too big.
Quote:
It's possible that FIRST would make a rule saying that your robot has to be mechanically incapable of exceeding the size limit, but I find that unlikely. I can see them pulling out tape measures, but as I mentioned above, that isn't equivalent to making sure to robot fits in a cylinder. |
|
#2
|
||||
|
||||
|
Re: Beware of R16 your robot design may be too big.
It would make refereeing a lot easier if the inspectors could determine if it is physically possible for a robot to exceed the 80" rule and mark it on the inspection sticker. If I know that a robot definitely can't break that rule, then I don't have to focus on supervising to see if it violates it.
|
|
#3
|
|||||
|
|||||
|
Re: Beware of R16 your robot design may be too big.
And even if the robot is mechanically capable of leaving the 80" cylinder area, code can allow for mechanisms to be in the right position at all times. (ie: a double jointed arm)
The manual does not outline a process for checking this violation and it is not in the inspection checklist. As I see it now the rule is way to vague to be able to follow correctly. Hopefully they will respond in the Q&A or in the next team update. Does anybody recall any penalties handed out for this rule last year? |
|
#4
|
||||
|
||||
|
Re: Beware of R16 your robot design may be too big.
I don't recall any being handed out at Great lakes.
For our part, after arriving at competition, we found that the process of deploying our gripper caused us to exceed the 72" rule albeit for less than 1 sec., so we tied up the gripper and in the name of GP (and not wanting to be the source of a penalty) didn't deploy it for the entire competition. We could still run defense, and climb on other bots, so we still did fine, and ended up with the Sportsmanship Award. Went home feeling good about ourselves and the competition. We fixed it, and had fun at Kettering in the fall. Steve |
|
#5
|
|||||
|
|||||
|
Re: Beware of R16 your robot design may be too big.
Quote:
There are ways to maximize coverage and still maximize the amount of cylinder still available... It wouldn't be a bad idea to have the bumpers excluded, but that makes the refs' job a bit harder. Bumpers can give a nice easy reference. Yep. One or two teams at L.A. were measured post-match after accidental ramp deployment. At least one didn't pass. |
|
#6
|
|||||
|
|||||
|
Re: Beware of R16 your robot design may be too big.
Quote:
Quote:
|
|
#7
|
|||||
|
|||||
|
Re: Beware of R16 your robot design may be too big.
Ah, OK. I couldn't remember the bumper contact being a requirement--no metal on metal this year, I guess.
|
|
#8
|
||||
|
||||
|
Re: Beware of R16 your robot design may be too big.
Quote:
Per EricH: I believe that ALL parts of the robot within the bumper zone must be within 10 degrees of vertical. (And the rule is 2/3 of the perimeter is required to be bumpered.) Correct, I just assumed that the bumpers would be vertical. Per EricH: It wouldn't be a bad idea to have the bumpers excluded, but that makes the refs' job a bit harder. Bumpers can give a nice easy reference. Maybe it would make the job easier since the bumpers typically are not attached at weigh-in/sizing. The inspectors could make this determination before the robot ever hits the track. I could easily see two vertical poles 80 inches apart with the robot on a flat cart. The team would to have physically move anything that goes beyond the starting envelope through its full range of motion. If at anytime the robot and manipulator or whatever can not pass between the post the robot it is not constructed "in accordance with all of the 2008 FRC rules" (quote from Inspection Checklist) and would not pass inspection. You would not have to attach your bumpers which are usually off the robot at this time to prove compliance with R16. It almost makes R16 obsolete. However, if you were using more than 80 inches of your infinite height in the playing configuration and tipped over before retracting you could still get the penalty on the field. That is the only time the refs would have to worry about R16. The top of the overpass will be approximately 80", within an inch or two anyway, and could easily be used as a visual reference when a robot is tipping (i.e. was it taller than the overpass when it fell or not) and my guess is that near the overpass is where most teams will be going higher than 80 inches to begin with. I could see that this would become a pain if you have to power up your robot to have it move through the range of motions during weigh-in. However, for those teams that are using programing vs hard stops to limit motion it would be an ideal time to prove out their software. Per GaryV: It's there - I had to look to be sure. I'm not sure if the requirement to bump with or against a bumper was added in the revised G38 or not. They only added: during teleoperated period, in revision #2 Last edited by ALIBI : 14-01-2008 at 13:38. |
|
#9
|
||||
|
||||
|
Re: Beware of R16 your robot design may be too big.
I recall it happening at every competition I attended (VCU, Chesapeake, and Championship). The reason every time was a ramp deploying early and outside the home zone. I do not know of any time where it was called for an arm extending beyond the size limits.
|
|
#10
|
||||
|
||||
|
Re: Beware of R16 your robot design may be too big.
I know that this was called a number of times. One that sticks in my mind was 45 being flagged at IRI because their gripper got snagged on the rack, and while backing out they went nearly horizontal. I remember robots with long arms being flagged after tipping at regionals, too, and I expect that to continue this year if a team doesn't e-stop first.
|
|
#11
|
|||||
|
|||||
|
Re: Beware of R16 your robot design may be too big.
Quote:
Quote:
In this year's rules it is written that a robot cannot cause another robot to be penalized. So in my opinion if one robot knocks another over and that robot is now outside the mythical cylinder, there should be no penalty. |
|
#12
|
||||
|
||||
|
Re: Beware of R16 your robot design may be too big.
This is an interesting interpretation that I haven't heard before. I can envision some scenarios where a robot could violate <R16> due to contact with another robot and not be penalized. I wouldn't say that this is a blanket rule... even if the other team tipped you, breaking <R16> might have been avoidable (much in the same way that you could potentially avoid a clockwise crossing, even if you were bumped). There are going to be some very interesting judgment calls for the referees this year.
|
|
#13
|
|||
|
|||
|
Re: Beware of R16 your robot design may be too big.
If, based on the explanation in the FIRST Q&A, the parenthetic example is NOT the rule.
The rule is the part of the sentence prior to the cylinder example. Measured horizontally includes all orientations of the robot - upright and fallen over. Some infractions during the game will be obvious (fallen over while fully extended) - while some will be very difficult to determine without replicating the exact orientation after the match. While the geometry I have been working on, is capable of reaching beyond the 80 inches - we will not allow that to occur by limiting the rotation of the joints using pots and mechanical stops. If you have a similar situation, would you demonstrate your maximum reach to the head ref during the practice matches - in order to avoid any issues later during the matches or would you be afraid to bring additional attention to your robot? Meaning, the ref then tells the other refs to "keep an eye on that one". Mike Last edited by meaubry : 15-01-2008 at 21:28. Reason: revised to fix my mistake regarding rule interpretation |
|
#14
|
||||
|
||||
|
Re: Beware of R16 your robot design may be too big.
Mike,
Your robot would probably draw attention on the track anyway if it looks like it was approaching 80 inches. In that case, if the head ref. had prior knowledge he/she could immediately say, I looked at that robot in the pits and they demonstrated their hard stops and programing to me and it does not exceed 80 inches, let's move on. Getting a quick definative answer would probably end any suspicions on the spot. I would like to see a range of motion test done while being inspected. That way the only dimensional rule that the refs. would have to worry about would be when a robot tips over. Not sure how practical implementing a test like that would be though. EDIT: In the pits or during the practice matches. |
|
#15
|
||||
|
||||
|
Re: Beware of R16 your robot design may be too big.
How about if it was enforced in the same way that the ball velocity rule was in 2006? Assume that everyone is following the rules, but if a referee has doubts as to whether a team is complying, they can request a demonstration before the robot is allowed to compete again. I'd restrict it to just refs being allowed to request this (as opposed to 2006, where anyone was allowed to complain), but this seems like a much more time-efficient way to examine only the borderline cases and flagrant violators.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| What's your robot design? | NeoRyu777 | General Forum | 19 | 10-02-2006 17:51 |
| So your original robot design was..... | LightWaves1636 | General Forum | 23 | 05-02-2006 03:36 |
| How do you design your robot? | Gui Cavalcanti | General Forum | 23 | 16-11-2003 18:33 |
| Beware of spending too much time in Chief Delphi Forum! | Ken Leung | Rumor Mill | 42 | 21-05-2003 18:22 |
| Size of the field: too big? too small? | archiver | 2000 | 5 | 23-06-2002 22:44 |