I. Mechanical Design-

LOMU (RCX robot-Team 2)- It is designed to move forward and backward, to use touch sensors that give feedback and give the command to turn, and to utilize light sensors which sense the glare of the START overhead lights and give the command to start the robot program. LOMU is also programmed to pick up the nest and drag it to the goal line.

The team strategy is for the robot to knock over the tubes as it goes to the opposite end of the playing board.  The robot then turns back and forth to prevent the opponent from scoring.                                                   <TOP

The engineer initiates predefined commands one at a time.  Next the computer movement is checked and the command parameters are adjusted.  As example would be, a 1000 millisecond timer is set to stop the robot and lower the claw.  Next, the nest is dragged where it needs to be. The robot is then started.  When it works correctly, the robot is turned on to do a series of tasks.  Then corrections are made again and the procedure is repeated.

The name of the RCX robot is MOG . 

The name of the handyboard robot is To Hell and Back. 

• March 20, 2002- get pre-constructed robot to move and hit touch sensor andmakerobot back up.  Use light sensor to follow a black-tape line.   Hand out rules (no discussion).
• March 23, 2002-  Use light sensor to follow a black-tape line. Go around object sitting on the line.
• March 27, 2002 - Design Discussion and detailed agenda.
• March 30, 2002- Detailed agenda.
• April 3, 2002 - Meeting from 5-8 pm.
• April 6, 2002- Meeting
• April 8, 2002- Meeting and detailed agenda
• April 13,2002- Detailed agenda
• April 17, 2002-Meeting
• April 20, 2002- Meeting
• April 22, 2002 & April 24, 2002 - Finish design changes and continue testing programming.

April 27, 2002- Begin with light program and 90 secong time program.  Test all robots.

MOG

To "Hell"  and  back.

Raiden parts

•     March 20, 2002- We had problems preventing the robots from getting

    sidetracked when crossing another line.
 
•     March 23, 2002-We tried to determine how to get robot to return to line

    once it roamed off the line.
 
•     March 27, 2002- Lots of ideas but some more practical than others were

    generated.
 
•     March 30, 2002- We tried to build robot parts which could perform

    specific  Botball Challenge tasks. (Some configurations worked and some did
    not.)
 
•      April 3, 2002 - We kept taking robots apart and re-designing various

    ideas that we wrote programs for related to Botball Challenge tasks...( very
    frustrating...)
 
•      April 6, 2002- We adjusted designs for better structural integrity. More

    changes seemed necessary.
 
•      April 8, 2002- We adjusted designs for better structural integrity. More

    changes seemed necessary.
 
•      April 13,2002- We adjusted designs for better structural integrity. More

    changes seemed necessary.
                                                                                                                       <TOP>
•      April 17, 2002-We adjusted designs for better structural integrity. More

    changes seemed necessary.
 
•      April 20, 2002- We finalized our designs and programs and tweeked the

    problems that showed up.
 
•      April 22, & April 24, 2002 - We tried to finalize information from

    sensor input and response, and continued to enhance the structural integrity.
 
•      April 27, 2002- We finalized information from sensor input and response,

    and continued to enhance the structural integrity.

• TUTORIALS:
• Insectroides (tutorial)
• Adam's Robotics (tutorial)
• Karel the Robot (tutorial)
• Alphaworks Robocode (tutorial)
• MIT's Handy Board
• Interactive C Code Repository
• For Other Projects: Building Sensors for Handy Board
• AAAI Mobile Robot Competition Photos
• Lego Dacta Robot Kits, etc.
• Pitsco Lego Dacta Kits, etc.
• Download for Interactive C Programming Language m
• Interactive C Users Guide
• Manual for the Handy Board