The Yellow Dart Project Summary Robotic Triathlon Heiko Maiwand Megan Bardolph Fred Pabon Bryan “ The Destroyer ” Shaw.

Slides:



Advertisements
Similar presentations
IRobot, Prosthetic Arm, and Rescue Robot Group 4 Adrian Burke Darren Draper Collin Palmer Max Reinisch Viyat Jhaveri Can Gurkan.
Advertisements

Identifying "Good" Architectural Design Alternatives with Multi-Objective Optimization Strategies By Lars Grunske Presented by Robert Dannels.
Ed Chu Justin Milks Kevin Patel Rachel Bittenmiller Shawn Hymel.
Team A.C.M.E. ECE 361 Final Project. Team Members A my Sibilia C hris Waters M att Fike E ric Benz.
Title Presentation based on $4M / year for 5 years proposal option.
Justin Harger | Adi Kapoor | John Kolodick | Captain Morgan Rebels.
TΣAM M1NDSTӨЯMΣЯZ Aaron Doades, Bryce Brown, Corey Richmond, John Witting.
The Prodigy Micromouse 296/396. Team Members/Assignments Dale Balsis (396) – Web Designer/Hardware Tyson Seto-Mook (396)– Project Supervisor Calvin Umeda.
Team SMAC’s Design Experience Design Process, Successes, and Failures.
Micromouse Team:. Team Members Kanoa Jou Ryan Sato KiWoon Ahn Brett Ikei.
Ellery Wong Senior Systems Engineer, Xerox Corporation Co-Team Leader, Team 191 Xerox/Joseph C. Wilson Magnet HS X-Cats (Est – Rochester, NY)
Project Summary for Chitty Chitty Bang Bang February 26, 2004.
From Legos to Legend: The Team Voltron Final Presentation.
Team Soda Evan Hanusa Doug Nelson Argha Raychowdhury Kris Renfro.
Team Oprah John Koch Amanda Olvey Matt Robertson Cole Ulen.
Team Blue Sweater, ECE Final Design Review “Deep Blue”
FIRST Robotics A view from the Systems Engineering Perspective Chris Mikus January 2, 2006 Rev 0.2.
Design of Embedded Systems Task partitioning between hardware and software Hardware design and integration Software development System integration.
EE 296 TEAM “DA KINE” MICROMOUSE PROJECT PROPOSAL Team members: Software Group - Henry, James Roles : tracking, mapping, guidance, interface Hardware Group.
Software Test Plan Why do you need a test plan? –Provides a road map –Provides a feasibility check of: Resources/Cost Schedule Goal What is a test plan?
CPM -200: Principles of Schedule Management IPM 2002 Fall Conference PMI-College of Performance Management – Professional Education.
{ Win more business Capture and Proposal Management.
Creative Training Ideas Presented by Your Name. Agenda Overview Introduce the Team Brainstorming Objectives Rules for Brainstorming Brainstorming Activities.
What is RobotC?!?! Team 2425 Hydra. Overview What is RobotC What is RobotC used for What you need to program a robot How a robot program works Framework.
Copyright © 2013 Human Workflows, LLC 6 Team Performance Tools.
Project Management Chapter 5, PG 92. Introduction Why is software management particularly difficult?  The product is intangible Cannot be seen or touched.
Pre-Class Wednesday What do you think is the difference between a computer engineer and a software engineer?
ORTOP WORKSHOP 3 ROBOT NAVIGATION & MISSIONS ORTOP WORKSHOP 3 ROBOT NAVIGATION & MISSIONS.
Design Development Image credit:
Software Inspection A basic tool for defect removal A basic tool for defect removal Urgent need for QA and removal can be supported by inspection Urgent.
CHAPTER 18 OPERATIONS MANAGEMENT. OPERATIONS MANAGEMENT (OM) n The Nature of Operations Management u Innovative managers do not just manage people--they.
By Mesa Robles Robotworks and Droids Robotics
Chapter 5: Project Scope Management Information Technology Project Management.
OVERALL ROBOT DESIGN, FTC STYLE PRESENTED BY: ANDY BAKER Sept
Engineering Design George E. Dieter Mc Graw Hill.
Teamwork in a Research Setting Jared Oluoch and George Corser.
Welcome to the SEED Collaborative Workshop Tyumen, Siberia, Russia October 9-12, 2006.
1 Robotics Challenge Overview. 2 Why? -Viking was tested at the Dunes -Develop intelligent robots -Explore Robotics.
Robotics & Engineering Design Projective Management Chin-Sung Lin Eleanor Roosevelt High School.
Physics Project Management Chin-Sung Lin Eleanor Roosevelt High School.
Pre-Class Wednesday What do you think is the difference between a computer engineer and a software engineer?
Request for Proposal (RFP)
Photography 101. In this segment, we will think about positioning, arranging, and other elements.
Copyright © 2015 Human Workflows, LLC 6 Team Performance Tools (pg. 97) Randall Ribaudo, PhD Larry Petcovic, MS 2 Human Workflows, LLC Co-founders, SciPhD.com.
Preliminary Design Review (PDR) Team Amaze Me. EE 296 Project (MicroMouse) Members –Brandon Gibu –Ah Ram Kim –John-Kalani Miyajima –Justin Ogata Website.
Com.Tech 3104 Outcome 12 By: Evan And Mark Progress Report.
SECON 2012 Final Presentation. Team Michael Helmbrecht Electrical Engineer Measurement Tasks Course Construction Chris Nicholas Computer Engineer Measurement.
1. 2 Quiz Preparation l Have Quiz sheet ready. l Top Center: QUIZ 2 l Upper Right: »Name (L, F, MI), »Today’s date 8/28/12 »Lab day, time »section number.
Rescue Robot Day 2 Exploring Computer Science Lesson 6-11.
How to Build Test Inventory Test inventory is built and updated as the software project moves from phase to phase –Start with Requirements List the actual.
M. Nelson, 21 Mar NorthWest Louisiana Autonomous Robotics Competition (NWLA-ARC) 2 Challenges – 4 Bottle Race – Board Challenge Awards for Event.
Project Overview  Introduction  Clawbot Build  Design Modification  Design Development  Programming  Sensors  Advanced Sensors  Open design challenges.
SHOOTING FUNDAMENTALS.  Eyes – what to look at – front of rim  Feet – Balance – point at rim or angle  Shooting foot – Forward and at middle of rim.
Roller Coaster Overview ENGR1182.  As part of the project in ENGR , your team will: Innovate, Design, Build, Document, Test a model roller coaster.
BUS 611 Week 4 Assignment Integrated Project Management To purchase this material link
Risk Management.
Systems Analysis and Design
ORTOP Workshop 3 Robot Navigation & Missions
Roller Coaster Overview
Moving into Design Chapter 8.
Robot Soccer First Design Review
The George W. Woodruff School of Mechanical Engineering
CPMGT 300 Competitive Success/snaptutorial.com
Project Overview Introduction Clawbot Build Design Modification
Lego Robotics Will Schleter 11/12/2018.
Chapter 2 The Process of Design.
Systems Analysis and Design
Systems Analysis and Design
Effective Project Management: Traditional, Agile, Extreme
Exploring Computer Science Lesson 6-11
Presentation transcript:

The Yellow Dart Project Summary Robotic Triathlon Heiko Maiwand Megan Bardolph Fred Pabon Bryan “ The Destroyer ” Shaw

Problem Overview Speed/Obstacle Course Basket Shots Block Pushing

Process Team Meetings Team Meetings Code of Conduct Code of Conduct Roles Roles Agenda and Minutes Agenda and Minutes Team Goals Team Goals List of Priorities List of Priorities Creativity Creativity Brainstorming Brainstorming

Process: Decision Making Design Alternatives Design Alternatives Locomotion/gearing Locomotion/gearing Shooting Baskets Shooting Baskets Pushing Pushing Software/Tracking Software/Tracking Basis for Design Basis for Design List of Priorities List of Priorities Pugh Matrix Pugh Matrix Trial and Error Trial and Error

Subsystem Development Subsystem Complete Integration Testing Does system work? Yes Project Complete Can we fix with software? No Yes Software Fix Software Test Hardware Change Required Process Flow Chart

Design Elements

Process: Tools Course Tools Course Tools Decision Making Decision Making Pugh Matrix Pugh Matrix Testing Testing Project Schedule Project Schedule Design Review Design Review Verification Testing Verification Testing

Testing Formed Tests Formed Tests Based on PDS Based on PDS Focus on repeatability Focus on repeatability Subsystem Testing Subsystem Testing Sensors Sensors Speed Speed Ballouncer Ballouncer Pushing Pushing

Test Completion Robot performed to our standards Robot performed to our standards Some specifications met, some exceeded Some specifications met, some exceeded Speed Course Speed Course Ball Dropping Ball Dropping Block Pushing Block Pushing

Test Results Speed course in under 25 seconds Speed course in under 25 seconds 30 baskets consecutively 30 baskets consecutively Completed block push 10 times Completed block push 10 times After completing the tests, we determined that our robot was fit to compete, and expected to do very well After completing the tests, we determined that our robot was fit to compete, and expected to do very well

Competition Results Did not perform as well as hoped Did not perform as well as hoped Bump sensor stuck Bump sensor stuck 2/3 baskets 2/3 baskets Coding issues Coding issues Came in third place Came in third place Pleased with a top three finish Pleased with a top three finish

Process Lessons Process Lessons Snack time Snack time Assign specific tasks to people Assign specific tasks to people Agendas worthwhile? Agendas worthwhile? Risk management Risk management The Good the Bad and… the Lessons Learned

Design Lessons: Good Design Lessons: Good Ballouncer Ballouncer Accurate Accurate Reliable Reliable Wide pushing surface Wide pushing surface Keeps block straighter Keeps block straighter AWD AWD Robust software Robust software The Good the Bad and… the Lessons Learned

Design Lessons: Could Improve Design Lessons: Could Improve Touch sensor location Touch sensor location No front wheels No front wheels Could have had faster speed algorithm Could have had faster speed algorithm

Summary 3 rd in competition ! 3 rd in competition ! Met PDS conditions Met PDS conditions Worked well as team Worked well as team Used course tools Used course tools Pepe is awesome Pepe is awesome

Future Project Robot that serves lunch Robot that serves lunch Opens pop cans Opens pop cans Opens bags Opens bags Makes sandwich Makes sandwich Places items on plates Places items on plates Arranges place settings Arranges place settings Jumping Robot Jumping Robot Use high speed and ramp Use high speed and ramp Frog-like legs Frog-like legs

Questions?