Week Six. We tested the second robot but when it hit a cup, it flipped over and broke. Our other bot now turns on and turns off in 89 seconds. Bravo!!!!! The dustructo bot is born!

Week Five. We totally changed the design of the robot and are going for a dustructo bot. We had the help of a professional computer programmer but we still changed our strategy like four or five times. The good thing is that it now is running on the board and all of our sensors going except for the CMU cam which we don\'t know how to run yet. Things are getting better.

Week four. The week was a waist of time as far as any advances go. We spent all our time talking about what we wanted to do but then changing our minds later on. Good news is that we now have eighteen points. I don't now how good that is compared to the other teams but it's way better than zero and we're happy! A programmer guy came on Friday and helped us clear up a few programming difficulties.

Cassin made a web site for our school. Click HERE to go to it.

Week three was filled with problems and disagreements. Nobody could seem to agree on the design of the bot so we were going no where fast. Mike seemed to be doing most of the work while the others just argued. Not much got done but we did make progress on the documentation site

Week two. The programmers are struggling along with the programming. Mitchell says it's "challenging" and that's exactly how I would describe this web site. Every one is organizing the legos. An important task if the rest of the competition is to go smoothly. The class size has shrunk considerably from nineteen students down to about fifteen. We're all learning fast and getting along well with each other. Design of the robot has started with brain storming and trying out different sensors and we are starting to think about what we want our robot to do once on the board.The big acomplishment for the week was getting our SONAR sensor to work! Now, thanks to Mitchell, our robot stops before hitting anything. I would say that this week has been a success!!

 Week one. Our initial group turned out to be much larger than expected so our first task was to find out who really wanted to be in Botball and who knew what they were committing to. Botball requires discipline, responsibility, hard work and commitment so we needed the right people. The documenting team checked out the web site and listened to the rules of Botball. Programmers and designers took inventory of parts and familiarized themselves with the rules and programming.