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

Slides:



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

Proposal Presentation EE 396 – Micromouse Spring 2008 Saturday, February 9, 2008 Donald Kim Lab - POST 214.
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.
Design Presentation Fast D.A.D.I.. Team Members D - ale Balsis A - aron Tsutsumi D - ennis How I - kaika Ramos.
MICROMOUSE 2006 Version: Meat & Potatoes. Alex Zamora Tyson Seto-Mook Mike Manzano Alex de Angelis Aaron Fujimoto The Team:
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.
Preliminary Design Review Micromouse EE 296 Spring 2008.
EE 296 TEAM “DA KINE” MICROMOUSE PROJECT PROPOSAL Team members: Software Group - Henry, James Roles : tracking, mapping, guidance, interface Hardware Group.
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)
Team 4 Shane Sunada – Project Leader Malcolm Menor – Project Manager Nathan Umeda – Technical Supervisor Joseph Longhi – Documentation Preliminary Design.
FINAL PRESENTATION Lost Café 66 EE 296 5/6/2004. Introduction of Team Team Leader: Arthur Phanphengdy Members: Quincy Quach Kang Lu Jackson Ng.
Shane Sunada Malcolm Menor Joseph Longhi. - Autonomous maze solving robot -16x16 maze starting at corner - No contact after switched on - No going under.
‘Iole o Mãnoa Mouse of Mãnoa. Team Members Jeff Fines Designer, Fabricator, Programmer & Thomas Matsushima Designer, Fabricator, 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.
CheezStix! EE 396 Micromouse Spring 2007 Proposal Presentation.
Micromouse 296 Final Presentation Fall 2008 Group: Rabbitwagon.
Proposal Presentation Micromouse Spring 08 8” Comb.
Amaze Me Final Presentation May 4, Introduction of Team Amaze Me Team Members –John Miyajima –Brandon Gibu –Justin Ogata –Ah Ram Kim.
Preliminary Design Review
Group Members Ikechukwu Mogbana Adewuyi Kupolati Frederick Tyson Advisor Prof. Mahmood November 10, 2005 Senior Project 2005/06 Undergraduate Project Proposal.
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.
Meat and Potatoes Micromouse Team Introduction ► Aaron Fujimoto ► Alex DeAngelis ► Alex Zamora ► Mike Manzano ► Tyson Seto-Mook.
Scott Lee Dwayne Yuen Justin Lo Ashley Tomita. Constructing an electronic mouse by using knowledge about circuits and programming. The mouse should move.
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.
1 Team Amaze Me (Micromouse 296/396) Brandon Gibu Chad Higa John Miyajima Justin Ogata (February 9, 2008) Fig. 1.1: Amaze Me 1.0Fig. 1.3: *Herbie the Mousebot*
("/(o_O)\") RaWr! Final Presentation May 9, 2006.
Micromouse Spring 2006 K A L The Pied Pipers. The Pied Pipers: Joanne – Programming Ken – Hardware Alyssa – Hardware Introduction of Team and Roles.
Ramrod IV Micromouse 396. The Team  Andrew Igarashi – Programming  Kevin Li – Hardware  Amy Maruyama – Hardware  Stephen Nakamura – Hardware  Quang.
Micromouse Team:. Team Members Kanoa Jou Ryan Sato KiWoon Ahn Brett Ikei.
Final Presentation EE 396 – Micromouse Spring 2008 Friday, May 9, 2008 Donald Kim Lab - POST 214.
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.
CheezStix! EE 396 Micromouse Spring 2007 Preliminary Design Review.
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.
Preliminary Design Review Micromouse Spring 08 8” Comb.
Preliminary Design Review Micromouse Team: Ocha. Team Members Kanoa Jou Ryan Sato KiWoon Ahn Brett Ikei.
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.
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.
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.
Super Space Monkey from Space Trent Robertson Krystle Dulatre Ben Ng Lori Nakamoto.
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.
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.
Team: CHEE WHOOO Spring 08. The Team Mitchell La Puente-Project Leader Josh Miyamoto-Software Richard Ordonez-Hardware.
EE 296-Micromouse Spring 2008 Team: CheeHeePono! Members: Mitchell La Puente Travis Suemori Travis Suemori William Chang William Chang.
MICROMOUSE EE296 Spring 2004 Team Name: Lost Café 66.
Micromouse 296 Team: Rabbitwagon Fall O8. The Team Richard Ordonez- Project Leader Bob Barfield- Software Manager Lance Lavarias- Mechanical Architect.
Proposal Presentation
Presentation transcript:

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

Mission Impossible-MicroSP08  To create a Micro- mouse (autonomous robot) that can navigate itself through a maze.  The mouse should be able to determine the quickest path to the center.

Design  FLOPPY-BASE  Top-Down sensors  Stepper motors  Right wall hugger  FAILING random  Messy wires

Design  Initially: Move long distances in the mazeMove long distances in the maze track within the mazetrack within the maze map the maze.map the maze. Just make it “work”Just make it “work”

Design  Final Design In our final design we omitted the mapping.In our final design we omitted the mapping. Rebuilt for easier assemblyRebuilt for easier assembly  Rebuilding helped debugging  Made it easier to ship to competition

Design  Tower-like design Bottom level holds the motorsBottom level holds the motors Second level has the sensorsSecond level has the sensors Third level has the batteries and rabbitThird level has the batteries and rabbit Top level has the motor circuitTop level has the motor circuit  Used RC batteries  Sensors Right, left, and inside tracking sensors are connected in “OR” logic.Right, left, and inside tracking sensors are connected in “OR” logic.

Problems  Motor circuit We got it working, then it broke down several times and took several hours to figure out what was wrong with itWe got it working, then it broke down several times and took several hours to figure out what was wrong with it  Had to change diodes  Had to change MOSFET’s  Had to rebuild the circuit on a new board  Changed one of our motors

Problems  Sensors Initially we had 5 sensorsInitially we had 5 sensors It had trouble turning and tracking so we kept adding moreIt had trouble turning and tracking so we kept adding more Finished with 17 physical sensorsFinished with 17 physical sensors The sensor board was too low so we had to raise itThe sensor board was too low so we had to raise it Initial circuit was incorrect, so we had to add resistorsInitial circuit was incorrect, so we had to add resistors

Problems  Programming Had difficulty organizing code to determine when to turn/track.Had difficulty organizing code to determine when to turn/track.  As a result it would track when it should’ve turned or turned when it should’ve tracked Code was unorganized so we had to rewrite itCode was unorganized so we had to rewrite it  Consisted of magic numbers and unnecessary modules Hard time programming with serial cablesHard time programming with serial cables

Outstanding Problems  Mouse doesn’t map  Tracking is not perfect  Body bounces when it moves  Can only find the center as a right wall hugger  Sometimes crashes when code does not get to sensor reading fast enough

FLOPPY-BASE Transformation

FINAL FLOPPY-BASE