Phys Comp Assignment 7: DC Motor

29 10 2007

I took my time following the schematic and consulting the data sheet for my H bridge, etc…, but, sadly, I can’t get my DC motor to work.

photo-110.jpg

I’m pretty sure that when I uploaded everything to my Arduino, the motor vibrated for a couple of seconds and then stopped. I restarted everything again to see if I could get it to work, and the LED blink code went off mid-program, which according to the notes means there was a burnout or a short.

I’ve been here for a while, so I think I’m going to take a break and see if I can figure out what went wrong with recharged eyes.

UPDATE: Realization three hours later, while washing my hands in the bathroom: I FORGOT TO CONNECT IT TO GROUND!



Phys Comp: LED mnemonic device + awesome materials find

29 10 2007

I have an atrocious memory, and been trying to figure out a mnemonic device for remembering which side of the LED is positive and which is negative for a while now. The easiest so far is that “short” has and “r” in it, and so does “ground.” But you could also think of this conversation, which throws in some terminology, too:

Person A: Are you sure the long one is called the anode?

Person B: Yes, I’m positive.

Ba-dum, ching!

- - -

BONUS: Check out this amazing programmable button, called a ScreenKey. It’s $48.95, but man it looks cool…

picture-11.png

 picture-12.png



Comm Lab Assignment 7: Flash animation

25 10 2007

I used excerpts from Scott McCloud’s Understanding Comics in my Flash animation:

On Abstraction

My only complaint here is that when I exported it to swf, the images became delayed by about ten frames, but the audio stayed the same, so the timing of my transitions was noticeably off. Since the piece pretty much depended on the timing, I went back and scooted the whole thing over to account for the difference. To give you an idea of the lag, here’s what it looked like originally: On Abstraction (with lag).



ICM Midterm

24 10 2007

For my midterm, I decided to continue working on the TwitterGrabber.

What I really wanted to do was create something called AllofMe, which would include similarly-styled RSS grabs from my blogs, del.icio.us, flickr, MySpace, etc… But I would have needed to learn inheritance and also figure out how to parse things within <item>, and it didn’t seem like that would be possible within the timeframe. In any case, the assignment was to perfect old skills, not learn new ones. So that idea’s in the back pocket for now.

For the latest version of TwitterGrabber, I wanted to grab user photos to add to my display in the same way that I had grabbed the updates and timestamp. After poking around some, I realized that Twitter hosts their photos on Amazon S3 and just points to them in a way that I couldn’t quite decode.

So I did it the old-fashioned way, and manually entered the URLs and made if statements that would load each, depending on the position of the counter variable (0 = first item in string, 1 = second, etc…). I also fixed up the timestamp a bit.

Obviously, this isn’t a scalable approach and it only works because I’ve only (manually) listed three users. Ideally, I’d be able to pull a list of anyone that I friend on Twitter and pull the photos in an equally “automatic” way, but I haven’t figured out how to do that just yet.



I’m on iStopMotion

24 10 2007

Somehow I became featured on the Boinx Software homepage for posting pictures of our stop-motion setup on Flickr.

Scott and SeungJun: you’re famous! And I guess I am, too.

The way they have it now, it sounds like Comm Lab is a program unto itself, rather than a class here at ITP. I passed this along to Peter so he or Marianne can give them more info that will hopefully straighten things out.

Here’s our video, posted at last. I bet this isn’t what Boinx pictured we’d produce. Ha. It was a lot of fun, but not as easy as it looks!

istopmotion.png



Phys Comp Midterm: The Final Product

23 10 2007

To see a complete write-up of the Physical Away Message project, including more photos and our notes from our user testing session, please visit our project website.

Group members are: Tom Gerhardt, Jen Grier and me, Heather Rasley. Details on my prototype are below…

- - -

HEATHER’S FLASHY MAGNETIC BUTTON PROTOTYPE

The inspiration

My two big issues with our initial prototype were that the connections for the switches were weak and it wasn’t at all aesthetically pleasing. If it was going to be something that people were going to wear every day, it needed to be something that they would actually want to wear every day.

My personal prototype was inspired by one idea and one object: 1) The suggestion that our device could be used in the nightlife scene. Not so much for the “taken” or “single” signals, but for the notion that this could be a more consciously fashionable object, 2) The tacky, trendy necklaces at Forever 21 (which I buy and wear). In short, I set out to pursue an option that would appeal more to women and incorporate some decorative elements.

prototype.png (photos by Tom Gerhardt)

The process

I went through a few different approaches to this prototype. After a cursory try at using normal wire, I took Mouna’s suggestion to use stranded wire instead, which is flexible. This works well, though it’s more delicate to work with, even after tinning the ends.

Mouna mentioned in her critique of our first prototype that we could do without the middle “neutral” position. After being out of commission with a cold for a few days and then seeing Tom and Jen struggle with their batteries due to the intentional short circuit of the netural position, I eliminated this from my schematic and went with a two-switch system.

For the switches, my first notion was to use clasps, but those weren’t solid enough to support a solid connection – not to mention that the clasps I chose melted when I tried to solder them. After a few days of searching, I came across magnetic buttons that were woefully expensive but great for making a connection that was solid but not too difficult to take apart. I found it impossible to solder directly to the magnets, so that too was a bit of a challenge.

I went through a couple of layouts for the switches, since it was hard to get the two bottom magnets to stay separate when the top two were connected. I ended up adding brass chains to the ends of the magnets on the bottom so they would dangle just above each other and not pull together. I added decorate brass cutouts directly on top of the top set of magnets after discovering that they were strong enough to connect with extra metal between them. For the bottom, I connected the decorative elements to the back, since these fasteners worked more with a traditional snap motion and weren’t as strong.

I chose to use a AA battery holder after observing Jen and Tom struggle with getting solid connections from theirs. However, I now regret this decision because the battery pack is so heavy and so obviously a battery pack that it detracts from the design, despite my attempt to hide it with felt and a decorative element. Also, I realized that it’s giving out far too much power for the LEDs on my circuit.

To display the LEDs, I attached one red and one green on the back and another red and green on the bottom, with a small piece of plastic backed with metal to diffuse and amplify the light. [One note here, as it’s my proudest find: the plastic circles are the sanded down tops of eyeshadow cases. I came across them at Kmart while on a strict mission to find any kind of small circular plastic/glass plate or container. For $1.99 each, they were much easier on my budget than the buttons.] I initially wrote “busy” and “free!” on these, but it wasn’t very attractive and I felt like by the time someone got close enough to read these words they would have already been invading that person’s space. So I just left them blank, for lack of ideas about a better way to signify “occupied” or “available.”
Thoughts on the final product

Aesthetics: The final product is a really kind of hideous take on the already tacky fashion of Forever 21 and the like, but I’m still proud that I at least gave it a try. My biggest qualms are, again, the battery, and the fact that it’s maybe a little too long. Also, the arrangement of the LED casings and the battery isn’t very nice. I think if they all dangled together it would look more like a normal necklace.

Construction: After using the same wire for my many iterations, the solder became weak, so my connection actually came apart in one place during user testing. This is probably also due to the fact that the stranded wire is probably a little too delicate to support the weight of my overly big battery pack and other doodads. Also, I unwisely used hot glue to attach the brass to the buttons. This too ended up being a real problem in our first user test, when our user accidentally ripped the brass covering off when attempting to undo the buttons.

Concept: I’m more of a button person than a zipper person, as far as aesthetics go, so I’m willing to sacrifice the ease of zipping something up for buttoning. However, most of the people we interviewed in the user test (more on our group page) felt that the zipper was more analogous to “opening” and “closing,” which I didn’t consider. For my personal use, I think I’d still stick with the buttons because I actually like having to think about making the connection, but I understand why others feel it doesn’t coincide well with the concept.

Conclusions: I definitely learned a lot in the process of making this product. Mainly, I learned that wearables are not at all as easy as they may appear to make. It’s a true challenge to work on a small scale with sewing and soldering and try to fit electronics in a package that someone would want to integrate with their everyday attire. I certainly didn’t meet it this time around, but I might like to try again. I’ve never constructed anything at all, whether of wood or fabric, so I’m happy I was able to complete something that at least worked for a little while. Another valuable aspect of this experience was learning where to find materials around town – and how easily the little things can add up.



Phys Comp Assignment 8: Brainstorming + DC motor lab (from week 7)

23 10 2007

Week 8:

  • Assignment:
    • Lab: Controlling a motor
  • Reading:
    • Physical Computing chapter 12


Comm Lab Assignment 6: Animation

18 10 2007

Our latest assignment in Comm Lab was to do an animation using iStopMotion. Scott and SeungJun were my partners. Our only plan at the beginning was to bring lots and lots of Play-Doh. Eventually it turned into a love story between two colored balls that was rather inexplicably interrupted by a yellow plastic dolphin and his pals.

It ended up being a two-day process, of about three hours each day. You can see the break between the two sessions when the lighting changes, though luckily that’s really the only giveaway that something changed.

Movie file forthcoming. The pictures of our process (on the first day) are here.

claymation.png



Comm Lab Assignment 6: Understanding Comics

18 10 2007

As a fan of comics both online and off, I was delighted to discover that Understanding Comics was required reading for CommLab. So excited, in fact, that I read it two weeks ahead of time — though that was partly due to my love-hate relationship with the Internet (more on that here).

As someone who’s drawn her own stick figure masterpieces over the years, it was comforting to hear that abstraction requires greater levels of perception and are therefore more relateable (pg. 49). I guess I already knew this — and a lot of other concepts in this book — from art history and my own experiences, but McCloud is so meticulous and convincing in his explanations that even familiar material becomes newly poignant.

I also appreciate that McCloud opened up the cartoonist’s bag of tricks and defined every one of them for us. Transitions, panel shapes and an endless number of icons and motion indicators all have meaning, which McCloud neatly outlines and demonstrates. Again, it’s something that I could guess after observing many different forms of comics, but I can save time (and brain cells) with McCloud’s help. Which I guess is what every good expert does: save us from having to perform years of our own research.

And, of course, it was simultaneously heartening and disheartening to read the final chapter, in which McCloud basically sets forth a model for becoming a skilled and informed artist (pg. 170). Heartening because, hey, there’s a path! And there are only six steps! Disheartening because those six steps don’t — and can’t — happen in 30 days or less. In fact, as he demonstrates, some artists never manage to go beyond three. But there is some hope that with had work and persaverence, you can fully understand and accomplish what it is you’re trying to do. Or die trying.



ICM Assignment 7: Midterm

18 10 2007

Week 7 Midterm Workshop

  • Try to find a nice scope for everyone’s midterm project.
  • Describe your project completely in English
  • Break your project down into steps. Algorithm.
  • Thin your project down to the simplest thing that can proove the concept.
  • Convert your algorithm into psuedo code
  • Covert your psuedo code into code.
  • Get rid of syntax errors.
  • Get ride of runtime errors.
  • Refer back to your algorithm and get rid of errors in your process.
  • Assignment: Do a project that solidifies some of the concepts that we have covered and perhaps takes another step.