12736

Electric Mayhem Green

Buffalo, NY, USA

Rookie Year

2017

Members

10

Mentors

2

Type

School

Team Statistics

Meeting Hours/Week

6

Approx. Budget

$5000+

Workspace

Dedicated Robotics Lab

Sponsorship Status

1-3 Sponsors

Robot Statistics

Drivetrain

Kiwi

Materials

Prefabricated Metal, Custom Metal, Polycarbonate, 3D-Printed Plastic

Providers

GoBilda, REV DUO, VEX Pro, AndyMark, Sparkfun Electronics, Axon, Swyft Robotics, Other

Odometry

Optical [Laser] Odometry

Sensors

Magnetic Limit Switch, Colour, Rotary Encoder

Systems

Claw/Gripper Effector, Rotary Wheel Effector, Linear Slides, Climber

Code Statistics

Programming Language

Java

Development Environment

Android Studio

3rd-Party Tools

FTC Dashboard

Vision

AprilTag Localization [Onboard], AprilTag Localization [Limelight 3A]

Free-Response

What is something that you think is unique about your robot this season? What about your robot do you think would make it stand out at competition?

I believe the most unique part of our robot is it's drivetrain. Instead of the standard FTC mecanum drivetrain, we are using a custom Kiwi drivetrain for it's balance of speed and versatility.

What types of Outreach do you plan to do for this season? Which of those Outreach initiatives are you most proud of?

Describe an element of your code which you think will be most advantageous to your performance over the season.

This year we are using the new limelight 3A for apriltag localization.

What competitions will you be attending? Which of the ones that you listed are you looking forward to the most?

Finger Lakes Qualifier MVCC Utica Qualifier Corning Qualifier This year we are most excited for the Corning Event as we intend on going a day early to explore the town and the glass museum.

How will you be organizing your team at competitions?

Driveteam: -Driver -Operator -Coach - Human Player Pit Crew & Pit Host Media Scouting Team

Describe a unique or noteworthy strategic device or element that you think would be useful for this game.

A strategy that we designed into our robot, was the ability to most advantageously outtake samples of the wrong color. We added a color sensor to our intake, so we can choose what color sample we want to intake, if we pick the wrong color the sample will be outaked out the back of the intake and thus out of the way for when we reattempt to intake.

How would you describe your design process? How many options/strategies do you compare? How do you visualize your designs before building?

This year we tried a new design process of not manufacturing/building anything final until the ENTIRE CAD of the robot was done. So far this philosophy has worked and we've run into not nearly as many integration issue during the final build.

How do you divide your team's time between things like design, building, programming etc. Do you enforce this timing? If so, why?

This year we spit our time with a priority on design and programming. The idea being if we get the design perfect in CAD, the build will come together quickly. We enforced this timing very strictly with a no building policy until after the CAD deadline of November 1st. Though the urge to begin building was strong, waiting until after the completion of the CAD has greatly paid off, so far.

Made with by Electric Mayhem Robotics and external contributors
Check out our code on GitHub