Integration and Test (I&T) …The forgotten subteam Kevin Killian, Coach Pascack  ONEERS, Team 1676

Slides:



Advertisements
Similar presentations
Team 1985 Robohawks A Systems Engineering Approach to their Rookie Year Dan Robinson, Mentor.
Advertisements

Beta Testing: The Contractor’s Perspective Trns·port User Group Meeting October 2005.
INTRODUCTION TO ROBOTICS AND MICROCONTROLLERS Instructors: Tijjani “TJ” Mohammed and Tarek Abdel-Salam.
Offensive/defensive evaluation: Define all functionalities of the game brainstorm early designs, evaluate feasibility, resource requirements Shooting (High.
What do Computer Scientists and Engineers do? CS101 Regular Lecture, Week 10.
EE 296 TEAM “DA KINE” MICROMOUSE PROJECT PROPOSAL Team members: Software Group - Henry, James Roles : tracking, mapping, guidance, interface Hardware Group.
FIRST Robot Design: a team- based process Andy Baker Mechanical Engineer, Delphi Corporation Co-Owner, AndyMark.biz Lead Engineer, team 45.
Project Status Update II R09230: Open Architecture, Open Source Unmanned Aerial Vehicle for Imaging Systems A. Benjamin Wager (ME) B. Michael Skube (ME)
Auto - Drive An Automated Driving Range. Team Members Mike Loiselle Jared Beland Jeremy Paradee.
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.
Preliminary Design Review
WBS & AO Controls Jason Chin, Don Gavel, Erik Johansson, Mark Reinig Design Meeting (Team meeting #10) Sept 17 th, 2007.
A utonomous W arehouse F orklift U tilization L ayout Michael F. Maher vs. Peter A. Zarcone.
Team Bi-directional -Keith Beland -Christian Brinegar -Justin Marsha.
Ellery Wong Senior Systems Engineer, Xerox Corporation Co-Team Leader, Team 191 Xerox/Joseph C. Wilson Magnet HS X-Cats (Est – Rochester, NY)
FIRST Robotics A view from the Systems Engineering Perspective Chris Mikus January 2, 2006 Rev 0.2.
Tracking Rover Team Rubber Ducky Joshua Rubin Alexander Starick Ryan Ramos Alexander Chi.
EE 296 TEAM “DA KINE” MICROMOUSE PROJECT PROPOSAL Team members: Software Group - Henry, James Roles : tracking, mapping, guidance, interface Hardware Group.
Software Developer By: Charlie Edwards Period 6 th Mrs. Truong.
CSC230 Software Design (Engineering)
Natasha Benko, Kevin Jacobsen, Marcus LaRose, Scott Timme October 14, 2009 Our design will automatically calibrate your speedometer according to tire size.
 At the end of this class, students are able to  Describe definition of input devices clearly  List out the examples of input devices  Describe.
Automated Inspection Using Machine Vision
E-LABORATORY PRACTICAL TEACHING FOR APPLIED ENGINEERING SCIENCES W O R K S H O P University of Oradea, Romania February 6, 2012 G E N E R A L P R E S E.
1 RoboSapien Based Autonomous Humanoid Robot Researched and Presented by Nick Repka.
Modularly Adaptable Rover and Integrated Control System Mars Society International Conference 2003 – Eugene, Oregon.
Team HazardHawk Team HazardHawk 2008 April 24, 2008.
Mentors Workshop Control System Sub-System Mark McLeod Team 358 Festo/Hauppauge H.S. F For I Inspiration and R Recognition of S Science and T Technology.
From Research Prototype to Production
MidKnight U: Who We Are Nabeel Peshimam & Nikhil Ramesh October 6 th, 2014.
OVERALL ROBOT DESIGN, FTC STYLE PRESENTED BY: ANDY BAKER Sept
Product Evaluation & Quality Improvement. Overview Objectives Background Materials Procedure Report Closing.
Automated Bridge Scour Inspection FSU/FAMU College of Engineering Team 7 Proposal 10/27/2010.
Overview What is Arduino? What is it used for? How to get started Demonstration Questions are welcome at any time.
Chapter 1 Careers in Electricity and Electronics.
Product Evaluation & Quality Improvement. Overview  Objectives  Background  Materials  Procedure  Report  Closing.
Juan David Rios IMDL FALL 2012 Dr. Eric M. Schwartz – A. Antonio Arroyo September 18/2012.
Operating System Principles And Multitasking
FTC Home Page FTC Game Page FTCGAMEPAGEFTCGAMEPAGE.
Computer Hardware Engineers
COMPUTER ENGINEERING SAMUEL ROMERO.
Engineering and Related STEM Careers BY MITCHELL PARTLOW.
ARTICULATION. What is articulation? It’s the way a robot interacts with the field and game objects Articulation systems usually have manipulators (mechanisms.
ClearVision Final Presentation Senior Design 1. Team Members Travis Ann Nylin Electrical Engineer System Testing Schematic Data-Logging and Retrieval.
Electronics and Controls
EG1003: Introduction to Engineering and Design Product Evaluation & Quality Improvement.
Aircraft Carrier Draft Measurement Ship Draft Team - Fall 2015.
Scrumm meeting. Mechanical Done. Tire vs belt? Tire chosen. What to do? Do a prototype of a car. Continue with design.
Mar 18, 2003PFIS CDR1 Control System Summary of Changes Since PDR All the motors, drivers, sensors, switches, etc. have been chosen Built up a mechanism.
Parasoft : Improving Productivity in IT Organizations David McCaw.
Design Aim: How can we solve open- ended design problems? Open-Ended Problem Solving.
Capstone design Remote manless probe Kim Jinkwang Han Seongkyu.
The 3 Jobs I would Like to have Electrical Engineer (Electronic) Computer Software Engineer Computer Programmer By Eric Hamilton.
P10203 LV1 MOTOR CONTROLLER FINAL REVIEW MAY 14, 2010 Electrical: Kory Williams, Adam Gillon, Oladipo Tokunboh Mechanical: Louis Shogry, Andrew Krall.
Laboratory Information Management Systems (LIMS)
PREPARED BY G.VIJAYA KUMAR ASST.PROFESSOR
Planetary Lander PDR Team Name
Product Evaluation & Quality Improvement
Product Evaluation & Quality Improvement
Product Evaluation & Quality Improvement
Product Evaluation & Quality Improvement
ECE 477 Final Presentation Team 1  Spring 2008
Control System Summary of Changes Since PDR
Heart Pump and the Circulatory System P17080
ACOE347 – Data Acquisition and Automation Systems
ECE 791 Project Proposal University of New Hampshire
Internal components of a computer.
System Analysis and Design:
CLASS® Compressible Liquid Adaptive Suspension System
Presentation transcript:

Integration and Test (I&T) …The forgotten subteam Kevin Killian, Coach Pascack  ONEERS, Team 1676

Which subteam does these tasks?  Builds and maintains the practice field  Follows the weight budget  Conducts drive team selection  Decides who gets the working chassis on a day-to-day basis  Balances driver practice vs. programming on the live robot

How about….

Integration and Test in R&D Organizations - Aerospace  For aerospace product development, I&T is a separate group Results must be trusted by product team and customers (and regulatory agencies) Used to find defects early in the design process Sets pace of project by scheduling test “gates” Runs customer acceptance/ verification testing  For programming, I&T tests sub-modules and integrates software with hardware

Integration and Test in R&D Organizations - Science  Typical entry-level job in an R&D lab: conduct testing and collect & analyze data  For scientific research, creating test and measurement equipment is often the hardest part of the job

Roles of I&T  Manage interfaces between assemblies and between subteams  Manage Assets  Test assemblies and components  Perform compliance testing  Track development schedule  Manage budgets  Perform system test

Manage Interfaces  This is the integration part  Examples of interfaces Software and chosen hardware Electronics and the components they drive Mounting of electronics Perform compatibility testing (try out a prototype) Prioritize modularity/modification ease

Manage Assets  The robot-in-process Driver testing and practice Software development Hardware integration onto the chassis  The field Manipulator prototyping Driver practice Field construction and maintenance  And….

The new control system  Wiring  Bench Testing Electrical Programming  Installation into the robot  Making the chassis work vs. additional programming development

Test Assemblies and Components  Create test specifications and test plans  Build test equipment  Conduct tests prior to integration of the components or assemblies  Examples of component or assembly-level tests Camera discrimination before camera mounting Sensor effectiveness before sensor mounting Bench testing of manipulator/scoring/collecting device Incoming testing of motors, belts, chain, etc  Find design errors or defects early

Perform Compliance Testing  Can be from sub-component level to complete system level  Test Physical characteristics (size, weight)  Test Performance characteristics (ball shooter velocity)

Manage Budgets  Weight  Power  Possibly height, width, length  Control Board Ports and modules  Buttons on operator panel

Perform System Test  Write test specifications  Write test plan  Build simulated field  Schedule testing  Schedule game practice (Beta Testing)  Choose Tournament operators (drive team)

Who should be assigned to I&T?  A strong, respected team member to enforce the development schedule  A few good math & science students Geometric analyses Physics computations (ball trajectory)  Members who may not work on robot fabrication, but would enjoy field construction  Members who can create and conduct measurements and tests Detail-oriented Analytical

Example: Clyde (2006 Aim High)

2006 Assembly/Component-Level tests  Camera accuracy – measured vs. computed angle to green light in 2 dimensions  Conveyor speed and capacity  Turret and tilt “lock-on” to green light  Ball shooter velocity

Let’s Brainstorm: 2009 Testing  Assembly-level testing?  Component testing?  System testing?  Other Suggestions?

Gracious Professionalism… …don’t leave high school without it!