2016 Robotics Competition
|2016 Robotics Competition
November 2-5, 2016
Double Tree by Hilton
Friday, September 23, 2016: Confirm Intent to Compete / Pay $30 Team Entry Fee
Monday, October 3, 2016: Rubrics Available to all groups: Design & Construction, Controller Methodology, Fabrication/Innovation, Poster, Technical Report Judging, and Competition
Friday, October 7, 2016: Submit Technical Report – email to alyssa@ATMAE.org
Special Note: Based on your request, the Robotics Competition will be on Wednesday, November 2nd. All poster and presentation sections will be held during the day and the Actual competition will be held that evening at the ATMAE Opening Reception.
- Teams are required to register online for the competition before September 23, 2016.
- $30 entry fee for ATMAE student chapters
- $60 entry fee for non-ATMAE student chapters
- All major credit cards are accepted online or send a check by selecting the "Bill Me" option during registration. All checks must be received by ATMAE no later than Friday, October 7th. Make checks payable to “ATMAE” and send to ATMAE 275 N. York Street, Suite 401, Elmhurst, IL 60126.
- For questions, email Alyssa at alyssa@ATMAE.org.
- The contest is open to all attending the 2016 Annual ATMAE Conference. All team members must register for the conference.
- Each team will be responsible for the cost of building and transporting the manipulator.
- Teams may not use robotic kits or off-the-shelf robot manipulators, but may use hobbyist level components available at typical hobby shops.
- In the 2016 contest, only one person may operate the robot at a time unless otherwise stated in the competition rules. The operator must be an undergraduate student who is on the competing ATMAE Chapter’s Robotics Team.
- The robots and robotic manipulators should be built by the students. Work can be done away from campus, but the work should be done by the students. Materials can be received from a donation, but work on the robot and/or manipulator should not be outsourced or donated by an outside business or organization.
- Each team can submit only one robot for the competition. The robot will need to be equipped to compete in both the Robotic Obstacle Course and the Robotic Relay Race. Different manipulators can be used for the two competitions, but they must be able to be changed within 5 minutes.
- The power source for each robot can be changed/charged between events. Changing the power source should be a process that takes 5 minutes or less.
- The Robotic Obstacle Course portion of the contest will be first, followed by the Robotic Relay Race.
- The Robotic Obstacle Course will have both manual and autonomous portions while the Robotic Relay Race will be completely manually controlled.
- Both events will take place in a hotel conference room, so the base surface will be carpet.
- Teams will NOT be allowed to practice before the actual events. All teams will have access to the competition area prior to the events for measurements, planning, etc., but no practicing.
- View all submitted questions and answers on our FAQ Page. If you have a question, please email firstname.lastname@example.org.
- Entries must be wireless remote controlled robots. No wires attaching control to the manipulator are allowed.
- Robots may be any weight and height, but the footprint will be limited to 12” x 18” (304.8mm x 457.2mm). Footprint is define as the portion of the robot that touches the ground with the robot in its starting position. The manipulator is allowed to touch the ground when lowered or extend to pick up and object.
- The robots may be pneumatically driven, electrically driven by solar, battery or hydrogen cell, or powered by a small muffled gasoline powered engine not to exceed 90 dB from 10’ (3.05 M) distance. No rockets will be allowed. ATMAE and the hotel will provide fire extinguishers if any combustible fuels are used.
- The robots will be controlled by radio controls as per past ATMAE competitions.
- There are standard communication frequencies available for radio controlled cars and aircraft. Since there will be times when more than one robot will be competing, it is recommended that each robot be controlled with a 2.4GHz DSM controller.
Manipulator cannot fly, or launch, or destroy any object.
RC hobbyist level components may be utilized in the development of the robot including the use of chassis, suspension, motors, controls, and transmitters.
The Robotic Obstacle Course will have a 10 minute time limit. If a robot is not able to complete the course in the allotted 10 minutes, the judges will score the robot based on the amount of the course the robot has completed.
Teams will be allowed to change the batteries in their robot between events and/or rounds of the relay race. Extended amounts of time for charging of batteries will not be allowed due to time constraints. Extra sets of batteries are recommended. Teams should design their robot so that the changing of batteries can be done in 5 minutes or less.
If a robot is damaged during either of the competitions, the team will be allowed to repair the robot, but if the damage is considerable and will take more than 15 minutes to repair, the team may be asked to withdraw. If the damage to the robot has been caused by another robot traveling out of its lane during the relay race and the damage causes a withdrawal of the team with damaged robot, the team that caused the damage will also be forced to withdraw from the relay race competition and will receive 0 points for the relay race portion of the competition.
- The competition will be held in a standard, carpeted hotel room.
- Lighting in the room will be standard hotel conference room lights.
- The competition areas will be marked off using 2” wide silver duct tape. The operators will not be allowed to enter the competition area but will be allowed to follow their robot as long as they remain outside of the marked area.
- The overall size of the room is 142' wide by 72’ deep with 19 foot ceilings.
- The competition area for the Obstacle Course will be 16’ x 12’.
- The competition area for the Relay Race will be 34’ x 4.5'.
- The tape that is to be followed during the autonomous section of the Obstacle Course will be 3M Foil Tape as pictured below.
- All teams are required to prepare a flat poster.
- Each poster entry should be 30” Wide x 40” Tall. If your team’s poster does not meet the size and orientation specifications your team will receive no points for this section of the competition.
- Each poster could possibly display the following information:
- Name of the robot
- Construction: materials, processes, etc.
- Calculations: speed, lifting capability, etc.
- Drawings: 2D or 3D drawings or robot and/or parts
- Schematics: electrical, pneumatic, etc.
- Be creative, but more importantly, be informative
- The poster cannot have a LCD or LED display
Technical Report and Group Presentation
- Each team will be required to submit a technical report (Word doc or PDF only). This report should include but not be limited to the following:
- Print of all drawings pertaining to the robot.
- Print of all related schematics.
- A list and explanation of all calculations used in the design of the robot.
- List of components and materials used.
- An electronic copy of the technical report must be submitted by October 7th, 2016 to allow time to evaluate the report.
- Each team will be required to make a presentation in front of the judges explaining the robot design, build, and components. This presentation should be between 5 and 10 minutes in length. Following the presentation, the judges will then ask questions pertaining to the area of the robot for which they are judging. It is recommended that your presentation include visual aids, such as PowerPoint or other software, to assist in the description of the robot and how it functions.
- Email Technical Report to alyssa@ATMAE.org.
Overall Scoring Distribution Summary
|Robotic Obstacle Course
|Robotic Relay Race
|Electronic / Control Methodology
|Fabrication / Innovation
|Technical Report and Presentation
Highest overall score wins
Judgments on Tiebreakers, Disqualifications or any other Scenario not Specifically Described in these Specifications