The REAL chokehold of 2016

[nuclearnerd]

Originally Posted by Ari423

You can't block the low goal using anything outside the frame perimeter, which is why he was trying to make the frame perimeter itself block both goals.

Phew!

[JamesCH95]

Check R19 very carefully, specifically the example in the bottom right corner of Fig. 4-4. There is no such thing as a convex frame perimeter, by definition frame perimeters cannot be convex.

If you can make it work with this rule... well, that would be very interesting! As-is your robot example doesn't appear legal.

[nuclearnerd]

You could probably make this work without a convex bumper. You could make the robot a triangle, with two gaps in the "front" bumper. You park on the center batter, and when a robot approaches a low goal you rotate slightly to push the gap intake that corner of the tower.

Since you have to rotate to block, two offensive robots working together could slip a ball past you on the other side, but you would still reduce the number of goals significantly.

I love this effort though. Evolving strategies and robots keeps FRC interesting over the competition season.

[JamesBrown]

I see the model of it at the top of the ramp, but i'm having trouble seeing how the bumpers are going to make it over the Dividers on the batter.

[Zebra_Fact_Man]

Face it: there is no legitimate chokehold for this game. GDC has made it very clear that they don't want any teams breaking the basic game mechanics. From height restrictions, to no-touch zones, to defensive limitations, everything is very cut and dry.

And the one possible break, involving blocking the return passages, someone was smart enough (read: dumb enough) to ask GDC if it would be ok to break the game before they actually did so, to which GDC heavily disincentivized (G21).

[Daniel_LaFleur]

Originally Posted by MaGiC_PiKaChU

Hello CD !

You probably remember my last thread about cheesecake. Well my team decided not to use this strategy for our next regional, because it's just too much pressure. So here we are, making it public

We were able to design a robot (see thumbnails) to completely block access to both low goals at the same time. We were looking at G25 -C


Both low goals now have a maximum opening of about 8". Pretty hard to force a boulder in there

The chokehold, here, is to make any robot that has no high goal capacity literally unable to score. Any alliance that has no high goal shooter could not do anything else than breaching all game, and, as you should know, those points are very limited. The robot has 3 wheel kiwi drive, that allows it to go over the secret passage, and go sideways under the low bar to come back and capture.

We were able to build the robot in about half a day, using only a jigsaw and about 5 pounds of our withholding allowance for parts that required more complex machining. about 40ft of raw aluminum bars make the frame of the robot.
What do you guys think?

Edit: Bumpers as shown are not legal, we are working on iterating on CAD to make it work

Originally Posted by G25B

B. coordinating a blockade of the FIELD with ALLIANCE members

G25B may be employed here as the robot is attempting to blockade the goals.

Also, if this strategy was used against me, I'd instruct my driver to pin the offending robot at 30 seconds left in the match and then back off, and when the offending robot chases me, pin it again ... since it can only drive in one direction to extract itself. This will allow 3 automatic scales as the alliance tries to take the batter.

Originally Posted by G22

G22 ROBOTS may not pin an opponent’s ROBOT for more than five (5) seconds. A ROBOT will be considered pinned until the ROBOTS have separated by at least six (6) feet. The pinning ROBOT(s) must then wait for at least three (3) seconds before attempting to pin the same ROBOT again. Pinning is transitory through other objects. If the pinned ROBOT chases the pinning ROBOT upon retreat, the pinning ROBOT will not be penalized, and the pin will be considered complete

[JamesCH95]

How does this robot navigate the two barriers on the batter that separate the climbing/challenge zones?

[MaGiC_PiKaChU]

Originally Posted by JamesBrown

I see the model of it at the top of the ramp, but i'm having trouble seeing how the bumpers are going to make it over the Dividers on the batter.

bumpers at max height can clear the dividers by 0.5", like on our real robot. The "wings" just fly over the dividers

[ctt956]

To me, it doesn't look tall enough to reach over the batter dividers. Very interesting design though! If nothing else, this would probably make a good demo bot.

EDIT: I just saw this after posting.

bumpers at max height can clear the dividers by 0.5", like on our real robot. The "wings" just fly over the dividers

[MaGiC_PiKaChU]

Originally Posted by Daniel_LaFleur

G25B may be employed here as the robot is attempting to blockade the goals.

Also, if this strategy was used against me, I'd instruct my driver to pin the offending robot at 30 seconds left in the match and then back off, and when the offending robot chases me, pin it again ... since it can only drive in one direction to extract itself. This will allow 3 automatic scales as the alliance tries to take the batter.

For the blockade, i remember seeing a Q&A about it requiring 2 robots blocking the field. So just one robot is not a blockade.

If you pin this robot at 30 seconds, with the sole strategy of making it give you scale points, then that would be pretty much against G11 anyways

[ratdude747]

If I'm honest, this design sounds like a good way to give the opponents automatic scales and captures.

I wouldn't classify this as cheesecake as it looks more akin to a new robot than a bolt-on mechanism.

[Ari423]

Originally Posted by ratdude747

I wouldn't classify this as cheesecake as it looks more akin to a new robot than a bolt-on mechanism.

I'd call it cheesecake, but really bad cheesecake. Like the kind that has way too much cheese and not enough cake.

[ctt956]

Originally Posted by Ari423

I'd call it cheesecake, but really bad cheesecake. Like the kind that has way too much cheese and not enough cake.

So it should be called cake cheese or just cheese?

[Andrew Schreiber]

Originally Posted by ratdude747

If I'm honest, this design sounds like a good way to give the opponents automatic scales and captures.

I wouldn't classify this as cheesecake as it looks more akin to a new robot than a bolt-on mechanism.

So Zebracorn cheesecake?[1]



[1] If Chicago can have it's own pizza[2] why can't Team 900 have their own cheesecake?

[2] Which I still hold is not real pizza [3]


[3] And I may be fine with people putting whatever they want ON their pizza I am NOT ok with people making their pizza that thick. It's an abomination!

[AmiableVariable]

Concerns about building this aside.
I would be worried giving something like this to an alliance partner who would be driving it for the first time in playoffs. There are not a lot of teams using holonomic drives, and kiwi drives MUCH differently from a standard kitbot, Rhino treads, or most other drive trains. As such, there would be a very high chance of getting stuck in the secret passage and lowbar, or racking up fouls for hitting someone in the outerworks, just in an attempt to get to the secret passage.
It is an interesting concept, but not reasonable to implement in between alliance selection and playoffs.