physical computing - university of washingtondepts.washington.edu/dmgmedia/memorybox.pdfphysical...

21
physical computing fall 2001 ken camarata julia cole don craig ned frisk todd smith mike weller

Upload: others

Post on 26-Jun-2020

0 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: physical computing - University of Washingtondepts.washington.edu/dmgmedia/memorybox.pdfPhysical Computing Winter ‘02 SLN 8963 This class will design and build an object that will

physical computingfall 2001

ken camarata

julia coledon craigned frisk

todd smithmike weller

Page 2: physical computing - University of Washingtondepts.washington.edu/dmgmedia/memorybox.pdfPhysical Computing Winter ‘02 SLN 8963 This class will design and build an object that will

ARCH 498Z

merging the physical and the virtual

through time the powers of computation will be embedded into our physicalsurroundings. we need to explore and understand the relationship.

memorybox

beginning with the work of theAmerican Artist Joseph Cornell and theValise of Marcel Duchamp as "containersof the memory of experience", make theboxes autobiographical. Case studies.Focus on duration and memory.

box

This class will design and build an object that will becomputationally enhanced as a means of exploring therelationship between the physical environment and thepowers of computation. In order to accomplish thisgoal students will learn about programming, sensors,circuit design, and the art of making. Although noprior experience is required, dedication, enthusiasm,and creativity are essential.

architecture hall room 049 (digital seminar room)wednesday 6:00pm - 8:50pm

credit/ no credit

fall ‘01 SLN XXXX [email protected]

memory

Physical Computing

-Ken Camarata

Page 3: physical computing - University of Washingtondepts.washington.edu/dmgmedia/memorybox.pdfPhysical Computing Winter ‘02 SLN 8963 This class will design and build an object that will

Phys

ical

Com

putin

g 49

8z F

all ‘

01

Mem

ory

Bo

xW

orki

ng w

ith th

e id

ea “

Tra

ces

of M

emor

y”, t

he m

ultid

isci

plin

ary

grou

p de

sign

edan

d bu

ilt tw

o ph

ysic

al in

put d

evic

es a

s w

ell a

s an

out

put d

evic

e th

at li

tera

llytr

aces

a p

erso

n’s

inte

ract

ions

.

The

res

ult i

s a

fun

and

com

pelli

ng r

elat

ions

hip

betw

een

the

phys

ical

obj

ects

and

the

mic

roco

mpu

ters

that

driv

e it.

Julia

Cole

- C

era

mic

Sculp

ture

Don C

raig

- M

usic

Com

positio

nN

ed F

risk -

Photo

gra

phy

Todd S

mith -

Arc

hitectu

reM

ichael W

elle

r - A

rchitectu

re

Inst

ruct

or -

Ken

Cam

arat

a

Join

us

next

qua

rter

!Ph

ysic

al C

ompu

ting

Win

ter

‘02

SL

N 8

963

Thi

s cl

ass

will

des

ign

and

build

an

obje

ct th

at w

ill b

eco

mpu

tatio

nally

enh

ance

d as

a m

eans

of

expl

orin

g th

e re

latio

nshi

pbe

twee

n th

e ph

ysic

al e

nvir

onm

ent a

nd th

e po

wer

s of

com

puta

tion.

In o

rder

to a

ccom

plis

h th

is g

oal,

stud

ents

will

lear

n ab

out

prog

ram

min

g, s

enso

rs, c

ircu

it de

sign

, and

the

art o

f m

akin

g.A

lthou

gh n

o pr

ior

expe

rien

ce is

req

uire

d, d

edic

atio

n, e

nthu

sias

m,

and

crea

tivity

are

ess

entia

l.

Page 4: physical computing - University of Washingtondepts.washington.edu/dmgmedia/memorybox.pdfPhysical Computing Winter ‘02 SLN 8963 This class will design and build an object that will

Documentation

Each student was asked to submit documentation for the project. The documentation notonly needed to address their individual contributions to the project but also answer thefollowing questions.

1 What kind of feedback did you receive about the project?2 Did people interact with it the way that you had intended?3 What would you change?4 What stands out as a success?

The following set of pages are their responses.

Page 5: physical computing - University of Washingtondepts.washington.edu/dmgmedia/memorybox.pdfPhysical Computing Winter ‘02 SLN 8963 This class will design and build an object that will

Memory Box – Julia Cole

Tubular Maze

Description:The tubular maze was the solution to a design problem that called for an objectwith which a user would freely and actively interact. Since the object wouldhouse tilt sensors, the activation of which would ultimately drive the outputdevices, we wanted to achieve as full a range of movement as possible. We alsofelt confident that the perception that the object was a game would counteractany intimidation that might hold people back from physical participation.

The maze was built as a hollow tube, with a twisting path that covered theentire outer surface. The original was modeled in paper clay (clay with paperfibers added to increase the strength of the material before firing), and asinuous groove was carved into the surface. Smooth walls were built on eitherside of the groove to form a channel that would contain the ball, as well asprovide both visual and tactile pleasure to the user. Beginning and end pointswere carved at either end of the tube to provide an objective for the player,and dead ends and loops were added to maximize active movement.

When the clay was dry, it was sealed with a mixture of Vaseline and mineralspirits and a form was built to stabilize the model and enable a hollow castingto be made. A mold was then made using silicone RTV (tin cure), which waschosen because of its flexibility and ability to faithfully capture detail.This eliminated problems of undercuts that would have occurred in attempting tocast such an intricate pattern on a cylindrical form. A plaster mother mold wasthen built around the outside of the silicone to hold it in place duringcasting, the original was removed and the mold reassembled.

A casting was then made using Aqua Resin. A slush coat was used to capturesurface detail, and then the structure was reinforced with fiberglass choppedstrand mat lamination. The two stages of curing that occur with Aqua Resinallow for tooling, seam chasing, repairs of imperfections, and wet sanding inthe first hours after the casting is removed from the mold. The casting wasthen sprayed with a matte latex paint.

Several solutions were tried to keep the ball on the surface of the maze as itwas rotated through 360 degrees. The original plan to cover the channel withclear plastic tubing was abandoned because the material was too difficult towork with. Several different types of mesh covering were then investigated, tofind one that would not impede movement of the ball. It was also important toprovide an aesthetically pleasing finish that would not detract from thephysicality of the maze surface. The final choice was a silky sheer nylon sockthat fit the tube perfectly.

Page 6: physical computing - University of Washingtondepts.washington.edu/dmgmedia/memorybox.pdfPhysical Computing Winter ‘02 SLN 8963 This class will design and build an object that will

A final detail was to provide the user with a reward for persevering with themaze. Since the ball to be used was a steel ball bearing, a small set ofcontact pins was drilled into the pocket at each end of the maze channel. Thepins were then hooked up to small flashlight assemblies that were inserted intotextured plastic balls, which in turn were inserted into the open ends of thetubular maze. The balls provided a closure to the ends of the tube, effectivelyconcealing the sensor mechanisms hidden inside, and had the added delight of(usually) lighting up when the ball finally landed in the terminal pocket. Thedesign of this detail could definitely have been improved upon with a littlemore time.

It had been hoped that the sensors in the maze would be able to be connected tothe Handyboard with a radio frequency device taken from a remote control car,so that there would be no wires to impede movement. Unfortunately this was notpossible within the time frame available because there were unforeseencomplications with the number of channels required. Nevertheless, the mazefunctioned extremely well as an input device during the presentation. As hoped,there was no hesitation at all to pick up the maze and interact with it.Participants were in fact extremely active and playful, and quickly made thetransition from traversing the pathways of the maze to using the whole objectas a means to influence the output device and effectively make a drawing(jiggling the tube, jumping up and down with it, etc.).

Project Critique:Although the input/output connection worked well as a functional device, mostor all of the original impetus to design a memory box was lost in thepresentation. The original idea was to have participants create a trace thatthey would leave as a record of their presence, in much the same way thatmembers of human societies leave stories behind as a collective culturalmemory. To heighten the analogy, we wanted to reference the fact that as eachof our stories is added to the collection it supplements, displaces and evenerases others. In the same way, the line created as a result of interactionwith the maze develops increasing levels of complexity over time and begins toobscure idiosyncratic traces. The unit did in fact perform in this way, but theconnection between the actions of users and the core idea could have beenstrengthened through the addition of text or images to the structure that wouldhave referred (however tangentially) to the process. It would also have !been interesting to investigate other means by which a trace could be left ^÷especially intriguing is the idea that a substance like starch or hot wax wouldleave a three-dimensional record.

It was also a relevant design feature that the user would stand on the side ofthe display that only revealed their participation in the overall patternthrough a window cut into the back board. This was intended to reflect the waythat we may only have fleeting or incomplete understanding of how we

Page 7: physical computing - University of Washingtondepts.washington.edu/dmgmedia/memorybox.pdfPhysical Computing Winter ‘02 SLN 8963 This class will design and build an object that will

participate as individuals in a collective memory. Because the maze wasattached to the output device with a long wire that went around the outside ofthe display stand, users were able to circumvent this intention by walkingaround to the other side and viewing the whole process. Although this couldhave been controlled by shortening the wires or passing them through a hole inthe back board, the problem would have not have been solved this way had webeen able to make the radio frequency signal work. This suggests that thedesign of the display stand could be slightly reworked to consider thisfeature, although perhaps if the conceptual connections had been stronger thefree movement of the participant from one side to the other may have been an asset.

Page 8: physical computing - University of Washingtondepts.washington.edu/dmgmedia/memorybox.pdfPhysical Computing Winter ‘02 SLN 8963 This class will design and build an object that will

Documentation for “Traces of Memory’Donald Craig

The project “Traces of Memory” is about the changes that are paved by themovement of objects in space. It can be considered an analog to the traces of memory leftby our own thoughts and perceptions. Physically, the project is a large wooden structurewith a desk-like area for the input objects and a moving canvas for the output display.The input devices were a soft and squishy object with bend sensors and a tubular mazewith tilt sensors. Depending on the changing attitude of the maze in space as a personattempted to solve the maze, motors driving the canvas would go forward or back and afelt tip pen would write on the canvas as it moved. Thus, an inscription or trace of themaze’s movement would be recorded.

People generally enjoyed playing with project, although I am not sure theconceptual analog of the ink traces on the canvas to memory traces was very clear. Thatseemed elusive to people I spoke with. Some people enjoyed the maze as a maze andothers only in so far as it manipulated the actions of the display, ignoring the maze itself.Once it became obvious that you could go around the back of the object and watch themechanism while playing with the maze, this is what everybody did.

I think the whole output display mechanism was very successful. I really like thelow tech impression created by the wooden wheels on wooden axles. With the slantedsurface, I can’t help but think of medieval siege engines (catapults, or trebuchets). I thinkthe maze was also very successful as an input device.

The sensors inside the tubular maze were a set of three tilt sensors. Two of themwere used to get a rotational position and the other an attitudinal position. This last onewas a simple on/off switch. The other one was more complicated. On the tilt sensor usedfor this, there are a group of five contacts, two of which complete a circuit as the sensor isrotated.

Here is s side view of the sensor and the contacts:

3

4 2

5 1

Each of these contacts was wired into a resistance network. The overall resistanceof the network changed according to which set of contacts were closed. Two differentvalues of resistor were used either singly or in pairs to get a total of four different valuesplus no resistance. The circuit diagram looks like this:

Page 9: physical computing - University of Washingtondepts.washington.edu/dmgmedia/memorybox.pdfPhysical Computing Winter ‘02 SLN 8963 This class will design and build an object that will

sensor contact 1

25 K contact 2

20 K

contact 3

15 K contact 4

10 K contact 5

sensor

The total resistance of the network is 70 K. If a set of contacts is closed, that resistance isremoved from the network. For instance, if 2 and 3 are closed, 20 K is subtracted fromthe 70 K to give a total of 50 K. The different resistance values that are possible are 0 K,45 K, 50 K, 55 K, and 60 K. These different values correspond to five different rotationalpositions of the maze.

Unfortunately, it is possible that when the device is tilted, none of the contactswill be closed. So another rotational sensor was used and wired into the same resistancenetwork. This sensor was wired oppositely the first one. This way, not matter how thedevice was tilted, the same rotational value was returned.

The idea as far as these value being converted into motor controls was that therotational value would be used for the speed and direction of the canvas and the tilt wouldbe for the back and forth of the pen. Continued rotation in one direction would cause themotor to go faster and changing the direction of rotation would change the direction ofthe canvas. I don’t believe the changing motor speed portion of this actually worked inany noticeable way.

The code used in the handyboard for the rotational sensor is here include here:

int sensor_position = 0;int position_difference = 0;int last_position = 0;int sensor_value = 0;int counter = 0;

int x_motor_speed () {

return ( ( maze_motor_speed() + squishy_bend_speed() ) / 2 );

}

int get_maze_position () {

if( analog(0) < 100 ) {

return 0;

Page 10: physical computing - University of Washingtondepts.washington.edu/dmgmedia/memorybox.pdfPhysical Computing Winter ‘02 SLN 8963 This class will design and build an object that will

if( analog(0) >= 100 ) {if (analog(0) < 130) {

return 1;

}}

if( analog(0) >= 130 ) {if (analog(0) < 135) {

return 2;

}}if( analog(0) >= 135 ) {

if (analog(0) < 140) {

return 3;

}}if( analog(0) >= 140 ) {

if (analog(0) < 150) {

return 4;

}}

if( analog(0) >= 150 ) {if (analog(0) <= 255) {

return 255;

}}}

int maze_motor_speed () {

sensor_position = get_maze_position();

if(sensor_position != 255){position_difference = sensor_position - last_position;last_position = sensor_position;}

if(position_difference >= 1) {counter = counter + 1;}

if(position_difference <= -1) {counter = counter - 1;}

if(counter >= 3) {counter=3;

}

if(counter <= -3) {counter=-3;}

return counter;

}

Page 11: physical computing - University of Washingtondepts.washington.edu/dmgmedia/memorybox.pdfPhysical Computing Winter ‘02 SLN 8963 This class will design and build an object that will

The other device was a soft and squishy device that had three bend sensors in it.The code for that simply averaged the values from the bend sensors. This code wasinclude in the same handyboard as that above. Here it is:

For the other handyboard, there was the tilt sensor from the maze and a pressuresensor in the soft object. The code for both of these was altered in the final testing of theproject. So this code is not exactly what was actually used. Here is the code for thesecond board:

int squishy_average_sensors () {

return (analog(0) + analog(1) + analog(3))/3;

}

int squishy_bend_speed () {

int sensor_value = squishy_average_sensors();

if (sensor_value >= 70) {if(sensor_value < 90){

return -2;

}}if (sensor_value >= 90) {

if(sensor_value < 105){

return -1;

}}if (sensor_value >= 105) {

if(sensor_value <= 115){

return 0;

}}if (sensor_value >= 115) {

if(sensor_value <= 130){

return 1;

}}if (sensor_value >= 130) {

if(sensor_value <= 150){

return 2;

}}

}

Page 12: physical computing - University of Washingtondepts.washington.edu/dmgmedia/memorybox.pdfPhysical Computing Winter ‘02 SLN 8963 This class will design and build an object that will

int y_motor_speed () {

return tilt_sensor_speed() + pressure_sensor_speed();

}

int pressure_sensor_speed () {

if(analog(6) >= 235) {if(analog(6) < 245) {

return -1;}}

if(analog(6) >= 245) {if(analog(6) < 250) {

return 0;}}

if(analog(6) >= 250) {

return 1;

}

}

int tilt_sensor_speed () {

if(analog(0) < 70) {

return -1;}

if(analog(0) < 250) {

return 1;

}{

return 0;

}

}

Page 13: physical computing - University of Washingtondepts.washington.edu/dmgmedia/memorybox.pdfPhysical Computing Winter ‘02 SLN 8963 This class will design and build an object that will

Traces of Memory – Ned Frisk

Project Description:

Our project was to create a “memory box.” The final result is a loose interpretation ofthis idea. What we created was a memory box in the sense that it records memories andkeeps them for viewing later. The device is made up of three parts; the frame, the input,and the output. Following is a summary of each part.

The Frame was made out of wood. Its purpose was to support the input and outputdevices. The design was intended so that the user interacting with the input deviceswould only be able to see the traces of what was already recorded and not what they weredoing in the present.

The input sat on one side of the frame and consisted of two toy like objects. One was atubular maze; the other was a soft, squishy, bendy object. Each toy had sensors in it andas the user interacted with it the sensors would send information about its movement tohandy boards which translated the information and relayed it to the output device.

The output device was a plotter that worked off the same principals as other basic x, yplotters. After the information was sent from the input devices to the handy boards, itwas translated into x and y movements for the plotter. The plotter then took theinformation and drew lines on a canvas; recording how the user was interacting with thetoys.

Feed Back:

The feed back was overall, very positive. Everyone seemed to be intrigued by it &enjoyed playing with it. They also seemed to be stimulated by the ideas and conceptsthat went into its construction. Some words that were overheard: cool, neat, impressive,etc…. A lot of people mentioned that they would like to see the input be wireless.

People would try to draw with it. At first everything worked like it was supposed to.Eventually people realized they could carry the input around to the output side and watchhow the plotter moved as they moved the maze. They started to learn how to control itand did that instead of interacting with they input as just a toy or object.

As far as changes are concerned, it would probably be more effective if the input waswireless and if the users were actually confined to the area where the input actually sat.Extra time for testing and bugs would be a good idea.

Successes? We made it and it worked. Everything we did needed to be a success or itwouldn’t have all worked as well as it did. It is probably attributed to everyone workingtogether as well as we did.

Page 14: physical computing - University of Washingtondepts.washington.edu/dmgmedia/memorybox.pdfPhysical Computing Winter ‘02 SLN 8963 This class will design and build an object that will

Soft & Squishy:

It was, as the name implies a soft and squishy blob with three sort of bulb like armsbranching off it. The object was covered with sparkly white spandex. Inside it were askeleton made of soft bendable wire, three bend sensors (one in each arm), and a pressuresensor (in one of the arms). When interacting with it, the user squeezes it and bends it.The wire in it holds its shape until it’s bent differently. As it gets bent and squeezed, thesensors send their information to the handyboards, which interpret it for the output.

The object needed to be designed so that people would feel compelled enough to pick itup and play with it. It also had to work different then the maze. Another considerationwas that it needed be made within the given time frame.

There were problems with the design. The sharp ends of the wires stared poking throughthe material. As the object was bent around, the wires would bunch up in the center of it.The biggest problem was that the cover ripped putting it on, so there was no time to haveit hooked up in time for any testing or code.

The sensors would give send the handyboard different resistance values based on howmuch they were bent or squeezed. That information gets translated to motor directionand speed and sent to the output. In the case of the three bend sensors the values wereaveraged in the code to give the single value needed.

As far as changes are concerned, I would have capped off the wires so that they didn’tpoke through and found a good solution to keep the wire from bunching up. I also wouldhave designed it so the cover wasn’t so hard to make and put on. It should have beenfinished sooner so it could be connected and tested.

People and the presentation were interested enough in it to pick it up and play with it.They seemed to enjoy its feel and malleability, but some were a little uncomfortableplaying with it because its shape was mildly suggestive. Overall they agreed that itserved its purpose quite well.

Page 15: physical computing - University of Washingtondepts.washington.edu/dmgmedia/memorybox.pdfPhysical Computing Winter ‘02 SLN 8963 This class will design and build an object that will

Todd Smith / Mike WellerArch 498zInstructor: Ken Camarata12/18/01

Display Documentation

“project description”

The project revolved around the idea of traces of memory. The result is manifested as a medievalmachine of sorts, an archaic version of an x/y plotter, which maps the manipulation of a twotoys, a maze and a stress squishy.

Sensors in the toys send signals which are relayed to two stepper motors. One motor moves thedrawing surface, a large canvas belt stretched vertically between two rollers, up and down. Theother motor turns a smaller canvas belt, with a sharpie marker attached to it, causing a line to bedrawn across the larger canvas. While a person manipulates the toys connected to themechanism, sensor data retrieved from embedded tilt, bend and pressure sensors is translated bya handiboard computer and relayed to produce movement in the stepper motors. Each person’sinteraction with the toys create different lines, ranging from straight to circular. The personmanipulating the object sees the past traces of movements through a cut in the display face thatreveals a portion of the canvas..

“what kind of feedback did you receive about the project?”

The majority of the feedback received from the project was particularly great. While working inthe shop, Todd did a lot of explaining as to what we were doing. The major vein of interest wasdirected towards the “machine” being made out of wood and very simply, yet powereddigitally/electrically. Commentators particularly noted the irony in such a construction, yetenjoyed it. Feedback at the presentation was minimal. People interacting with the machine werekind of astonished at the project, trying to figure it out, ending up at an eventual “that’s prettycool,” yet not knowing what the hell they were looking at.

“did people interact with it the way that you intended?”

People generally interacted the way we intended. Some people cheated and walked around to thedisplay side so that they could immediately see the effects of their manipulations.

“what would you change?”

Todd would change the relative ambiguity of the subject. Putting specific initial requirementswithin the project statement, and reconsidering the time needed to come up with a project couldhelp.

“what stands out as a success?”

Page 16: physical computing - University of Washingtondepts.washington.edu/dmgmedia/memorybox.pdfPhysical Computing Winter ‘02 SLN 8963 This class will design and build an object that will

The most successful and beautiful thing about the whole project revolved around the fact thatcross disciplinary study does work, and creates unique possibilities, otherwise unattainablewithout the joining of different minds. Also, the completion of such a bizarre concept lies as thebiggest accomplishment.

“tell me about making the display.”

“description”

Mike came up with a design for a standing display that could be constructed out of two pieces ofplywood, interlocking via slotted construction. This would lessen the need for mechanicalconnections and later play a large part in governing our decision for a simple connectionlanguage throughout the whole x/y mechanism. The display not only acts as a resting spot forthe two constructed objects, but also a housing unit for the entire mechanisms that control themovement of the pen and canvas. The display looked like a giant easel of sorts, allowing forsomeone standing in front of it to look through a cut section to the canvas being drawn upon.

“design decisions”

Design decisions were we made on tri-weekly basis. We would get together 3 times a week overcoffee and sketch out ideas confirming between the both of us, the fate of the display.Eventually the design got carried out into the shop to be constructed in a 3 hour period duringclass, just roughly.

“tell me about the XY table”

“description”

The XY table acted as a means to transpose the movements of simple objects into a drawnrepresentation on canvas. The x movement of the table consisted of a pen mechanism poweredby a small stepper motor. The pen was attached to a 2 in wide canvas that rolled on 4 in” indiameter wheels clock, or counter clockwise. This movement was complimented by theperpendicular movement of a large 2.5’ wide canvas moving in the y direction positively up ornegatively down on 4.5 in PVC tubes with wooden dowels shoved through the middle acting asan axel. This movement was powered by a larger stepper motor. Both motors were obtained viaold printers, laser and dot matrix.

“design decisions”

design decisions were also made on a tri-weekly basis. Once the display was finished, the designsession went towards the XY mechanism. This eventually went into the shop, where, weconducted a little design build session totaling upwards of 40 hours in the shop. It was decidedthat the language of our whole machine had to stay within the confines of simple, and somewhatmedieval in look, character and connection. Todd did all the metal work for the brackets to holdthe motors in place on the display.

Page 17: physical computing - University of Washingtondepts.washington.edu/dmgmedia/memorybox.pdfPhysical Computing Winter ‘02 SLN 8963 This class will design and build an object that will

“unforeseen problems”

We didn’t think it was going to take as long as it did. Buying expensive materials doesn’t paybeing that time is an issue, and a refined product is not in the plans, especially when thepossibility of even getting the project done is up in the air.

“tell me about the stepper motors”

“wiring considerations”

We used six-wire stepper motors, which had two pairs of control wires each served by a powerwire. We wired the control wires into a handiboard’s four forward motor ports, and the powerwires into the respective reverse ports, with some resistors on them to keep the board fromoverheating.

“programming for them”

We fired the four motors in sequence, first turning one motor on, and then the previous motoroff, and then pausing for an interval. By adjusting the interval we could vary the speed of themotor.

“code from the display”

Page 18: physical computing - University of Washingtondepts.washington.edu/dmgmedia/memorybox.pdfPhysical Computing Winter ‘02 SLN 8963 This class will design and build an object that will

Gallery of Photographs from the Presentation

The Soft and Squishy Input Device

The Tubular Maze Input Device

Page 19: physical computing - University of Washingtondepts.washington.edu/dmgmedia/memorybox.pdfPhysical Computing Winter ‘02 SLN 8963 This class will design and build an object that will

Visitor (Dustin Eggink) interacts with the tubular maze

Visitor (Claus Seligmann)

Page 20: physical computing - University of Washingtondepts.washington.edu/dmgmedia/memorybox.pdfPhysical Computing Winter ‘02 SLN 8963 This class will design and build an object that will

The Pen Mechanism in action

The x-axis mechanism The y-axis mechanism

Page 21: physical computing - University of Washingtondepts.washington.edu/dmgmedia/memorybox.pdfPhysical Computing Winter ‘02 SLN 8963 This class will design and build an object that will

The plotter output

Detail of the top roller