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

Slides:



Advertisements
Similar presentations
Mobile Robot ApplicationsMobile Robot Applications Textbook: –T. Bräunl Embedded Robotics, Springer 2003 Recommended Reading: 1. J. Jones, A. Flynn: Mobile.
Advertisements

Sensor Based Planners Bug algorithms.
A 296 MicroMouse project By Brian Kuriyama. Profit!
MicroMouse Proposal Presentation Team: Amaze Me. Introduction Members and roles Brandon Gibu Brandon Gibu Updating webpage Ah Ram Kim Ah Ram Kim Contacting.
Proposal Presentation EE 396 – Micromouse Spring 2008 Saturday, February 9, 2008 Donald Kim Lab - POST 214.
Ramrod IV Micromouse 396. The Team  Andrew Igarashi – Programming  Kevin Li – Hardware  Amy Maruyama – Hardware  Stephen Nakamura – Hardware  Quang.
A fully autonomous robot designed to navigate and solve a maze.
The Pied Pipers Alyssa Visitacion Ken Shum Joanne Flores.
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 – 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)
Curry Mouse EE 296 Project Proposal Presentation February 11, 2006.
‘Iole o Mãnoa Mouse of Mãnoa. Team Members Jeff Fines Designer, Fabricator, Programmer & Thomas Matsushima Designer, Fabricator, Programmer.
Micromouse 296 Final Presentation Fall 2008 Group: Rabbitwagon.
Preliminary Design Review
1 Final Presentation Team Amaze Me May 8, Content Members Overview of Project Goals Structure of Design Design Decisions Problems & Improvements.
KTD Micromouse Overview Team Goals Approach Outstanding Problems Future Solutions Final Status.
take your JACKET OFF KELLIESCOTT KENDALLJAYSON Final Presentation  Members:  Jayson Nakakura: Chassis Design and Fabrication  Kellie Murakami: Circuitry.
The Pied Pipers Joanne Flores Ken Shum Alyssa Visitacion.
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.
M & M EE 296 Final Presentation Spring 2004 Presentation Overview Team Member Introduction Project Overview Overall Design Description Final Project.
Micromouse 296 By Lemmings. Introductions  Vicky- coordinator, software/hardware  Bryce-morale booster, software/hardware  Ruffer-time keeper, software/hardware.
Micromouse Spring 2006 K A L The Pied Pipers. The Pied Pipers: Joanne – Programming Ken – Hardware Alyssa – Hardware Introduction of Team and Roles.
Fast D.A.D.I. Team Members Dale Balsis Aaron Tsutsumi Dennis How Ikaika Ramos.
("/(o_O)\") RaWr! Proposal Presentation February
Ramrod IV Micromouse 396. The Team  Andrew Igarashi – Programming  Kevin Li – Hardware  Amy Maruyama – Hardware  Stephen Nakamura – Hardware  Quang.
Ramrod IV Micromouse 396. The Team  Andrew Igarashi – Programming  Kevin Li – Hardware  Amy Maruyama – Hardware  Stephen Nakamura – Hardware  Quang.
Central Power Mouse Group Members: Stacey Mitani Jeremy Perron (team leader) Erica Salvador Reid Ueda.
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 
Team Asphalt Kellen King Ikaika Ramos Brad Centeno.
Preliminary Design Review EE 296: Micro Mouse Spring 2007.
Team P.A.C.K men EE 296 Project. Chris Mcleod Hardware Specialist.
MicroMouse Final Presentation Jill Kobashigawa Min Mo Jon Shindo Christy Kaneshiro.
EE 296 Team Da Kine James Cuaresma – Software Wesley Mina - Hardware Regi Morales - Hardware Henry Do - Software.
Robot Maze Solving EGR106 Project Overview Spring 2004.
Ramrod IV. The Team  Andrew Igarashi – Programming  Kevin Li – Hardware  Amy Maruyama – Hardware  Stephen Nakamura – Hardware  Quang Ngu – Programming.
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.
Curry Mouse EE296 Final Presentation Wednesday, May 10, 2006.
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.
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.
Mobile Robot ApplicationsMobile Robot Applications Textbook: –T. Bräunl Embedded Robotics, Springer 2003 Recommended Reading: 1. J. Jones, A. Flynn: Mobile.
Curry Mouse EE296 Design Review Presentation Saturday, March 11, 2006.
Loops and Switches. 1. What kind of blocks are these? 2. Name two kinds of controls that can be specified to determine how long a loop repeats. 3. Give.
Lynbrook HS Robotics San Jose, CA aMazing Robot iARoC Presentation.
Team 4 Shane Sunada – Project Leader Malcolm Menor – Project Manager Nathan Umeda – Technical Supervisor Joseph Longhi – Documentation Final Presentation.
‘Iole o Mãnoa Mouse of Mãnoa. Team Members Jeff Fines Designer, Fabricator, Programmer & Thomas Matsushima Designer, Fabricator, Programmer.
Final Presentation Micromouse Spring 08 8” Comb.
Preliminary Design Review (PDR) Team Amaze Me. EE 296 Project (MicroMouse) Members –Brandon Gibu –Ah Ram Kim –John-Kalani Miyajima –Justin Ogata Website.
  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.
The George Washington University Department of ECE ECE Intro: Electrical & Computer Engineering Dr. S. Ahmadi Class 4/Lab3.
MICROMOUSE EE296 Spring 2004 Team Name: Lost Café 66.
ROBOTC for VEX Online Professional Development. Homework Questions Thoughts? Questions?
PostBase Automatic Feeder Component Removal Service Training
Understanding Communication with a Robot? Activity (60 minutes)
Touch Sensor.
Loops and Switches Pre-Quiz
1. Write three fractions that are less than one.
Loops and Switches How Do You Make Loops and Switches? lesson > TeachEngineering.org Center for Computational Neurobiology, University of Missouri.
Presentation transcript:

Ramrod III Micro mouse

The Team  Andrew Igarashi – software  Kevin Li – hardware  Stephen Nakamura – hardware  Quang Ngu – software

Project Overview  To design a fully autonomous robot that can move through the maze  Top down sensors locate walls around the mouse  Programmed in Dynamic C to locate the center

Our Approach  Bottom up approach  Build chassis and frame  Install motor and sensors  Test proper operation using Dynamic C

Block Diagram ControlSolvingBatteriesMotorsSensors

Start

 Overwrite starting cells with value 10 until first multiple choice turn  Overwrite cells with value 10 after hitting a dead end

Delays  Used to prevent phantom walls  Used dummy variables hold delay values  Ex.  If tracking sensors are on for more than X miliseconds, then adjust  If there 1 pad detectors nothing for more than X seconds, then it is ok to turn

 One Choice  Force Case  Two Choices  Straight or Left  Straight or Right  Right or Left  Three Choices  Right, Left, or Straight

This algorithm tells the mouse which cell is closer to the middle and gives preference to that cell. If it is not possible to move to a lower value, then move to a cell with equal value, if even that is not possible as shown above, then move to a cell with a greater value. Front of the Mouse

This is a special case when the Algorithm is in confusion. Since both cells are of equal value. To get around this, we have the mouse remember what type of turn previous to the 180 turn was executed. If this certain turn was a right turn (like in the last slide), when the mouse reaches the wall, we will give preference to a right turn. Vice Versa for left turns. If the mouse did not make any 180 turns, then it will act on a set initial turn. Front of the Mouse The mouse will reverse only to adjust itself so it won’t hit the wall. The cell behind the mouse is not an option.

Problems While Testing  Wall detection and sensor problems  Heat  Wires coming loose  Not enough voltage  Cell counting / Solving

[16][1][17][1][15][1][14][1][13][1][12][1] Out of Bounds [16][1] [15][2] [16][1] – [1][0] = [15][1]

Outstanding Problems  Inconsistent results  Wall detection  Alignment  Algorithm / Mapping

Updated Schedule