Sensors and Control Applications 7 Rivers Robotics Coalition December, 2015 D. Foye.

Slides:



Advertisements
Similar presentations
Study Habits Successful students have good study
Advertisements

Test-First Programming. The tests should drive you to write the code, the reason you write code is to get a test to succeed, and you should only write.
© 2006 Prentice Hall Leadership in Organizations 10-1 Chapter 10 Leading Change in Organizations.
Lesson 9: Making Decisions
Add and Use a Sensor & Autonomous For FIRST Robotics
Test-Driven Development with Lego Mindstorms Ru Maaret
IRobot, Prosthetic Arm, and Rescue Robot Group 4 Adrian Burke Darren Draper Collin Palmer Max Reinisch Viyat Jhaveri Can Gurkan.
Taking a Waterfall Project Agile REF: Paul Geberth GCSS-J Project Manager Establishment of an Agile Project.
Effective First Strategies With Peter Jasko. Topics That Will Be Covered Strategic Design Pit Scouting Match Strategies.
What is the Best Position? More Advanced Positioning February, R. Baker1.
Topics: Interviewing Question Type Interviewing techniques
Engineering H193 - Team Project Gateway Engineering Education Coalition P. 1Spring Quarter 2007 Week 8 Day 1 Notes on Individual Competition and Visual.
1 Software project management (intro) An introduction.
©2006 CSUC Institute for Research in Intelligent Systems Introduction to Coding June 15, 2006.
Agent-Based Acceptability-Oriented Computing International Symposium on Software Reliability Engineering Fast Abstract by Shana Hyvat.
James Tam Evaluating Interfaces With Users Why evaluation is crucial to interface design General approaches and tradeoffs in evaluation The role of ethics.
Adaptive management AM is about learning to manage DYNAMIC systems more effectively There are two kinds of AM: –Passive (certainty equivalent): assumes.
AGILE PROJECT MANAGEMENT Cydne Zabel, INFX 543 Winter 2009.
By the end of this chapter, you should:  Understand the properties of an engineering requirement and know how to develop well-formed requirements that.
1 Shawlands Academy Higher Computing Software Development Unit.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Ch1 AI: History and Applications Dr. Bernard Chen Ph.D. University of Central Arkansas Spring 2011.
COMPUTER CONTROL Year 11. Lesson 1 Introduction to Computer Control.
2009 Team America Rocketry Competition Some Thoughts on Having a Successful TARC Experience.
Robotics- Basic On/Off Control Considerations. On/Off Control Forms the basis of most robotics operations Is deceptively simple until the consequences.
Sensors. Sensors are for Perception Sensors are physical devices that measure physical quantities. – Such as light, temperature, pressure – Proprioception.
Adapted for STLP Camp ‘09 Mobile Robots Why do robots need to move?
KEY KNOWLEDGEKEY SKILLS  The principles and processes of learning as applied to the cognitive, associative and autonomous stages, including the role feedback.
LabVIEW Program and Data Flow Review LabVIEW Robotics Fundamentals.
Coding for the FIRST Tech Challenge: RobotC
SOFTWARE ENGINEERING1 Introduction. Software Software (IEEE): collection of programs, procedures, rules, and associated documentation and data SOFTWARE.
ROBOTICS VOCAB AND FLOWCHARTING. ROBOTICS VOCABULARY Robot- a machine capable of carrying out a complex series of actions automatically, especially one.
Please see this weeks session overleaf; which looks at some ways to help your players develop their fitness in a functional, football predominant fashion.
1 The Software Development Process  Systems analysis  Systems design  Implementation  Testing  Documentation  Evaluation  Maintenance.
Testing -- Part II. Testing The role of testing is to: w Locate errors that can then be fixed to produce a more reliable product w Design tests that systematically.
Chapter 16 Problem Solving and Decision Making. Objectives After reading the chapter and reviewing the materials presented the students will be able to:
SIPHER Students: Javier Lara, Darren Lamison-White Graduate Student Advisors: Ethan Jackson, Ryan Thibodeaux Controlling Robots: Long distance, straight-line.
More LEGO Mark Green School of Creative Media. Introduction  Now that we know the basics its time to look at putting some robots (or toys) together 
Computer Control.
University of Windsor School of Computer Science Topics in Artificial Intelligence Fall 2008 Sept 11, 2008.
Computer Control Using computers to control things.
Negative Power or Negative Rotation makes robot go backwards. But if both are negative, the robot will go forward! Move Steering Block.
SOFTWARE ENGINEERING1 Introduction. SOFTWARE ENGINEERING2 Software Q : If you have to write a 10,000 line program in C to solve a problem, how long will.
Data Gathering Techniques 27 th February Data Gathering Techniques System requirements specify what the system must do or what property or quality.
The Software Development Process
Engineering H193 - Team Project Gateway Engineering Education Coalition P. 1 Spring Quarter Observations from the Individual Competition Week 8 Day 3.
Monitoring and Evaluation in MCH Programs and Projects MCH in Developing Countries Feb 9, 2012.
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
Fast SLAM Simultaneous Localization And Mapping using Particle Filter A geometric approach (as opposed to discretization approach)‏ Subhrajit Bhattacharya.
You can do this as a nice warm up to get the players minds working. These simple ideas are designed to get (forces) players to look away from the ball.
BEGINNER FLL PROGRAMMING WORKSHOP BY DROIDS ROBOTICS & EV3LESSONS.
Quality Control Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill.
Deriving Consistency from LEGOs What we have learned in 6 years of FLL by Austin and Travis Schuh © 2005 Austin and Travis Schuh, all rights reserved.
Data Analytics – A Cost Effective Approach to Reducing Operating Costs Automatically “find what matters” in the data from building equipment systems and.
CSE SW Metrics and Quality Engineering Copyright © , Dennis J. Frailey, All Rights Reserved CSE8314M33 8/20/2001Slide 1 SMU CSE 8314 /
How Do You Make a Program Wait?
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
Deriving Consistency from LEGOs
Introduction SOFTWARE ENGINEERING.
Project Overview Introduction to Factory Automation Numerical Control
Control Loops Nick Schatz FRC 3184.
Project Overview Introduction Clawbot Build Design Modification
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
ASPECT ORIENTATED PROGRAMMING RESEARCH
An Introduction to VEX IQ Programming with Modkit
Lesson 9: Making Decisions
Advanced LabVIEW
Experiencing the Model for Improvement
Leading Change in Organizations
Presentation transcript:

Sensors and Control Applications 7 Rivers Robotics Coalition December, 2015 D. Foye

FIRST Robotics Challenges The robot must be functionally flexible- able to implement different strategies and adapt to the playing field environment Team members must provide most of the decision making and strategy- which cannot be pre-determined Some functions needed on the playing field can be pre-determined, and in fact must be- it is not practical to force all intelligent responses onto the operators/team So- what can the robot do autonomously???

Typical benefits of autonomous functions Consider a pre-designed, programmed function: When an identical sequence of operations must be performed multiple times- When a simple function must be performed quickly- more quickly than a human operator When a relatively simple function, aided by robot local sensors, must be effective, reliable, and result in good performance

Why sensors? Sensors allow us to implement “intelligent” robot autonomous functions Sensors provide information about the environment to the robot software we create BUT- CAREFULL ! Sensors don’t always operate and react the way we expect Sensors can be challenging to include in the robot and work the way we want them to

Reasons many teams do not use sensors Do not have them Do not understand what they do Have not seen successful applications Programming is complex

What do we use sensors for? In general, sensors are used to provide a measurement, which is then used to make a decision (in software) Sensors can also provide a measurement, which can then be used in continuous control

What can we do? Decide where the sensor will operate best Test ideas early by: Acting out the software sequence and watching for problems Running monitoring software for the sensor to: Try it and be sure it is working! Operate during operating walk-through to see if sensor is detecting what we want Try it when other sensor disturbances are present To use sensors well, you must understand and “be” the robot !

Internal Sensors vs. External Sensors Internal Time Wheel rotations Direction External Distance Barrier (touch) Sight- light, image, color

Two forms of Control Demonstrated Bang-Bang Robot program causes action to correct when target is exceeded Proportional Robot program causes proportional correction to error

Performance is related to the Error amount and strength of response Bang-Bang Too much correction can cause loss of control; I.E. -response outside of the control range Proportional Too much correction can cause loss of control; I.E. instability and rapid cycling, while too little may not be effective in maintaining control within the control range

Demonstrations- monitor

Demonstrations- Two sensors vs. One

Design Sequence Try the sensor, learn how it works and responds Operate the sensor in the application, add a monitoring function to watch for good or undesired responses Fine tune for the desired performance

Is it working well? Wow! You got your control system to work once ! Are you done? You can: Try it several times to see if success will repeat Change environment (within reason) to see when and if your design will fail Observe carefully for signs or hints of failure