Ri3D 1.0 Robot Reveal 2016

[Jon Stratis]

Originally Posted by dellagd

I think there are two different possibilities for violation of this type here. The >15" tall upper structure of the robot and the >15" extension that grabs the bar to lift the robot.

If the extension rule stays parallel to the plane of the bumper zone, then when tilted at 90 degrees back the extensions that are grabbing the bar would have to be less than 15 inches. I wasn't there for them, but I thought this type of extension was legal in past seasons.

Remember, past season rules and interpretations do not apply this season!

The most recent time I can think with anything similar was Breakaway (2010). In that game, you were not allowed to extend past your frame perimeter, except in specific situations. For climbing, the rules specifically stated that you were allowed to exteond utwards into a specific volume defined by the finale configuration (90" tall, 82" diameter right cylinder) while touching the tower. There's no such similar rule this year to apply while climbing - it appears that, as it's written now, the 15" limit applies while climbing. Now, how that's interpreted is anyone's guess, and certainly will lead to the Q&A before anyone build something that might be illegal!

[michchinn]

What motors and reductions were you running on the shooter?

[Dan Richardson]

Originally Posted by Purpose

Very nice robot, loved your reveal! I thought the Sally Port mechanism was especially ingenious. I'm curious as to how you guys would go about mounting bumpers onto your bot, do you think you could give some insight into that?

I think it would require creating a sheet metal bracket that spanned the rear and front gaps to create a flat surface for the bumper to mount. You may also need some standoffs to ensure that the bumpers are level to the ground. I believe a many teams will be working through this packaging challenge as the Rhino Tracks are fun to use.

Originally Posted by michchinn

What motors and reductions were you running on the shooter?

We used 2 mini cims to drive 4 x 4" Kit Wheels through Modulox Channel and Lunchbox kits. We used a 1:1.14 gear ratio from a 32 (driving) to 28 (driven) flex hub gears.

This design was inspired by the Modulox basketball launcher from a few years ago: https://www.youtube.com/watch?v=DO0XzkthMUs

[team1512]

First of all, nice job in the robot! It looks great.
We saw that you used flashlights to direct your shots, and I know the rules for this year doesn't say anything about this, but last year's checklist says that you can't direct/focus any lights in any way.
Does anyone know if this would be a problem this year?

[apm4242]

FYI - The GDC just ruled on the 15" extension reorientation while scaling issue -


Extensions outside the FRAME PERIMETER are measured in the same plane as the FRAME PERIMETER. As the FRAME PERIMETER is re-oriented (e.g. when a ROBOT drives up the BATTER), the plane of measurement is similarly re-oriented.

https://frc-qa.firstinspires.org/Que...ng-hook-to-cli

[jdaming]

I believe that with some small modifications this scaling method could still be legal. Making the tower that the arm rotates from taller (so the point it contacts on the wall is up closer to the bar and the arm doesn't need to be as long) or using a long oriented chassis (so that the arm could be longer and the longer frame perimeter would keep more of it inside the robot) would both seem to fix this issue.

[Monochron]

Great job team 1.0, that robot is massively impressive!

Originally Posted by TerryS

Great job again! I'm sure you're all in deep sleep mode right now, but I'd really like to see your tank drive going over the rock wall and rampart, especially as a tall robot.

I would like to echo this sentiment. An important part about Ri3D is educating teams on the benefits and disadvantages of these styles of robot. Your design is definitely impressive and it's really valuable to see all the things that it can do. But it will be equal valuable to see the things that it struggles with, so that we can incorporate that into our own designs.

[dradel]

One of the things that I like about ri3d is how seeing these various groups come up with a mechanism to solve a task, but as a side result we can look for the gray area of the rules and ask questions based off of what was seen done by a ri3d team.

[Mr. B]

Great Job
Will you give some detail on what and how you target the goal?
Thanks

[Dan Richardson]

Originally Posted by apm4242

FYI - The GDC just ruled on the 15" extension reorientation while scaling issue -


Extensions outside the FRAME PERIMETER are measured in the same plane as the FRAME PERIMETER. As the FRAME PERIMETER is re-oriented (e.g. when a ROBOT drives up the BATTER), the plane of measurement is similarly re-oriented.

https://frc-qa.firstinspires.org/Que...ng-hook-to-cli

We saw the clarification this morning.

If I'm interpreting this correctly then our configuration is legal as our arm never extends further than 15" outside the robots frame perimeter. This works because the entire robot revolves around the arm pivot and thus we never violate that configuration.

We designed the arm with the specific length in mind so we could manipulate the defenses during game play as well as hang. I'm happy our design remains within the rules for now, however it is odd to be so restrictive on a more difficult task.

Originally Posted by jdaming

I believe that with some small modifications this scaling method could still be legal. Making the tower that the arm rotates from taller (so the point it contacts on the wall is up closer to the bar and the arm doesn't need to be as long) or using a long oriented chassis (so that the arm could be longer and the longer frame perimeter would keep more of it inside the robot) would both seem to fix this issue.

I think the assumption is that our arm is very long but it is indeed only 15" longer than the frame perimeter. If it were not then we would not be able to use it to manipulate the defenses.

/Edit***** I should say close enough to prove a point. If our bot is an 1" or so out of spec. we don't typically rectify. We only ever seek to be mostly FIRST legal :-)