Introduction to Micromouse WVU IEEE Student Branch 9/24/2014 Stephen Itschner.

Slides:

Advertisements

Similar presentations

Robofest 2005 Introduction to Programming RIS 2.0 RCX Code.

Advertisements

MicroMouse Planning for Spring 2006 Competition Scott F. Smith Boise State University.

Cambodia Robocon March 2015

Project RFP’s Brian Bayliss Mathew Dicke Nathan Ferrel.

Boe-Bot Challenge. Advanced Users (those who have used Boe-Bots in Digital Electronics) There are suggested activities / programs for each challenge.

A 296 MicroMouse project By Brian Kuriyama. Profit!

Place captured red pieces here Place captured yellow pieces here To use as Kings Rules New Game Exit Left mouse click on piece – drag to desired location.

Trinity Robot Competition Introduction. Purpose 1.Build an autonomous computer controlled robot that can find its way through an arena that represents.

July School of Engineering, Mechanical Engineering Division Singapore Robotics Games 04 Symposium Title: An Efficient Maze Solving Algorithm for.

MicroMouse Proposal Presentation Team: Amaze Me. Introduction Members and roles Brandon Gibu Brandon Gibu Updating webpage Ah Ram Kim Ah Ram Kim Contacting.

Maze Craze Challenge 5. Completing a Maze using a Sound Sensor Many times in real life, people get through problems through hearing clear directions.

Ramrod IV Micromouse 396. The Team  Andrew Igarashi – Programming  Kevin Li – Hardware  Amy Maruyama – Hardware  Stephen Nakamura – Hardware  Quang.

The goals of Micromouse: to build an autonomous “mouse” Mouse should be able to navigate and solve any given maze Mouse should be no bigger than 25.

Design Presentation The Prodigy. Introduction Group Members: Dale Balsis Tyson Seto-Mook Calvin Umeda Keoni Wasano.

Ramrod III Micro mouse. The Team  Andrew Igarashi – software  Kevin Li – hardware  Stephen Nakamura – hardware  Quang Ngu – software.

EE 296-Micromouse Spring 2008 Team: CheeHeePono! Members: Mitchell La Puente Travis Suemori Travis Suemori William Chang William Chang Ashley Tomita Ashley.

Ramrod III Micro mouse. The Team  Andrew Igarashi – Hardware  Kevin Li – Programming  Stephen Nakamura – Hardware  Quang Ngu - Programming.

EE 296 TEAM “DA KINE” MICROMOUSE PROJECT PROPOSAL Team members: Software Group - Henry, James Roles : tracking, mapping, guidance, interface Hardware Group.

Ramrod III Micro mouse. The Team  Andrew Igarashi – Hardware  Kevin Li – Programming  Stephen Nakamura – Hardware  Quang Ngu - Programming.

Micromouse Team:. Team Members Kanoa Jou (Leader) Ryan Sato (Organizer) KiWoon Ahn (Organizer) Brett Ikei (Recorder)

EE396 Project Micromouse Team: Ocha. Team Members Kanoa Jou (Programmer) Ryan Sato (Hardware) KiWoon Ahn (Recorder) Alan Do (Programmer)

FINAL PRESENTATION Lost Café 66 EE 296 5/6/2004. Introduction of Team Team Leader: Arthur Phanphengdy Members: Quincy Quach Kang Lu Jackson Ng.

Curry Mouse EE 296 Project Proposal Presentation February 11, 2006.

CheezStix! EE 396 Micromouse Spring 2007 Proposal Presentation.

Micromouse 296 Final Presentation Fall 2008 Group: Rabbitwagon.

Proposal Presentation Micromouse Spring 08 8” Comb.

Preliminary Design Review

KTD Micromouse Overview Team Goals Approach Outstanding Problems Future Solutions Final Status.

The Prodigy Micromouse 296/396. Team Members/Assignments Dale Balsis (396) – Web Designer/Hardware Tyson Seto-Mook (396)– Project Supervisor Calvin Umeda.

Design Review Presentation Lost Caf é 66. Introduction of Team Team Leader: Arthur Phanphengdy Members: Quincy Quach Kang Lu Jackson Ng Team Name: Lost.

TAKE YOUR JACKET OFF! Proposal Presentation  Members:  Jayson Nakakura: Chassis Design and Fabrication  Kellie Murakami: Circuitry Design and Fabrication.

Micromouse Spring 2006 K A L The Pied Pipers. The Pied Pipers: Joanne – Programming Ken – Hardware Alyssa – Hardware Introduction of Team and Roles.

TETRIX/VEX Challenge (use either robot hardware) There will be two events for the May Madness 2010 Challenge –The Grand Challenge - completely autonomous.

Micromouse Team:. Team Members Kanoa Jou Ryan Sato KiWoon Ahn Brett Ikei.

Preliminary Design Review EE 296 – Micromouse Spring 2007.

M & M EE 296 Project Spring 2004 Alex Gomera Sophomore: electrophysics?!?! Favorite EE Teacher: F. Koide I hope to be like that man 

Preliminary Design Review EE 296: Micro Mouse Spring 2007.

Curry Mouse EE296 Final Presentation Wednesday, May 10, 2006.

The goals of Micromouse: to build an autonomous “mouse” Mouse should be able to navigate and solve any given maze Mouse should be no bigger than 25.

VISION CONTROL MICRO MOUSE MSc Computer Systems Engineering By: Rekapally Mahendranath Supervisor: Dr. Nic Snailum.

KTD Micromouse OverviewApproach Potential problems Personal Expectations Team Goals.

Micromouse 296 By Lemmings. Introductions  Vicky- coordinator, software oriented  Bryce-morale booster, software oriented  Ruffer-time keeper, hardware.

Team P.A.C.K men EE 296 Project. Chris Mcleod Hardware specialist.

Spring Project November 14, Course Overview Project will be formalized in “request for proposals” (RFP) Your group of 3-4 will work on.

EE 296 TEAM “DA KINE” MICROMOUSE PROJECT PROPOSAL Team members: Software Group - Henry, James Roles : tracking, mapping, guidance, interface Hardware Group.

Final Presentation EE 296 – Micromouse Spring 2007 Friday, May 4, 2007 POST 214.

Curry Mouse EE296 Design Review Presentation Saturday, March 11, 2006.

M C S E A Rules for Team Competition Answer all parts of a question THEN… Hold up your 1 st attempt so order recorders can see your team number.

QUICK DESIGN GUIDE (--THIS SECTION DOES NOT PRINT--) This PowerPoint 2007 template produces a 36x48 inch professional poster. You can use it to create.

Sumo Introduction F10. theCOMPETITION Crash course in robotics for the inexperienced/curious.

Lynbrook HS Robotics San Jose, CA aMazing Robot iARoC Presentation.

Project Micromouse: Minitaur

Xtreme Robotic Olympiad Peter Laz Associate Professor Department of Engineering University of Denver.

Sumo Introduction Fall theCOMPETITION Crash course in robotics for the inexperienced/curious.

Robo - Cross Students will design and build a robot to collect items on a playing field, move them from one zone of the playing field to another, and.

Raman Veerappan EPS 109 Final Project.  Goals  To examine various maze solving algorithms using MATLAB determine which algorithms are most effective.

Introduction to Robotics Lab 10 – Robot Sorter Felix Duvallet, Matt Faria.

Team Name: Group C.  Zisimos  Team Leader, Software Engineer  Richard  Hardware Engineer  Michael  Hardware Engineer  Jason  Software Engineer.

Preliminary Design Review (PDR) Team Amaze Me. EE 296 Project (MicroMouse) Members –Brandon Gibu –Ah Ram Kim –John-Kalani Miyajima –Justin Ogata Website.

Team: CHEE WHOOO Spring 08. The Team Mitchell La Puente-Project Leader Josh Miyamoto-Software Richard Ordonez-Hardware.

  Yuwon “The Prize” Moon  Seth “Capt. Planet” Wheeler  Mitch “Thriller” Jackson  Michael “Whiteboard Guy” Penney Team Condi Rice.

HBRC A-Mazing Challenge Line Maze, Phase I, II, III.

M. Nelson, 21 Mar NorthWest Louisiana Autonomous Robotics Competition (NWLA-ARC) 2 Challenges – 4 Bottle Race – Board Challenge Awards for Event.

Student Defined Lab Demo Date: April 29, 2009 Robot Exchange.

Blimp Pentathlon a proposal of possible events for an indoor blimp competition The Blimp Pentathlon is an open-source, team guided competition. The competition.

Micromouse 296 Team: Rabbitwagon Fall O8. The Team Richard Ordonez- Project Leader Bob Barfield- Software Manager Lance Lavarias- Mechanical Architect.

HBRC A-Mazing Line Maze Challenge

Scratch – Simple Programming

Tools, Materials and Organisation

FLOORBALL Introduction

Presentation transcript:

Introduction to Micromouse WVU IEEE Student Branch 9/24/2014 Stephen Itschner

What is a Micromouse?  Autonomous robot able to find its way through a maze in the shortest possible time  Maze is a fixed size, but configuration is unknown until the competition  Cannot receive any external input or control (limited to onboard hardware and processing)  Robot no more than 25cm x 25cm

Many Possible Designs

This Mouse Has Solved the Maze

How to Win 1 of the 4 corners is the starting block Get to the center squares in the shortest time

The Only Info Going In:  Maze size is 16 squares by 16 squares  Each square is 18cm X 18cm (16.8 cm between walls)  Walls are 5cm high, red on top, white on sides (IR reflective paint)  Floor is black (IR absorbing paint)  Goal will always be to reach the center 4 squares

Rules  The robot cannot:  Burn through, cut through, fly over, or climb over the walls  Damage the maze in any way  Leave parts of itself behind  Be powered by any flammable substance  The clock starts when the robot leaves the starting square and stops when it enters the goal square, measured from the front edge  Each robot gets 10 minutes to run the maze as many times as desired  The official time is the fastest run completed within the 10 minute period  Every time the mouse is touched after being set down is a 30 second penalty added to the fastest run  Slow robots that solve the maze place higher than fast robots that do not

Cash Prizes (vary by year)  Option 1: built from a commercial OTS kit  $300 1 st  $200 2 nd  $100 3 rd  Option 2: built from scratch  $600 1 st  $500 2 nd  $300 3 rd

An Expert Micromouse, Fast Run Only:  =rja&uact=8&ved=0CCUQtwIwAQ&url=http%3A%2F%2Fwww.youtube.com%2Fw atch%3Fv%3DCLwICJKV4dw&ei=WRwjVMjhH4u3yATlhYKAAQ&usg=AFQjCNG2lzY Ru1DWSXm-Bf7lTsi5c8iGvQ&bvm=bv ,d.aWw =rja&uact=8&ved=0CCUQtwIwAQ&url=http%3A%2F%2Fwww.youtube.com%2Fw atch%3Fv%3DCLwICJKV4dw&ei=WRwjVMjhH4u3yATlhYKAAQ&usg=AFQjCNG2lzY Ru1DWSXm-Bf7lTsi5c8iGvQ&bvm=bv ,d.aWw

Path Forward for WVU IEEE Scratch Team  Currently own a micromouse made from scratch  Pet project of the presenter since ~Sept  Needs to be debugged and programmed  Optimizations to hardware permissible  Full hardware and design brief available for those interested Kit Team  Order known working hardware  Program the maze exploration and solving  Pros:  Known, working hardware  Online support  Potential for finding source code online  Cons:  Lower prize  Other teams have same advantages