Team Name: Group C.  Zisimos  Team Leader, Software Engineer  Richard  Hardware Engineer  Michael  Hardware Engineer  Jason  Software Engineer.

Slides:



Advertisements
Similar presentations
© 2006 MVTec Software GmbH Press Colloquium Part II Building Technology for the Customer’s Advantage.
Advertisements

Micromouse Meeting #2 PROGRAM DETAILS, APPLYING FOR FUNDING, OVERALL SYSTEMS.
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.
Introduction to Micromouse WVU IEEE Student Branch 9/24/2014 Stephen Itschner.
Embedded vs. PC Application Programming. Overview  The software design cycle  Designing differences  Code differences  Test differences.
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 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 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:
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)
Micromouse Projects LTD. Presents a STIG, Whitey, Zephyr Production.
Curry Mouse EE 296 Project Proposal Presentation February 11, 2006.
CheezStix! EE 396 Micromouse Spring 2007 Proposal Presentation.
Micromouse 296 Final Presentation Fall 2008 Group: Rabbitwagon.
Proposal Presentation Micromouse Spring 08 8” Comb.
Preliminary Design Review
TEAM MECHAZAWA Jeong Bang Riley Ceria Grant Higa.
KTD Micromouse Overview Team Goals Approach Outstanding Problems Future Solutions Final Status.
System for Engine Location Of a Web Train Paul Wimmer and Adam Weintrop Dr. Irwin and Dr. Schertz 2/27/06.
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.
TAKE YOUR JACKET OFF! Proposal Presentation  Members:  Jayson Nakakura: Chassis Design and Fabrication  Kellie Murakami: Circuitry Design and Fabrication.
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.
M & M EE 296 Project Spring 2004 Alex Gomera Sophomore: electrophysics?!?! Favorite EE Teacher: F. Koide I hope to be like that man 
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.
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.
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.
System for Engine Location Of a Web Train Paul Wimmer and Adam Weintrop Dr. Irwin and Dr. Schertz 3/6/06.
EE 296 TEAM “DA KINE” MICROMOUSE PROJECT PROPOSAL Team members: Software Group - Henry, James Roles : tracking, mapping, guidance, interface Hardware Group.
Fast D.A.D.I.. Team Members D - ale Balsis - Machinist D - ale Balsis - Machinist A - aron Tsutsumi - Electrician A - aron Tsutsumi - Electrician D -
DC Motor Control  mouse EE 496 Advisor: Dr. Tep Dobry.
Micro-Mouse Rotech means robust mice technology..
1 Object Oriented Programming Computer Systems Engineering (D2) and Programming (P)
Team Spot On! With Zebulon Clark Desiree And Earl.
To come up with a practicum project that full filled the 411 requirements Create a fun project that would get kids interested in science and engineering.
IEEE Robotics - Requirements Presentation Presented by Jason Abbett and Devon Berry.
IT Job Roles & Responsibilities Shannon Ciriaco Unit 2:
Program Development Cycle Modern software developers base many of their techniques on traditional approaches to mathematical problem solving. One such.
IEEE Robotics - Requirements Presentation Presented by Jason Abbett and Devon Berry.
Somerset Berkley Regional High School Robotics Engineering with LabView.
Back To Basics A BASIC Stamp Based Micromouse B2B MicroMouse Traditional MicroMouse  Language used › PBASIC  Drive systems › Servo Motors  Sensor.
By Mike Rogers November 19 th, Introduction What is not craftsmanship What craftsmanship is Why craftsmanship can be rare Why craftsmanship can.
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.
Nic Shulver, Welcome to Principles of Software Engineering Tutor: Nic Shulver Web site and Blackboard presence 100% coursework,
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
1 LBT Q Engineering Review ECS: Enclosure Control System, includes the dewpoint sensor, CA system upgrades, grounding, enclosure track performance.
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.
CMGT 555Competitive Success/snaptutorial.com
Proposal Presentation
The Secret to Solving Big Problems
Chapter 2. Problem Solving and Software Engineering
Presentation transcript:

Team Name: Group C

 Zisimos  Team Leader, Software Engineer  Richard  Hardware Engineer  Michael  Hardware Engineer  Jason  Software Engineer

 This is our first year of Micromouse so we are going to buy the parts kit  We are going with side sensors rather than top down because we want a smaller mouse.  A small and quick mouse is our goal  Lithium-ion polymer batteries  Greedy search method  If we get past greedy fast we will work on a “better” searching algorithm

 TIME!!!  Working in the lab and meeting as a group  FIXING BUGS IN CODE!!!  There are always problems when it comes to writing code so we want to leave a lot of time for the debugging of our mouse.  Our battery charger is currently not working  Tracking and the solving algorithms need to be perfect

 We want to hone our coding skills  Learn how to efficiently interface between hardware and software.  Learn the umouse basic skills just in case we decide to build a better faster mouse for another project.

 FINISH!  We do not want to take an “I”  Mini competitions 1 and 2  If our mouse is doing well we will head to the regionals