The Pied Pipers Joanne Flores Ken Shum Alyssa Visitacion.

Slides:



Advertisements
Similar presentations
Proposal Presentation EE 396 – Micromouse Spring 2008 Saturday, February 9, 2008 Donald Kim Lab - POST 214.
Advertisements

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.
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.
Thomas Kagawa, Kenyan Kawauchi, Christopher Lanuevo, Ronald Mangoaong, Joan Suniga.
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.
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.
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.
Design Review Presentation Lost Caf é 66. Introduction of Team Team Leader: Arthur Phanphengdy Members: Quincy Quach Kang Lu Jackson Ng Team Name: Lost.
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.
("/(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.
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.
Meat and Potatoes Micromouse Spring Introduction (Top-Down, Left-Right) –Alex DeAngelis –Mike Manzano –Aaron Fujimoto –Alex Zamora –Tyson Seto-Mook.
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.
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.
Ramrod IV. The Team  Andrew Igarashi – Programming  Kevin Li – Hardware  Amy Maruyama – Hardware  Stephen Nakamura – Hardware  Quang Ngu – Programming.
Thomas Kagawa, Kenyan Kawauchi, Christopher Lanuevo, Ronald Mangaoang, Joan Suniga.
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.
Curry Mouse EE296 Design Review Presentation Saturday, March 11, 2006.
Old control system ( ) MVRT. Main Circuit Breaker Connected to the red wire (power) of the battery When turned off, all power is cut off and robot.
EDGE AVOIDER ROBOT USING I-BOT mini V3. EDGE AVOIDER USING I-BOT mini V3 Edge Avoider Robot is built using the IR based Line Detecting Module. The modules.
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.
Electricity Notes 6 - Circuits Electric Circuit – _______________________________________ All electrical circuits have 4 parts: 1.____________________________________________________.
Mechanical Components and Programming Ken Youssefi Introduction to Engineering – E10 1.
ECE 445 Group 20 4/23/2012 Kevin Dluzen Jonathan Hall Diyang Qiu.
IMDL Summer 2007: RoBeDeS by David Ladolcetta.
Model Blimp Design Competition Soldering Workshop by Youth College (International) / VTC 09:30 – 11:00 11:00 – 12: May
Presentation transcript:

The Pied Pipers Joanne Flores Ken Shum Alyssa Visitacion

Project Overview To create an autonomous robotic mouse that will navigate a maze.

Goals Have each circuit correctly interact with each other. Make mouse move forward Have mouse make turns Complete a wallhugging mouse Find center of maze

System Diagram Program Module Mechanical Module

Program Module Tracking Algorithm Sense walls If offset sensors turn on, you are no longer centered. Increase speed on side of offset sensors until centered. Wall Hugger Algorithm Move forward as long as there is a wall on the left.  If there is a wall in the front, turn right.  If there is no wall on the left, turn left.

Excerpt from Tracking and Wallhugger Code int delaysignal(void); unsigned moveforward(void); unsigned turnright(void); unsigned turnleft(void); main() { RdPortI WrPortI(SPCR,&SPCRShadow,0X84);// declares all A ports as output ports while (1) // basic wallhugger {if (SENF1 || SENF2) {turnright();// this function moves mouse right delaysignal(); } else if (!SENL1 && !SENL2 && !SENL3) {turnleft();// this function moves mouse left delaysignal; } else {moveforward;// this function moves the thing forward delaysignal; }

Mechanical Module Chassis Battery Packs Tires Motors Standoffs Electrical Circuitry Sensors Circuit Motor Drivers Circuit Rabbit

Design Decisions To make it as compact and light as possible To keep the wiring neat To minimize the amount of sensors used To organize circuits by placing each part on three different layers.

Design Structure Consists of three layers of circuitry Chassis contains standoffs, which holds up the three layers Sensors Circuit – Bottom Layer Motor Drivers Circuit – Middle Layer Rabbit and Switch – Top Layer

Overall Design

Sensors Layer Two sensors in front of mouse Three sensors each on left/right side of mouse Has a hole in the middle to lead motor wires to middle layer

Motor Drivers Layer Contains motor drivers circuit Also holds the voltage inverters that connect to each sensor panel.

Top Layer Contains rabbit and switch. Neatly covers the motor drivers layer

Final Status Sensors Circuit and Motor Drivers Circuit works Used Circuitwriter to make connections in circuit Sensors are attached to body using velcro

Problems That Occurred Altering Design Scheduling conflicts Too much time spent on debugging Bad Connections Broken Parts Switch incorrectly connected

Outstanding Problems Unable to move due to a broken rabbit

Future Improvements Time management Etching More visually appealing Coding

Questions?