Monday, November 22, 2010

Final Project: Building the outside 2

The robot holds a marker that it draws while it moves. It will be placed on a piece of paper so that it's marks can be recorded. The paper will sit on the wood base shown below.
Carrying the base that the paper will sit on

Drawing

Drawings for the robot
The box is evolving!


Tuesday, November 16, 2010

Final Project: Building the outside

This week we worked even more on the outside of the robot. We retested the program and it still works!
About the outside, we made it so that it can be removed in case the cyborg fails in some way. If the cyborg were to stop working, then the outside could be moved to a new cyborg and our work would not be for nothing.
Working
The marker is attached to the cyborg using lego pieces. It can be easily adjusted so that the marker sits on the paper correctly.
The robot with pen

The cover for the robot

The cover for the robot

Wednesday, November 10, 2010

Final Project: Appearance

Since we got the robot's program to work last week, we spent today's class working on the appearance of the robot. We began thinking about its construction. During class there was a run to the craft store. My partner went to the craft store to get supplies and I stayed in the classroom and worked on designing picture frames in the Adobe Illustrator computer program. Below is what the Illustrator document looks like. It is like a piece of paper. On this "piece of paper" there are three picture frames and one rectangle that has the working title of the robot, Robart (a combination of the words "robot" and "art") on it.
Supplies from the craft store
Adobe Illustrator document
Here are some more pictures of our workspace and of my partner working:
Working on the robot's outside

Working

Workspace

Tuesday, November 2, 2010

Final Project: Beginnings

Today in class we began working on the appearance of the robot that creates art. I will post some sketches soon. We also continued to work on the programming. We are having trouble with different glitches. Sometimes the program works, sometimes it doesn't. It seems to be able to handle the code for switch3? (a button that you press) and switch2? (a second button that you press). It also seems to be able to handle the code for a loudness and a brightness sensor. However, it doesn't respond when both sets of info are put together in a single program.






Motion Module: Quack Machine

Busy working