Posts Tagged ‘network’

it’s real (time) !

Wednesday, November 4th, 2009

all eventsafter a couple of late nights, i have a proof-of-concept in the real-time cycling-related datalogging. the reasons behind the project are still getting sorted, but lately my interest in ubiquitous urban sensor networks has been piqued and this is a tentative exploration in that area. sensors don’t have to remain static as part of physical infrastructure…millions of people are carrying millions of sensors around with them daily. (more…)

1-2-10: Sensors

Monday, April 20th, 2009

bed-sensor

Brainstorming some sensors and possible applications. Two quick examples. Wake-up Coffee and Deflation.

There are several habitual activities that I do upon waking up, regardless of what time that ends up being. One of them is to make some coffee. Many coffee makers have timer features, but my preferred device, a single-serving espresso maker does not. Even if it did, I don’t always get up at the same time every day, so I’d have to reset the timer each time. (more…)

Spatial Media: TrafficFlow Implementation

Thursday, February 19th, 2009

tf_system_diagram1The TrafficFlow project has changed due to comments received during the first critique.

The table is circular with a smooth surface. User places an internet connected device on the table (mobile phone, PDA, laptop). After visiting the project’s website with the device and performing a brief initialization, particles representing internet traffic emanate from the device and begin to swarm off to the center of the table, where they become obscured in “the cloud”. As data flows into and out from the device, particles will flow between the cloud and the device. The movement of the particles will follow some type of fluid dynamics, tracking gracefully as the user moves their device. As the device is lifted from the table, the flow will cease.

Each particle represents packets of TCP/IP data. The particles will be color-coded by data type (web, e-mail, ftp, torrent, tcp overhead) and may be strung together to indicate groups of related packets in a data stream.

Methods:
Blob / Edge detection for devices on the table.
Packet Sniffing (Carnivore / libpcap) to watch network traffic / power visualization
Ajax web application to register users (associate IP with physical footprint of device)

System Diagram:
particle system visualization
projector (spec. TBD)
projection surface (allowing for rear projection)
camera with IR emitter (location of emitter TBD)
sensing (IR, WiFi traffic)

Procedural Direction:
1. user joins our public network
*. user places device on surface
*. user instructed to visit initialization site
4. site asks user to hit the connect button
5. site recognized users IP / UserAgent string
6. visual confirmation, ensuring the correct device is correlated with the IP
7. association is made
8. start sniffing packets
a. read packet header
b. determine source, destination, data type (as inferred by port number)
c. pass this data to visualization in the form of parameters
9. begin visualization
10. if blob of associated device is lost, the ajax interface asks the user if they wish to reconnect

Points of Failure:
- confusion for those connected to the internet via mobile data service (GPRS, Edge, 3G)
- simultaneous user logo
- inability to maintain tracking of devices

Spatial Media: Traffic Flow

Thursday, February 12th, 2009

puckTangible interface for exploring local network traffic.

The installation will be been designed to visualize the flow of information within a local area network. The goal is to make visible the invisible layer of information that comprises our information infrastructure which generally flows beneath a general level of awareness. (more…)