Projects 1: Project Kickoff Meeting Project: Design an Interface between a Robot and a LTU Laptop Group members: Colin Black Steve Holcomb.

Slides:



Advertisements
Similar presentations
Using three IR sensors, SensingBot can sense the front obstacles so it can avoid them. Sensing.
Advertisements

TrailerBot is a robot that moves trailer as using connecting device on the back of a truck with only driving space. Learn about standard that divides vehicle’s.
Wait, sound sensor >70, Port 2 Flowchart – Heartbeat 1 Start Motor A, Move Backward, 1/3 Rotation, Power 20 Wait, 1 Second Sound Sensor (Port 2) Less than.
V EX C OACHES ' T RAINING October 12, Agenda for Today 9 – 10 AM : Tina Reeves and the Engineering Notebook 10 – Noon : Finish Building, Basic Robot.
Part 1: Introduction FRC Introduction  FRC 2907 since 2008  Each area of the robot has a team assigned  The Electronics team is headed this year.
RaceBot can do car race using two DC motors. Let's learn how to go forward, backward, right turn, and left turn. with practicing ' ㄱ ' shape racing, and.
Robot Programming. Programming Behaviors Behaviors describe the actions and decisions of your robot.
Intelligent Ground Vehicle Competition 2006 Brigham Young University.
The Pied Pipers Alyssa Visitacion Ken Shum Joanne Flores.
EE 296 TEAM “DA KINE” MICROMOUSE PROJECT PROPOSAL Team members: Software Group - Henry, James Roles : tracking, mapping, guidance, interface Hardware Group.
Nandini Vemuri (EE) Jason Jack (CE) Ryan Schmitt (CE) Jeff Howe (EE) John Corleto (CE) Emily Phillips (EE) Power Distribution Subsystem Wireless Communication.
Curry Mouse EE 296 Project Proposal Presentation February 11, 2006.
Right Face Introductory Presentation. Opening Activity How can you use this to make a right turn program? This is your program from Full Speed Ahead to.
The Prodigy Micromouse 296/396. Team Members/Assignments Dale Balsis (396) – Web Designer/Hardware Tyson Seto-Mook (396)– Project Supervisor Calvin Umeda.
Team P.A.C.K men EE 296 Project. Chris Mcleod Hardware Specialist.
Nandini Vemuri (EE) Jason Jack (CE) Ryan Schmitt (CE) Jeff Howe (EE) John Corleto (CE) Emily Phillips (EE) Power Distribution Subsystem Wireless Communication.
Curry Mouse EE296 Final Presentation Wednesday, May 10, 2006.
EE 296 TEAM “DA KINE” MICROMOUSE PROJECT PROPOSAL Team members: Software Group - Henry, James Roles : tracking, mapping, guidance, interface Hardware Group.
Table Dancer Final Design Presentation 10/20/04 Team Members: Ryan Gray Dale Williams Emeric Rochford Dan Beard.
Remote Surveillance Vehicle Design Review By: Bill Burgdorf Tom Fisher Eleni Binopolus-Rumayor.
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.
LEGO Mindstorms NXT Programming We will be using the Common Palette for our Robots This is how you download your program onto the brick Drag and drop a.
Controller, Sensors and Motors Ding Ke Tutorial 1, UGB 230N.
BugBot is a robot that walks with 6 legs not using wheels Bug.
FanBot is a fanning robot using High-speed DC Motor. Fan.
Modeling, Simulation, and Control of an Omni-directional Robotic Ground Vehicle Andrew Niedert, Richard Hill, and Nassif Rayess University of Detroit Mercy,
Remote Control of a Furby Toy with Bluetooth
The George Washington University Department of ECE ECE Intro: Electrical & Computer Engineering Dr. S. Ahmadi Class 3.
Twyla and Jordan.  Light over black line  Runs roverbot.
GROUND UTILITY NETWORK DECIPHERING AUTOMATED MACHINE GROUP 10 BLAKE SIMONINI DIDIER LESSAGE GABRIEL RODRIGUEZ G.U.N.D.A.M.
JMC – Joint Motion Controller Complete guide to building and testing each JMC.
VEX Drive Trains.
A-Tech Technical Training. Robotic Design - Basket Grey pieces act like funnel Black rubberband keeps basket closed.
ECE 001 Final Presentation: Escape from Maze and Biomedical Centrifuge Experiment Scott Trocchia The George Washington University Computer Engineering.
Overview of Project 3 Slides are available at : Updated 1/28 Due Date for project has been extended to next Friday 2/6.
How to link the robot and the computer (Bluetooth) How to turn on and off How to connect the adaptor Fluke card connection Sec Getting Started How.
Cass Lake Bena Robotics.  Drivetrains  Electrical System  Operator Interface.
BullBot is bull robot that can have bull fight with techniques of butting or lifting. Learn how bull fight, Korean traditional game, had started and kinds.
Erin Halseth, Will Gottschalk, Briana Warschun, and Michaella Gaines
Engineering H193 - Team Project Gateway Engineering Education Coalition Lab 1P. 1Spring Quarter Introduction to Sensors Lab 1.
Automatic accident avoiding system PROJECT MEMBERS MUTHUKUMAR.K (05ME33) SAKTHIDHASAN.S (05ME39) SAKTHIVEL.N (05ME40) VINOTH.S (05ME56) PROJECT GUIDE:
Robot Programming. Programming Behaviors Behaviors describe the actions and decisions of your robot.
The George Washington University Department of ECE ECE Intro: Electrical & Computer Engineering Dr. S. Ahmadi Class 4/Lab3.
The George Washington University Electrical & Computer Engineering Department ECE 002 Dr. S. Ahmadi Class3/Lab 2.
Oregon Robotics Tournament and Outreach Program RCX Basics.
Rescue Robot Day 2 Exploring Computer Science Lesson 6-11.
Wheels: Go Forward Speakers: Say “Hello” OSCAR: Go Forward Say “Hello” Remote Control PC.
Cass Lake Bena Robotics Team 3134 & Team  Drivetrains  Electrical System  Operator Interface.
GreenJacket IMDL Summer 2002 Final Report Matthew Chernosky August 6, 2002.
VEX Cortex Video Trainer using ROBOTC
What you asked me to teach…
This is the Lego NXT ->
VEX Motors & Servos J.M. Gabrielse.
Programming Part 2 Mod Kit
BEGINNER PROGRAMMING LESSON
Serial Data Hub (Proj Dec13-13).
Motion transmission systems
GEARS:.
VEX Motors & Servos J.M. Gabrielse.
Robots with four wheels
Forward Until Touch Robot goes forward until it hits a wall.
Training 11/11/16 Robot Code (WPILib).
The George Washington University Department of ECE ECE Intro: Electrical & Computer Engineering Dr. S. Ahmadi Class 4.
BEGINNER PROGRAMMING LESSON
Robot Challenges.
Which way does the robot have to turn to get to the charger?
The George Washington University Department of ECE ECE Intro: Electrical & Computer Engineering Dr. S. Ahmadi Class 4.
Oregon Robotics Tournament and Outreach Program
Exploring Computer Science Lesson 6-11
Presentation transcript:

Projects 1: Project Kickoff Meeting Project: Design an Interface between a Robot and a LTU Laptop Group members: Colin Black Steve Holcomb

Objective Design and implement an interface between a robot and a LTU laptop

Target Goals: Robot should be able to traverse forwards and backwards with the capability to turn Robot should be able to travel at two to three speeds Interface should be easily available for use in third-party programs –i.e. writing maze-traversal programs

Design Sub-Systems Laptop Interface Sensor System Steering System Drive System Power System

Power Sub-System Capable of powering interface and robot –Laptop runs on batteries Power sources under consideration: –Batteries Heavy Limited functional time –110V connection to maze exterior Limits size of maze Requires addition of transformer on robot

Drive Sub-System A single drive wheel located at the rear of the robot Variable speed bi-directional motor Controlled through interface board Tachometer connected to drive wheel for distance/speed reporting to interface

Steering Sub-System Based on standard Rack and Pinion design Single servo/motor to control steering angle Angle controlled through interface board

Sensor systems Initial sensor type: touch Sensor contact causes immediate event/interrupt; drive halted Expansion of system possible to include other sensor types

Laptop Interface Use of Handyboard to relay commands to drive/steering sub-systems and contact data from sensor sub-system Laptop interfaces to Handyboard through Parallel/Serial port Interface to third-party programs through binary API or compile-time headers –Knowledge of Windows 2k/XP Device Drivers required

Timeline Parts ordered by11/30 Drive system/chassis built02/01 Steering system built02/15 Sensor/Interface built03/01 Device Drivers/Headers written03/08 Final testing03/29 (Competition date - RoboFest)04/27