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

Slides:



Advertisements
Similar presentations
A 296 MicroMouse project By Brian Kuriyama. Profit!
Advertisements

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.
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.
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)
Micromouse Projects LTD. Presents a STIG, Whitey, Zephyr Production.
("/(o_O)\") RaWr! Design Review Presentation March 11, 2006.
FINAL PRESENTATION Lost Café 66 EE 296 5/6/2004. Introduction of Team Team Leader: Arthur Phanphengdy Members: Quincy Quach Kang Lu Jackson Ng.
‘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.
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
TEAM MECHAZAWA Jeong Bang Riley Ceria Grant Higa.
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.
Meat and Potatoes Micromouse Team Introduction ► Aaron Fujimoto ► Alex DeAngelis ► Alex Zamora ► Mike Manzano ► Tyson Seto-Mook.
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.
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.
("/(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.
Raiton Denki No Jutsu Brandon Inouye Jennifer Liem Chester Lim Roxanne Yee.
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.
CheezStix! EE 396 Micromouse Spring 2007 Preliminary Design Review.
The EE296 MicroMouse. Team Members Eric Fune (Director of Programming)‏ David Hashisaka (Senior Circuitry Technician and Chief Fabrication Officer)‏ Jarret.
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.
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.
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.
Fast D.A.D.I.. Team Members D - ale Balsis - Machinist D - ale Balsis - Machinist A - aron Tsutsumi - Electrician A - aron Tsutsumi - Electrician D -
Curry Mouse EE296 Design Review Presentation Saturday, March 11, 2006.
Micro-Mouse Rotech means robust mice technology..
‘Iole o Mãnoa Mouse of Mãnoa. Team Members Jeff Fines Designer, Fabricator, Programmer & Thomas Matsushima Designer, Fabricator, Programmer.
Team Name: Group C.  Zisimos  Team Leader, Software Engineer  Richard  Hardware Engineer  Michael  Hardware Engineer  Jason  Software Engineer.
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 TEAM “DA KINE” MICROMOUSE PROJECT PROPOSAL Team members: Software Group - Henry, James Roles : tracking, mapping, guidance, interface Hardware Group – Regi, Wes Roles : sensors, soldering, device placement, chassis construction, motors, power supply

Overview To create a moving object which can traverse through the maze and find the center of the maze without any human intervention.

General Approach First step - work in separate groups (software/hardware) Second step – integrate software and hardware when both are working properly Third step – test, solve problems which arise ( ex. turns, alignment, crashing, etc.) Final step – make final adjustments on the mouse, then let it rip!

Potential Problems Steering (turning at desired angles) Centering mouse between walls Time conflicts when having group meetings Code errors Durability of mouse from crashes (damage control)

Fruits from labor! Learn how to integrate software and hardware to solve a real world problem Learn how to apply engineering principles and theory to create a smart robot Learn how to troubleshoot Learn how to work as a team to reach a design goal

Expectations Mouse will find the center of the maze in record time! Win the micromouse competition! Be the next micromouse champion!