![]() |
robot design question
so, we're trying to figure out if it's legal to design the bot so part of the trailer would be within the robot's dimensions, kind of like something between a fork. Can't find anything in the rules. Help?
|
Re: robot design question
<R18> To attach the TRAILER to the ROBOT, TEAMS must use a Trailer Hitch constructed from
materials provided in the 2009 Kit Of Parts. Details on the construction of the Trailer Hitch are provided in Drawing “GE-09040.” There it is, so if your design includes that then I don't think it's a violation. |
Re: robot design question
Quote:
|
Re: robot design question
Just found this too:
Quote:
|
Re: robot design question
<r18> section D says outer edge, technically the inside of a bracket would be inside edge, thus illegal.
oh well. |
Re: robot design question
Quote:
Oh w8 look at this: Quote:
|
Re: robot design question
i'll try and get a 3d image of what i'm talking about.
|
Re: robot design question
The dimensions of the trailer with bumpers range from approximately 34" (distance between midpoints of opposite sides) to 39" (distance between opposite corners). This would make it near-impossible to fit within a U-shape, as each side of the U could only be 2 inches wide.
Also note that the trailer tongue protrudes about 10" from the trailer, so you would not be able to achieve a tight fit. |
Re: robot design question
Quote:
|
Re: robot design question
![]() image is top view, and not to scale completely, but you get the general idea. The question is "Is this legal?". In so far as what constitutes an "outside" edge. The rule's not completely unambiguious about this. Can parts of the robot "wrap around" the trailer so to speak? Would we be allowed to make a design that limits the lateral movement, through the placement of the hitch alone and no other modifications, of the trailer, assuming that trailer to robot contact is still going to be bumper-to-bumper? EDIT: also, this design won't ever see field time, I kinda wanna keep the real one hidden, so just imagine that the trailer isn't as engulfed as it is here. The same questions apply, though. |
Re: robot design question
I've been doodling that all day with a scale and dimentions, and with the size restrictions, its possible, but hard. If you do, as you sketched, you're in the clear, but there is a rule about the trailed bumper and your robot 's contact, its clearly stated in <R18>.
|
Re: robot design question
Quote:
Alright. |
Re: robot design question
I think what you are talking about is this. (16"x36" contact base)
![]() ![]() ![]() ![]() The red areas are the "blocking spaces where balls can't be thrown. All measurements are ballpark (within 1-2" accurate, Proof of Concept) The robot fits in the "box" and hugs at least half of the trailer. Weight issues might be a problem, but if you make the shroud light enough and place the batteries and heavy stuff in front you might be OK. |
Re: robot design question
A neat design, nice drafting in the short time since kickoff.
My $0.02 is that with such a design, and the way it effectively eats your entire size envelope, you cant hopper up the balls to bring them to your human players more effectively, and you can't really fit a launcher in there either, meaning two key ways of scoring are severely hindered... not sure if its a net gain or not. EDIT: also, the CoG being off center like that could make you easily tippable/have problems with moving on this already difficult to move on surface. Furthermore, strategies like this will just make the human players go for your teammates goals, since they're wide open they're more likely to score there, rendering the protection they give more or less redundant. |
Re: robot design question
Quote:
Is 2/3 of the BUMPER PERIMETER enclosed by bumpers? I think so, if the short pieces are at least 6". BUMPER PERIMETER is defined by the outermost corners of the robot. The "outer" location for the trailer hitch is not defined. |
| All times are GMT -5. The time now is 02:47. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi