CSE Design Lab Milestone III Karl SchwirzJames Hopkins Dennis O’FlahertyDave Festa

WHEN LAST YOU SAW US…  Implement LEGO NXT Robot using Microsoft Robotics Studio Use MSRS to interface with LEGO NXT Brick’s various sensors and allow the robot to traverse a room detecting objects in the room. Robot will be able to traverse the room on an “automatic” mode as we as a real time Bluetooth controlled mode.

THE BOT Ultra Sonic Sensors Touch/Pressure Sensors

WHAT WE’VE BEEN UP TO… The James Show! James has been busy on the construction of the robot and making sure all the sensors and driving motors are working properly. After a hiccup in our initial design the robot will now be built with three wheels, two in back and one centered in the front. Also the motor driving the eyes (sonic sensors) has not been functioning properly. Initial designs have been when an object is detected the eyes will turn to the right and left and determine which route has more space. However, the motor cannot return to its origin consistently, after some research James found that it is not possible and the robot will turn to the right and left in order to assess the terrain.

WHAT WE’RE UP TO NOW… Now that James is done constructing and configuring the bot the project has been passed onto the rest of us… Dennis and Dave: Further configuration of the sensors Automate the bot Implement Manual Controls on the bot Karl: Integrate sensor data to construct a visual representation of what the bot “sees” and well as store a map so that the bot will remember where it’s been. * If there is time create a sub-routine that will allow the bot to plan the best route to get from A  B (Kind of like GPS Road mates) James: As his major task has been completed James will now be providing auxiliary support to the group as necessary.

WHAT WE’RE UP TO NOW… Team: Jointly develop a UI that will facilitate the Auto/Manual Controls as well as Real Time Visual Representation. Welcome to Bot Controls… now take over the World! STOP! Auto Manual

WHAT WE’RE UP TO NOW… Team: Determine codename for robot based on which famous movie robot it looks most like… Wall-E Number Johnny Five Number Wall-E Five???

WHERE WE’RE GOING… Over the next several weeks we will be writing our respected implementations and will be testing them to the point of slowly integrating them together one at a time. Why one at a time? Allows for in depth testing Should there be an issue with one of our implementations it will be easier to pinpoint either a compatibility error or a programic error.

OUR TIME SCHEDULE… MOSTLY ON TRACK

RE-SCOPE OF OUR PROJECT Continuing Project Definition Improve, revamp, and finish bot’s various capabilities dealing with Manual and Automatic controls Create a virtual map based on returned sensor data Create an intuitive UI that will allow users easy access to all functions of the bot. Project Software Usages Microsoft Robotics Studio via Microsoft’s Visual Studio 2005/2008

’S (QUESTION MARK IN BINARY CONVERSION)