This design could potentially be much better if it were centered in the robot to prevent it from being unbalanced. I look forward to see what you come up with next.
<R7> part e states that you can use…
An unlimited amount of 1/8” (or local metric equivalent), braided, nylon rope
The string mechanism is theoretically infinitely scalable and might seem like a great idea. The problem is holding the cubes from sliding horizontally since they are very slippery. This would require the string to be very tight but it still might not fix the problem and just cause other problems. The idea of using non-slip mesh instead of the rope has also come up but it might not be such a good idea either, but without testing we wouldn’t know for sure. Most likely these designs wouldn’t hold more than a couple cubes. Although someone is building the design and I am interest to see how it works…
I am however working on another design which could be much more viable. This new design will have a completely rigid cube hold and do internal stacking. The design will include a completely passive intake that even holds cube with more force the more cubes there are. Here is quick sketch of the design…
A new video will come out showing exactly how this new design will work.
Have you seen @Codec’s first concept?
I don’t know how that could be accomplished, but if it’s done, that would be incredible. I look forward to seeing it!
But would there be penalty if the blocks fall?
If it’s caused by the alliance that would be negatively affected, no, there is no additional penalty other than a loss of points.
But, if it’s caused by the opposing alliance, it would count as a warning or automatic DQ.
Check SG3
Well, the video is only a video made with editing software. It might only be large enough for 4 to 5 cubes, but if you have enough string, It’s fine.
My team has begun to build the robot. The string is not easily ripped or cut.
Doesn’t the mechanism get less and less sturdy as the amount of cubes increases? Also regarding the rules, is it legal to hit your opponents stack so it falls off?
It is legal to knock over the stack, but the design has been inproved and is shown here
Just to be clear, It is not legal to knock over an opponent’s scored stack as specified in <SG3>.
Don’t want people getting misinformation.
<SG3> refers to protected zones and protected towers. I think they were talking about robots holding stacks not in protected zones. In which case you can knock over their stack; <SG3> does state that you cannot knock cubes stacks scored in protected zones and protected towers…
<SG3>
Stay away from your opponent’s protected areas. Robots may not intentionally or accidentally, directly or indirectly, perform the following actions:
- Contact an opponent Robot which is fully contained within
their Protected Zone. - Contact any Scored Cubes in either of opposing Alliance’s
Goal Zones. - Contact any Placed Cubes in the opposing Alliance Tower.
- Contact either of the opposing Alliance’s Goal Zones or
Barriers. - Contact an opposing Alliance’s Inner Protected Zone
- Cause Scored Cubes within the opponent’s Protected Zone
to no longer meet the definition of Scored (i.e. “knock over
their stack”). - Cause a Cube which is Placed in the opposing Alliance
Tower to no longer meet the definition of Placed (i.e.
“remove it from the Alliance Tower”).
I think you will see an update to the initial Game Manual to include goals for scored stacks.
I might be wrong…
Still the clarification stands that there are stacks you can not knock over.
Yes, I meant stacks that were on/in the robot, not the scored stacks.
Thank you for clearing up the doubt! This was my main worry with this design, but now I don’t need to! I’ll definitely try out this design now.
I thought the same thing. It looks like we are wrong.
https://www.robotevents.com/VRC/2019-2020/QA/288
I think this will lead to some very difficult calls as to what is or is not match affecting.
Game Manual update will be tomorrow. Will see what it brings for specific wording. Right now you still need to be careful for opposing scored stacks, immediate DQ in protected zone, and DQ if match effecting in unprotected.
Is there a way I can find out where the other motors are?
Please Answer Once You See This Post