|
Doria Fan doria[at]nyu[dot]edu
|
Networked Objects
|
||
|
|
Final Project Documentation: Networked Flowers Please go to this link for more info.
Figured out logic to get Jason's Making Things module (substitute for xport, that allows for an easier flash interface to code communication between devices) speaking to our circuit. Tested it with a simple circuit, and got Mauricio's device communicating. When we hooked it up to the crazy heep of wires and LEds that is my circuit, it won't work. There's not enough power to supply all these LEDs. We'll just dummy this using switches for now. Need to solve power issues. Mockup for what the web interface should look like is up: here. I'll document more after I get some rest. Stuff on final scenario, sketch 1 & sketch 2 of stuff I've having laser cut. Testing out some very, very basic shapes to see what the laser cutter is capable of, and how light plays off of the plex. I'll refine the shapes if this comes out okay. other sketches and models also exist.
Networked Bouqet/Digital Flowers: emotional communication device. Below is cut & paste from an email I sent Tom describing the project (since I can't be faffed to rewrite this): Description:
Location/Identification Hmm...makes me think of (stream of conscious here) about issues with geopolitics, world affairs, national security, our right to privacy, bill of rights, surveillance, and how this technology is (ab)used. It makes me think of the case of libraries being pressed to send the gov't library records. A lot of these technologies were originally made for manufacturing/business purposes, but end up being repurposed. A lot of information technology weighs convenience and other benefits with our right to privacy. It always seems like a Faustian bargain. GPS stuff -- I used to play in the streets of Taiwan with the neighborhood kids at age 4. No gps tracker needed. I will be very sad if I have to give my kid's one of these gadgest. I had to carry a pager for work, back in 1995-6, my dad called it, appropriately, an electronic leash. GPS for outdoors-y people -- I'm all for it, as long as they still have mastered the basic Boy Scout skills, how to read a map, common sense, etc. Otherwise, if the device malfunctions, you're screwed.. Week ? SmartHome:Some of this stuff looks like the stuff showcased in the homes on MTV's The Crib (or whatever its called -- tacky homes of nouveau riche celebrities who lack good taste and judgment, and fill their homes with gadgets.) The electric tea kettle -- I miss my electric kettle I had in England. We also had these Warmrails - AMEN. So simple, but I tell you, a godsend. You'd have a warm towel and warm underwear (it's like always wearing clothing out of the dryer), which in the middle of winter, should not be underrated. Makes me think of the gorgeous radiator I saw in the paper a few months ago by a Dutch designer, part of the Droog Collective: http://www.jorislaarman.com/. (click on "reinventing functionality".) This thing is gorgeous, and takes a necessary nuissance (the ugly radiator in the housefhold) & ubiquitous product and transforms it into this gorgeous thing. The Dutch design sensibility-- smart, witty, and quirky. I currently do not have enough time or energy to write
in coherently, so I'm just going to spit out some notes here: Week 5 Ping Pong. It worked fairly smoothly. But an occasional
bug when you've lost the game. First time, Amit and I hooked up our Xports,
I think we were both in AutoConnect mode (D5), and we were able to connect
without a problem. However, in this case, we were in C4 & C5 mode,
and Amit wrote our own handshake/autoconnect protocol. Pic
code and flow
chart. Amti can probably write this in his sleep, but It takes me
a bit for me to wrap my head around all the game logic. Here's the important
part of this exercise -- figuring out the protocol to getting the 2 xports
to communicate, so it knows when to transmit and when to receive, and
what to do with the info. Since serin is a "block out' function",
we use the "WAIT" command, so the pic will continue running
a subroutine until it receives the piece of info it's waiting for.Also,
it's smarter to send all the data in one array/one piece of data, than
as multiple chunks.
Week
4 A lot of networked, interactive projects seem to be about bridging time/space, and facilitating propinquity, when people can't be in the same space at the same time. Now that we can do networked computing that is location sensitive, there's an amazing potential for interesting work (like some of the readings). I love maps and the visual display of information, so it's hard for me to take to them when they're reduced to tiny real estate on a PDA or cellphone. Granted, that is the challenge of making this stuff. When dealing with location-based work, I still prefer a more physical display of information. I really like the work of Local Projects, particularly the Memory Maps and City of Memory. I realize this is like comparing apples and oranges -- these "location/mapping" related projects are completely different in purpose and context. Back to location-aware computing and space annotation...the one project in our reading I didn't take to was the SonicCity. "It enables users to create a real-time personal soundscape of electronic music by walking through and interacting with urban environments. " Everytime you walk in a city, you get your own, unique personal landscape based on your interaction/reaction with the urban environment, as well as the ambience of your surrounds, which are specific to that time and place. I'm fairly sensitive to the sounds around me, and it shapes my experience there. The SonicCity thing doesn't do it for me. It's augmenting and artificially changing the aural experience.
Week
3 Xport is up and running. Got the Xport and PIC communicating.
Figured out how to configure Xport to autoconnect to a specific IP address.
Paired with Amit for the PingPong project. He comes up with the idea of
something along the lines of "Simon Says" using push button/switches
and LEDs. I built a circuit of a bunches of switches and LEDs to get back
used to wiring up a circuit, and mapped out flow chart for how the logic
would work, and have the framework for this code. Amit's written a program
in Processing that can check for communication between the Xport and computer,
that we can use to debug the Xport. Right now, it will print to screen
which LEDs we send out. He programmed a chip with some basic logic, built
out a circuit with LEDS&switches which I've mirrored, and we have
the 2 boards (Xports and chips) successfully communicating using his PIC
code. I've taken a look at his PIC code and logic. We came up with different
protocol/system for establishing communication. I'm going to flush out
the PIC code to reflect the correct physical setup (chip, ports, # of
switches & LEDs) and clean up the logicof the game a little.
Week
2 Readings: Writing (Equator & Disappearing Computer Initiative) on stuff like this (interaction design and research, physical and digital, etc.) seems to use the the following words a lot: "seamless", "blur", "disappear," "divide,", "integrate," and "smart." Good resources to see what kind of work other people are working on, and inevitably, there will be overlap with interests here at ITP, but those sites are a bit unwieldy to navigate. Other 2 articles --Greenberg/Kuzuoka: their protoypes of "surrogate" and"active hydra" provided some comic relief while waiting for the Q. Virtually living together -- I'm not sure when this article was written, but the methodology they write about seems to be be fairly standard practice in the design discipline. Although, they made some good observations about the way families, I'm not convinced their prototypes addressed those issues very well. Overall, some good food for thought. Xport: Got it up and running. Amazing how much information from last semester I have not retained. But good to get back to it. Maybe by the end of my 2 years here, I will finally learn how to properly read a circuit diagram/schematic. Working with electronics is a pain because they're at such a small scale, so sometimes it's hard for me to catch some glitches-- I should get a magnifying glass or those granny reading glasses. Here are some thoughts and observations from being back in the lab the last few day 1) I've completely lost the level of patience, which isn't very high, to actually read through material thoroughly, which would make life a little easier. I'm not sure if it's because I haven't been in an academic environment for a while, or if it's because I've become acclimated to flashes and blurbs. 2) I've been fascinated by the anxiety we (ITP students, myself included) seem to have about physical computing, or technical material in general.
Week 1 I'm always a bit wow'ed when I see the dates(1996!) that these articles were written. (When they're on, the prescience is uncanny, when they're off, it's highly entertaining.) Almost a decade later, we still can't get our shit together to make things desirable or useable, or better yet desirable and usable. Granted, not everything is meant to be "useable" in the sense of product. But, the art or pieces of provocation or contemplation should leave me more than that feeling of "so what." They should do something for someone, not necessarily me, aside from just the creator. I hadn't heard the term "calm technology" before -- it's an interesting and odd expression. We've developed a lot of technology to glean and process information. What's more interesting and important to me, is seeing it used in a meaningful way. What is "meaningful" is certainly debatable -- and it usually comes down to intent and user. There's a lot of real estate for us to work in between the goofy Spencer for Gifts or more "high" end Sharper Image gimmicks and all those dry products that the Silicon Valley seems to pump out, that's had their soul sucked dry by the usability folks. It's interesting for me to hear folks at ITP, or designers in general, engage in all these cultural theory discussions, although the work we produce doesn't seem to reflect our respective mantras. Classic case of easier said then done.In our defense, when you really start trying to work through all the issues, they can be very hard to resolve elegantly. Back to the idea of information overload that this
article addresses....and ubiquitous computing. Sometimes I think as designers
and technologists, we underestimate the user, or fall in love with the
technology for technology's sake.( We also tend to be narcissists -- we
want our creations front and center, whether or not they belong there.)
Humans are capable of processing a lot of info -- it's a matter of whether
or not we want to or need to, and when and where. I keep thinking about
other complex and "hi-tech" products, such as cars and medical
devices, though they may not be great comparisons. I revert to cars, because
I worked for an automobile manufacturer. The basic technology of the car
has not changed in almost a century -- internal combustion engine.There've
been many, many advances and cars have become far more technologically
complex. Cars are also a product, though technologically complex, that
really plays to human emotions, and has a complex place in our culture
and identity. Basically, a car needs to get you from point A to B in one
piece. Safety trumps emotion and comfort. There is a lot of peripheral
infomation on your dashboard, and also within arm's reach. Each piece
of info is there for you to access when you need or want it. The technology
of each component (seat-warmer, stereo, GPS, power windows just to name
a few) is invisible to you until it breaks and you see what the mechanic's
bill is for it. All these peripherals are great, but they are irrelevant,
if you can't do the main task -- get from point A to B in one piece, safely.
I don't think it's a question of whether we as users are capable of handling
all the info. It's an issue of providing us with what we want when we
want it. Things are going to get more complex, and we adapt and filter
out what we don't need, and use what we do. We all have choices. With
any technology, be it ubiquitous computing, there's always the potential
for it to be used thoughtfully and intelligently, and a lot of room for
idiocy. (There are a lot of ass-ugly, unreliable cars out there.) |