Team 4 Shane Sunada – Project Leader Malcolm Menor – Project Manager Nathan Umeda – Technical Supervisor Joseph Longhi – Documentation Final Presentation.

Slides:



Advertisements
Similar presentations
A 296 MicroMouse project By Brian Kuriyama. Profit!
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.
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.
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)
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.
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
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.
Team P.A.C.K men EE 296 Project. Introduction to team P.A.C.K men Paul Linden – Systems specialist. Aaron Lake – Power specialist. Chris McLeod – Hardware.
The Prodigy Micromouse 296/396. Team Members/Assignments Dale Balsis (396) – Web Designer/Hardware Tyson Seto-Mook (396)– Project Supervisor Calvin Umeda.
EE 296-Micromouse Spring 2008 Team: CheeHeePono! Members: Mitchell La Puente Travis Suemori Travis Suemori William Chang William Chang Ashley Tomita Ashley.
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*
Final Presentation for x96 Projects 9:00 AM – 11:30 AM Thursday, 3 May 2007 Donald Kim Lab, POST 214 Team Raiton Denki No Jutsu Project Micromouse.
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.
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.
Final Presentation EE 396 – Micromouse Spring 2008 Friday, May 9, 2008 Donald Kim Lab - POST 214.
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.
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.
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.
Curry Mouse EE296 Design Review Presentation Saturday, March 11, 2006.
DC Motor Control  mouse EE 496 Advisor: Dr. Tep Dobry.
Administrative Introduction Our goals for this project is for the two robots to work together intelligently using wireless communication Not only did.
Team Spot On! With Zebulon Clark Desiree And Earl.
Administrative Introduction Our goals for this project are for the three robots to work together intelligently to complete a maze faster than an individual.
‘Iole o Mãnoa Mouse of Mãnoa. Team Members Jeff Fines Designer, Fabricator, Programmer & Thomas Matsushima Designer, Fabricator, Programmer.
Back To Basics A BASIC Stamp Based Micromouse B2B MicroMouse Traditional MicroMouse  Language used › PBASIC  Drive systems › Servo Motors  Sensor.
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.
The George Washington University Department of ECE ECE Intro: Electrical & Computer Engineering Dr. S. Ahmadi Class 4/Lab3.
The George Washington University Electrical & Computer Engineering Department ECE 002 Dr. S. Ahmadi Class3/Lab 2.
Casne.ncl.ac.uk Taking care of the CrumbleBot Please do NOT stress the robot's motors 1.Do NOT push the robot 2.Do NOT hold the.
Micromouse 296 Team: Rabbitwagon Fall O8. The Team Richard Ordonez- Project Leader Bob Barfield- Software Manager Lance Lavarias- Mechanical Architect.
Proposal Presentation
Presentation transcript:

Team 4 Shane Sunada – Project Leader Malcolm Menor – Project Manager Nathan Umeda – Technical Supervisor Joseph Longhi – Documentation Final Presentation May 9, 2008

To design and construct a robotic “mouse” that can successfully navigate to a central point of a randomized maze and return to the starting point with minimal collisions. Overview

Hardware

Initial Goals - Robot base must be able to rotate 180 degrees in a 16cm x 16cm square - Robot base should be robust - Robot base should be light (no excessive material) - Robot should be easily disassembled - Robot should LOOK GOOD!

Alteration -Chassis and Sensor Layout -Rear Sensors -Tire size - Chassis lightening - Circuit element decisions

Problems -Thought our motors were bad when circuit was on Breadboard -Shorted RCM2000 -Batteries/Power Drain -PCB -Heat Generated -Finding Right Value of Resistors for Sensors

Software

Initial Goals -Get it moving Straight -Tracking -Get it to turn Wall Hugger -Right -Left -Switching -Random -Flood Fill -Track (x,y) position in maze -Flood Filling Functions

Straight/Tracking -Stop one wheel -Deciding which sensors to use -Use Costates -Reverse Code -Acceleration

Turning -Move both wheels in opposite directions so turn in place -UTurn is just 2 turns

Wall Hugger -Slow down when no wall -Turn after no wall then wall -Started with just right wall hugging -Mod to left wall -Switching -Random Pulses

Flood Fill -Tried position with step count -Wrote other functions -Not able to get all function to sync

Problems

Straight/Tracking -If tried a smooth correction it didn’t correct fast enough -Sensors to far apart -Trying to Find the Right speed to move the mouse -Sometimes tracked when we didn’t want to -(Tracked into Wall) -Changed Sensors Used

Turning -Getting the values for turning -Sometimes one wheels locked

Wall Hugging -Getting Code to compile -Deciding When the mouse should turn -Instead of using step counts sense when wall disappears and then reappears -Turned when it shouldn’t or the wrong directions -Change what sensors were used to detect turn

Continued Switching/Random How to make it switch Implementing a Random Function Added LED Crashed into wall Reset Feature

Flood Fill -How to write a flood fill code and what it is -How to avoid flood overflow -Just don’t check outer walls -Keeping track of position in the maze

Recap Final Standing -Have Chassis using Stepper Motors and a PCB Motorboard -8 Sensors and 2 LED on a Adjustable Sensor Board V Rechargeable Batteries -Left, Right, Switching, Random Wall Hugger, Drag Race switchable with 8 Dip Switches

Outstanding Problems What we would change

Power Drain/ Heat -More Voltage Regulators -Stepper Motors gave problems -Rechargeable Batteries -Add one more Switch

-Sensor Layout -Closer Sensors -More Sensors -PCB Sensor Boards -Weight Reduction -Position -Trying to keep track of position in maze

-Moving -S-Turns -Better Tracking -Solving Algorithms -Getting Flood Fill to work -Find a better algorithm