|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#61
|
||||
|
||||
|
Re: Beware of R16 your robot design may be too big.
We are a Rookie Team this year and actually had a pretty good idea(at least I think so) to grab the ball with 2 rings but they will probably be outside the R16 rule so once again we're back to drawing board
. Im really wondering how we could come up with a design that wouldn't cost us penalties for the new rule and so far I got nothing |
|
#62
|
|||||
|
|||||
|
Re: Beware of R16 your robot design may be too big.
see if you can contact the ball above and below, with some type of (safe) prongs about 26" apart, and tilt it up and back.
|
|
#63
|
|||||
|
|||||
|
Re: Beware of R16 your robot design may be too big.
Certainly 72x72 was called last year, mostly for when a bot's ramps lowered prematurely.
|
|
#64
|
||||||
|
||||||
|
Re: Beware of R16 your robot design may be too big.
Quote:
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. |
|
#65
|
|||||
|
|||||
|
Re: Beware of R16 your robot design may be too big.
Our machine will be capable of exceeding the envelope, but will be programmed to stay within it, using potentiometers. We should be well within the cylinder.
However, I do worry about being over scrutinized, just because of the physical possibility. Also, last year we were tipped over twice during the season by a collision, while scoring tubes. Since we were fully extended when we were hit. We were called for a 72" violation, while lying there helpless on our backs. (ouch!) I saw this happen to other teams as well. So if you get tipped you may be in violation of the cylinder rule.And finally, I really hope that FIRST can make a definitive statement about how this rule will be enforced. Many teams are still in the early design stage and it will make a huge difference. |
|
#66
|
|||||
|
|||||
|
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. |
|
#67
|
||||
|
||||
|
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.
|
|
#68
|
|||||
|
|||||
|
Re: Beware of R16 your robot design may be too big.
Quote:
Quote:
|
|
#69
|
|||||
|
|||||
|
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.
|
|
#70
|
||||
|
||||
|
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. |
|
#71
|
|||||
|
|||||
|
Re: Beware of R16 your robot design may be too big.
Quote:
It was far more obvious that I would imagine R16 violations to be, this year. |
|
#73
|
||||
|
||||
|
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.
|
|
#74
|
|||||
|
|||||
|
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. |
|
#75
|
||||
|
||||
|
Re: Beware of R16 your robot design may be too big.
Quote:
|
![]() |
| 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 |