![]() |
Question about Netting
Our team is thinking about using a net or net type material to hold the balls. We know that the robot cannot extend outside the 28 X 38 X 60, but what if it can be pulled to extend out of those dimension? Since netting is usually stretchy, to some extent at least, would that pose a problem or should it be ok?
|
Re: Question about Netting
Sounds like a question for the GDC.
My first question to you though would be, what would this net be pulled by to extend out of your envelope, since no device can exit another robots envelope to enter yours? If it's designed in such a way that it always deflects to some extend I'd say it most likely would violate the envelope rule. If it would be some sort of accidental thing that COULD happen, but would not give you an advantage and would not be considered "normal" operation, then I would chance saying it's probably not a big deal, but would obviously be at the discretion of the refs and/or inspectors. |
Re: Question about Netting
We were thinking that the judges might pull it out while we are being measured. Not sure if they would, since we have never used netting before. I figured I might as well ask. :)
|
Re: Question about Netting
Quote:
1) Entanglement with another bot, which then pulls you outside of your bumper perimeter. As another robot would be causing you to break a rule, you wouldn't be penalized for expanding too far (<G18>). However, your robot would be an entanglement hazard- you might not get penalized (DQed) for a one-time problem, but it would be wise to build your robot so that it does not pose an obvious risk of entanglement (<G33>). Quote:
Quote:
This would earn you a penalty, because you have violated the robot rules (<R16>, <G16>). Quote:
Quote:
Edit: I see that while I was typing and searching down manual quotes, you clarified a bit. When you get measured, they are going to stick your robot in a box which represents the maximum robot size. If you fit in the box, you're good to go. They won't pull out the netting, but if it does expand beyond the bumper perimeter enough for the refs to notice during the course of a match, then see the two circumstances I posted above. |
Re: Question about Netting
I wouldn't reccomend having netting that can get snagged by another bot. In 2006, we were debating using netting and decided on a more solid fabric.
|
Re: Question about Netting
I don't think entanglement issues will be seen all that often this year since robots are not allowed to extend outside of their bumper zones, but a more hefty material may be in order just for a more rugged design's sake.
|
Re: Question about Netting
We used chicken wire for the poof balls in 2006. It worked okay, but I left that build day with quite a few scratches on my hands.
|
Re: Question about Netting
Quote:
|
Re: Question about Netting
Quote:
Quote:
We used a loose netting in 2006 for our robot, but veiled the entire robot in a mesh fabric (we nicknamed it "the corpse bride" because of this) for safety and endurance issues. It held up through the season, and we have since removed the mesh from the outside. However, I'm going to have to agree with the above posters- a substantial fabric would probably be preferred. Also, scratchy things like chicken wire (or the aluminum guards we also had on our 06 robot) are bad news- you end up with lots of scratched and bleeding students, especially when making repairs. |
Re: Question about Netting
Your real question here should be: will the balls force the netting out when you're full.
If that netting extend over your bumpers - not past them, just over them, you're illegal. You may not have anything extend past the bumper perimeter. The bumper perimeter is the inside edges of your bumpers. |
Re: Question about Netting
I'm not sure, but make sure that netting is permitted in the bill off parts.
|
Re: Question about Netting
Quote:
|
Re: Question about Netting
Quote:
-dave . |
Re: Question about Netting
Quote:
|
| All times are GMT -5. The time now is 09:01. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi