Friday, December 12, 2008
final review: becker/turkula
from orifice to monster security:
jon turkula/john becker fa2008
Our project has gone down two major paths. One: interactive aperture that helps define the relation between desirable objects, people and places. this mode of investigation sought to create a physical relationship between the two spaces, such as user/ storage. The second seemingly tangential trajectory we took was the interface between two very separate groups. We chose to look at the security of a a bank vault. On fifth avenue in midtown, chase bank has an all glass facade between the public on the street and the bank vault. This shift in the idea of security was pivotal in this, the new information age. No longer guarded by a stone wall, but by glass. This project is sited to be along this glass wall as a beautiful, historical look at the relation between the public and the most sacred. Small mouth open as if to guard the space, following the pedestrians along the street. The interface allows for distant observation to be unencumbered, while when the wall is approached a warning is made.
Labels: aperature, awesome, becker, distance, monster, ping sensor, relays, turkula
Final Prototype 03
Final Prototype 02
here, we test the prototype with the FSR sensors -- one touch on the "positive" side controls one group of flexinol (keeping it open), another touch adds a second group, and a third controls all. one touch on the "negative" side wrests control of one group from the positive (keeps it closed). and so on..
Labels: touch
Final Prototype 01
here, we're testing the default state, prior to user engagement. Ambient information (in this case, small movement and hints of opening) acts to pique the curiosity of passersby and encourage them to band together to monitor what is beyond.
Labels: touch
urban sound monitor 2 from lleigha on Vimeo.
Labels: arduino, audio, booth, pd, puredata, sound, urban
we're proposing to use our working prototype as a means to explore urban social behavior in relation to sound. by using puredata, an arduino, and a flexinol actuator, we have developed a simple mechanism which reacts to sound set at various thresholds. paired with a webcam or video camera, our prototype acts essentially as a lens cover which, when triggered by sound, reveals the source of the sound and/or the public reactions to the sound. when untriggered, the prototype obscures the lens.
the sites we are proposing to install our prototype(s) are the public phones located within new york, as well as other various private/public zones found within the sidewalk zones of the city. the public phones indicate a kind of space that are rarely used for their original intent, especially in new york where they're valued more for their advertising space, yet still maintain references to communication and still occupy a substantial amount of urban space.
our prototype could be consider a kind of modular unit which parasitically could attach itself to these various public zones. as a result of this system, we're proposing three scenarios, which could produce different results.
1. a singular module as a tool to explore social behavior in reference to urban sound
2. multiple modules located within a localized zone, which could communicate with each other to produce a kind of relationship with particular events, time, and proximity.
3. modules that could communicate globally, making a connection between different cultures and different urban sound spaces.
Labels: arduino, audio, booth, pd, puredata, sound, urban
this is our first attempt at prototyping a modular unit to occupy our various locations/scenarios. the standalone unit allows the flexinol lens cover to obscure and reveal a camera based on the given sound input threshold, while the led reacts with pulse width modulation to the same sound source. the opacity of the mylar describes a location for possible video playback from other module sources, giving the unit the ability to record and capture video/sound, as well as project video/sound from other units. the low tech flexinol lens cover is revealed in a way that makes the act of recording explicit, while the variations in led intensity begin to reinforce the understanding of sound as input. the systems within the unit are contained yet don't attempt to become hidden surveillance. we're more interested in the possibility for a feedback loop with hopes that the input and playback might begin to play an interactive role with the behavior of the people passing by.
in this video, the flexinol's reaction to sound are only slight. this was mostly due to the acrylic melting upon contact with the heated wire. (by the way, that song is silent kid - pavement)
Labels: arduino, audio, booth, flexinol, led, pd, puredata, sound
sound input with flexinol and led output
we rebuilt the puredata file to also include an led responding to sound with pwm, as well as an option for adjusting the input's amplitude threshold.
Labels: arduino, audio, booth, flexinol, led, pd, puredata, pwm, sound
Tile movement sequence as train approaches the 116th ST subway station
1.digital input
2.analog/sound input
3.train at 103rd ST. heading North
4.train at 110th ST. heading North
5.train at 125th ST. heading SouthLabels: Sound TIles
tile movement diagram
Beating Facade-Final
Beating Facade-Final
final prototype
final prototype
2nd prototype
1st prototype
Group-Guillermo, Heejoo, Sang Wan, Adolfo
prototype II - two cells
prototype I - one cell
Tuesday, December 9, 2008
prototype - sound input
prototype - digital input
Prototypes 7,8
We tested a script which would randomize output. Here the LEDs are substitutes for flexinol. The random movement will provide ambient information - the default setting for our final prototype.
Here we tested a new material, polycarbonate.
We are also currently testing new touch sensors that respond to pressure and not vibration.
Labels: touch
Sunday, November 23, 2008
sound experiments
here is some video of us trying to use the kinetic output from flexinol reacting to a sound input as a screen to obscure and reveal the laptop's camera. for some reason, when we took the setup into the public to analyze the ambient/urban noises that our system would react to, it wouldn't perform, puredata kept crashing, and the flexinol wouldn't react more than once or at all... it may have been too cold.
Labels: ambient, arduino, audio, booth, flexinol, pd, puredata, sound, urban
Tuesday, November 11, 2008
mid rev.
we are currentlywaiting on our flexinol delivery... this is a mock up of our orafice system. four flexinol wires as assembled in assn 1, attached to a frame. due to the script we have working for the previous post. we can program each of these wires to act in unison, of seperately. this design allows for variable aperatures, however lacks in the varaiable aperature size that we had initially hoped for. we may still be able to attain variable changes by using a head to tail addition system of the wires.
codes_111108
midterm_111108
prototype
Only if two sensors are triggered, flexinol wire is activated.
In order to maximize the movement, two batteries and longer flexinol wire are used.
In order to maximize the movement, two batteries and longer flexinol wire are used.
Group-Guillermo, Heejoo, Dae Wook, Sang Wan, Adolfo
sound as analog input_111108
Prototype 6
Monday, November 10, 2008
Prototype1 (basic frame of interactive advertisement wall)
Prototype with PIR sensor as an input and flexinol wire and LED as an output.
We tested different length of flexinol wire to maximize movement of output.
Group-Guillermo, Heejoo, Derik, Sang Wan, Adolfo
We tested different length of flexinol wire to maximize movement of output.
Group-Guillermo, Heejoo, Derik, Sang Wan, Adolfo
Sunday, November 9, 2008
audio input and flexinol output
using our pd audio input program, we were able to activate the kinetic flexinol triangle with sound.
Labels: arduino, audio, booth, flexinol, pd, puredata, sound
flexinol and pure data toggle
using our pd toggle program, an arduino and a breadboard, we were able to activate a flexinol triangle to produce a kinetic output. the circuit includes a standard 9-volt battery and a compact relay.
Labels: arduino, booth, flexinol, pd, puredata, relay, toggle
Tuesday, November 4, 2008
audio input and pwm led output
using our mic-in program along with a couple decibel converters, we wrote a program using audio as input through the laptop microphone to control the pulse width modulation of an led (dimming). the led's intensity varies according to the amplitude of the sound input. we also have the audio signal writing to an array/wave.
Labels: arduino, booth, led, microphone, pd, puredata, pwm
led pulse width modulation with pure data
with an arduino, a breadboard, and pure data, we modified our led toggle program to use a pulse width modulator (pwm) to simulate an analog output in order to dim an led.
Labels: arduino, booth, led, pd, pulsewidthmodulator, puredata, pwm
Sunday, November 2, 2008
mic-in/arduino-out with pure data
now that we've figured out how to use the arduino as an output and sound as an input respectively, we're trying to figure out how to merge the two.
we wrote this simple mic-in program, multiplied with a simple toggle object for on/off (instead of the crazy sawtooth generator). we're hoping to be able to use this as input for the arduino-out rather than the digital toggles we have been using. (so far, we haven't been able to figure out how to do this)
Labels: arduino, booth, microphone, pd, puredata
audio input with laptop microphone and pure data
we altered a ringmod program to convert analog audio input to digital from the laptop's microphone, and then multiplied the signal with a sawtooth generator (phaser~) to enable an audio output (with a slider to change frequency). we also added an output to write the audio to an array/graph.
we used the standard mac volume control sound as the input. the audio output from the laptop speakers begins to act as an input through the laptop microphone, which creates an interesting feedback loop. (sorry about the horrible video resolution)
Labels: audio, booth, microphone, pd, puredata, sound
led pulse with pure data
in pure data, we created a program to toggle an led to pulse at a given metro rate. half way through the video, we changed the metro rate from 100 (ms) to 500 (ms). this program also uses a digital toggle object as an input (on/off).
Labels: arduino, booth, led, pd, pulse, puredata
led toggle with pure data
using puredata (a dataflow programming language much like max/msp, but opensource), we've set up a simple program to activate an led (on/off) with a digital toggle object.
Labels: arduino, booth, led, pd, puredata, toggle
LED patterns with ARDUINO
these are the videos of our led arrays using the arduino software. the code was posted on oct. 7. both videos show the same example with different pacing/delays.
Labels: arduino, array, booth, led
Tuesday, October 28, 2008
Touch Sensor Prototype 5: LED + Flexinol
Lisa Ekle, Pierre Gerlier, Keith Greenwald, Michael Walch
We set up a loop with 2 sensors for input and a LED and Flexinol for output. If one sensor is triggered alone, the LED turns on. If both sensors are triggered simultaneously, then the flexinol contracts.
Script:
' {$STAMP BS2}
' {$PBASIC 2.5}' WIRING NOTES: PIN 15 controls flexinol,
' PIN 11 controls LEDTriggerPin0 PIN 5 ' Pin that gets the touch sensor input
TriggerCount VAR Byte
Main:
DO LOW 11
LOW 15
TriggerCount = 0 IF TriggerPin0 = 1 THEN
TriggerCount = TriggerCount + 1 ' Check pin0, add to counter
DEBUG "sensor 0 on", CR
ENDIF
IF TriggerPin1 = 1 THEN
TriggerCount = TriggerCount + 1 ' Check pin0, add to counter
DEBUG "sensor 1 on", CR
ENDIF
IF TriggerCount >= 2 THEN ' Both on, turn on flexinol
HIGH 15
DEBUG "both sensors on", CR
PAUSE 1000
ELSEIF TriggerCount = 1 THEN ' Otherwise, turn on LED
HIGH 11
DEBUG "one sensor on", CR
ENDIF
PAUSE 1000
LOOP
Labels: flexinol, piezo, touch
two sensors and multiple output
two sensors and multiple outputs (LED and Flexinol wire)
10/28/08
Group-Guillermo, Heejoo, Derik, Sang Wan, Adolfo
Tuesday, October 21, 2008
Buying more flexinol locally
http://www.imagesco.com/
These guys are in Staten Island and can get any length of flexinol wire quite quickly.
What we started off with was the .006 'HT' (high temperature) wire.
The flexinol only needs 1.5V, and they recommend a more controlled source than battery power (we used an AC-DC converter from RadioShack, which works like a charger cable/power source for any electronic device.. it regulates the power much better than a battery).
These guys are in Staten Island and can get any length of flexinol wire quite quickly.
What we started off with was the .006 'HT' (high temperature) wire.
The flexinol only needs 1.5V, and they recommend a more controlled source than battery power (we used an AC-DC converter from RadioShack, which works like a charger cable/power source for any electronic device.. it regulates the power much better than a battery).
two LED & flexinol with two PIR sensor
1. Only if both triggered, both lights will be on
'{$STAMP BS2}'
'{$PBASIC 2.5}'
PIR PIN 0
PIR2 PIN 15
counter VAR Byte
Main:
'DO
IF PIR = 1 THEN
IF PIR2 = 1 THEN
counter = counter +1
HIGH 6
HIGH 8
DEBUG HOME, "TRIPPED...", DEC3 counter
DO : LOOP UNTIL PIR = 0
DEBUG HOME, "CLEARED...", DEC3 counter
DEBUG HOME, "TRIPPED2...", DEC3 counter
DO : LOOP UNTIL PIR2 = 0
DEBUG HOME, "CLEARED2...", DEC3 counter
LOW 6
LOW 8
'PAUSE 100
ENDIF
ENDIF
IF PIR2 = 1 THEN
IF PIR = 1 THEN
counter = counter +1
HIGH 6
HIGH 8
DEBUG HOME, "TRIPPED...", DEC3 counter
DO : LOOP UNTIL PIR = 0
DEBUG HOME, "CLEARED...", DEC3 counter
DEBUG HOME, "TRIPPED2...", DEC3 counter
DO : LOOP UNTIL PIR2 = 0
DEBUG HOME, "CLEARED2...", DEC3 counter
LOW 6
LOW 8
'PAUSE 100
ENDIFENDIF
'{$STAMP BS2}'
'{$PBASIC 2.5}'
PIR PIN 0
PIR2 PIN 15
counter VAR Byte
Main:
'DO
IF PIR = 1 THEN
IF PIR2 = 1 THEN
counter = counter +1
HIGH 6
HIGH 8
DEBUG HOME, "TRIPPED...", DEC3 counter
DO : LOOP UNTIL PIR = 0
DEBUG HOME, "CLEARED...", DEC3 counter
DEBUG HOME, "TRIPPED2...", DEC3 counter
DO : LOOP UNTIL PIR2 = 0
DEBUG HOME, "CLEARED2...", DEC3 counter
LOW 6
LOW 8
'PAUSE 100
ENDIF
ENDIF
IF PIR2 = 1 THEN
IF PIR = 1 THEN
counter = counter +1
HIGH 6
HIGH 8
DEBUG HOME, "TRIPPED...", DEC3 counter
DO : LOOP UNTIL PIR = 0
DEBUG HOME, "CLEARED...", DEC3 counter
DEBUG HOME, "TRIPPED2...", DEC3 counter
DO : LOOP UNTIL PIR2 = 0
DEBUG HOME, "CLEARED2...", DEC3 counter
LOW 6
LOW 8
'PAUSE 100
ENDIFENDIF
2.Independent
'{$STAMP BS2}'
'{$PBASIC 2.5}'
PIR PIN 0
PIR2 PIN 15
counter VAR Byte
Main:
DO
IF PIR = 1 THEN
counter = counter + 1
HIGH 2
HIGH 6
DEBUG HOME, "TRIPPED...", DEC3 counter
DO : LOOP UNTIL PIR = 0
DEBUG HOME, "CLEARED...", DEC3 counter
LOW 2
LOW 6
PAUSE 100
ENDIF
IF PIR2 = 1 THEN
counter = counter +1
HIGH 8
DEBUG HOME, "TRIPPED2...", DEC3 counter
DO : LOOP UNTIL PIR2 = 0
DEBUG HOME, "CLEARED2...", DEC3 counter
LOW 8
ENDIF
PAUSE 100
LOOP
'{$PBASIC 2.5}'
PIR PIN 0
PIR2 PIN 15
counter VAR Byte
Main:
DO
IF PIR = 1 THEN
counter = counter + 1
HIGH 2
HIGH 6
DEBUG HOME, "TRIPPED...", DEC3 counter
DO : LOOP UNTIL PIR = 0
DEBUG HOME, "CLEARED...", DEC3 counter
LOW 2
LOW 6
PAUSE 100
ENDIF
IF PIR2 = 1 THEN
counter = counter +1
HIGH 8
DEBUG HOME, "TRIPPED2...", DEC3 counter
DO : LOOP UNTIL PIR2 = 0
DEBUG HOME, "CLEARED2...", DEC3 counter
LOW 8
ENDIF
PAUSE 100
LOOP
3.Any possibility
'{$STAMP BS2}'
'{$PBASIC 2.5}'
PIR PIN 0
PIR2 PIN 15
counter VAR Byte
Main:
'DO
IF PIR = 1 THEN
HIGH 2
HIGH 6
DEBUG HOME, "TRIPPED...", DEC3 counter
DO : LOOP UNTIL PIR = 0
DEBUG HOME, "CLEARED...", DEC3 counter
IF PIR2 = 1 THEN
counter = counter +1
HIGH 8
DEBUG HOME, "TRIPPED2...", DEC3 counter
DO : LOOP UNTIL PIR2 = 0
DEBUG HOME, "CLEARED2...", DEC3 counter
LOW 2
LOW 6
LOW 8
'PAUSE 100
ENDIF
ENDIF
IF PIR2 = 1 THEN
HIGH 8
DEBUG HOME, "TRIPPED2...", DEC3 counter
DO : LOOP UNTIL PIR2 = 0
DEBUG HOME, "CLEARED2...", DEC3 counter
IF PIR = 1 THEN
counter = counter +1
HIGH 2
HIGH 6
DEBUG HOME, "TRIPPED...", DEC3 counter
DO : LOOP UNTIL PIR = 0
DEBUG HOME, "CLEARED...", DEC3 counter
LOW 2
LOW 6
LOW 8
'PAUSE 100
ENDIF
ENDIF
'{$STAMP BS2}'
'{$PBASIC 2.5}'
PIR PIN 0
PIR2 PIN 15
counter VAR Byte
Main:
'DO
IF PIR = 1 THEN
HIGH 2
HIGH 6
DEBUG HOME, "TRIPPED...", DEC3 counter
DO : LOOP UNTIL PIR = 0
DEBUG HOME, "CLEARED...", DEC3 counter
IF PIR2 = 1 THEN
counter = counter +1
HIGH 8
DEBUG HOME, "TRIPPED2...", DEC3 counter
DO : LOOP UNTIL PIR2 = 0
DEBUG HOME, "CLEARED2...", DEC3 counter
LOW 2
LOW 6
LOW 8
'PAUSE 100
ENDIF
ENDIF
IF PIR2 = 1 THEN
HIGH 8
DEBUG HOME, "TRIPPED2...", DEC3 counter
DO : LOOP UNTIL PIR2 = 0
DEBUG HOME, "CLEARED2...", DEC3 counter
IF PIR = 1 THEN
counter = counter +1
HIGH 2
HIGH 6
DEBUG HOME, "TRIPPED...", DEC3 counter
DO : LOOP UNTIL PIR = 0
DEBUG HOME, "CLEARED...", DEC3 counter
LOW 2
LOW 6
LOW 8
'PAUSE 100
ENDIF
ENDIF
Group-Guillermo, Heejoo, Derik, Sang Wan, Adolfo
Touch Sensor Prototype 4
Lisa Ekle, Pierre Gerlier, Keith Greenwald, Michael Walch
In this prototype we tested a thicker Flexinol wire (.015 HT) and an AC adapter.
In this prototype we tested a thicker Flexinol wire (.015 HT) and an AC adapter.
Labels: flexinol, piezo, touch
jon turkula, john becker, wayne congar
Here is the flexinol wire paired with the LED showing two separate responses to motion at different distances.
Here is the flexinol wire paired with the LED showing two separate responses to motion at different distances.
jon w. turkula, john m. becker, wayne c.
this is a test to show that the led sytem we developed previously can be used with the flexinol wire...
' PingTest.bs2
' {$STAMP BS2}
' {$PBASIC 2.5}
time VAR Word
DO
PULSOUT 15, 5
PULSIN 15, 1, time
time = time ** 2251 DEBUG CR, "Distance = ", DEC4 time, " cm"
PAUSE 20
IF time < 0015 THEN HIGH 2
PAUSE 10
IF time = 0015 THEN LOW 2
PAUSE 10
IF time > 0015 THEN LOW 2
PAUSE 10
LOOP
this is a test to show that the led sytem we developed previously can be used with the flexinol wire...
' PingTest.bs2
' {$STAMP BS2}
' {$PBASIC 2.5}
time VAR Word
DO
PULSOUT 15, 5
PULSIN 15, 1, time
time = time ** 2251 DEBUG CR, "Distance = ", DEC4 time, " cm"
PAUSE 20
IF time < 0015 THEN HIGH 2
PAUSE 10
IF time = 0015 THEN LOW 2
PAUSE 10
IF time > 0015 THEN LOW 2
PAUSE 10
LOOP
Monday, October 20, 2008
test relay
Images
Testing Relay to amplify output to make bigger movement of flexinol wire.
It was still making small movement.
10/13/08
Group-Guillermo, Heejoo, Derik, Sang Wan, Adolfo
LED with PIR sensor
Instead of using flexinol wire for output , we tested LED sensor to check if PIR sensor is working properly.
experimenting two LED with two PIR sensor. It was working properly, but two system can't operate together due to code.
10/06/08
Group-Guillermo, Heejoo, Derik, Sang Wan, Adolfo
PIR Sensor
We experimented PIR sensor which detects motion up to 20'.
PIR sensor looked like working , but we couldn't see enough movement of wire.
It might be becuase of not enough output from battery or not enough tension provided for flexinol wire. we decided to test LED for output to make sure if PIR seonsor working properly.
09/29/08
Group-Guillermo, Heejoo, Derik, Sang Wan, Adolfo
Statement
Saturday, October 18, 2008
Arduino+Amplifier+MAX/MSP (Sound as an Input )
We used the same amplifier setup as the previous exercise, this time we added MAX/MSP to visually represent the sound input.
Group - Sang Hwan Park, James O'Meara, Nita Yuvaboon, Ki Ung Na, Yemeze Edozie
Labels: Sound TIles
LED fader with MAX/MSP
Group - Sang Hwan Park, James O'Meara, Nita Yuvaboon, Ki Ung Na, Yemeze Edozie
Labels: Sound TIles
Physical Pixel Controller
Link : http://www.tigoe.net/pcomp/code/category/category/MaxMSP
Group - Sang Hwan Park, James O'Meara, Nita Yuvaboon, Ki Ung Na, Yemeze Edozie
Group - Sang Hwan Park, James O'Meara, Nita Yuvaboon, Ki Ung Na, Yemeze Edozie
Labels: Sound TIles
Tuesday, October 14, 2008
Touch Sensor Prototype 3: Relay
Lisa Ekle, Pierre Gerlier, Keith Greenwald, Michael Walch
We experimented with a relay to get more power directly to the Flexinol. The Flexinol was unable to take the extra voltage. It produced smoke and quick abrupt movements. We will experiment with a thicker or longer Flexinol wire for our next prototype which will be able to withstand more voltage and will produce greater movement.
Labels: flexinol, piezo, relay, touch
Two LEDs with PING sensor
JON W. TURKULA, JOHN M. BECKER, WAYNE CONGER JR.
We decided to see if we could produce some variability in the output. to test this we set up one led to be triggered at any distance less than 15cm, and another led to be triggered at less than 3o cm. It worked so well, that we think other people should read this and tell us about how impressed they are. We are looking to use this type of output to create an output that has some gradation of effect based on distance.
We decided to see if we could produce some variability in the output. to test this we set up one led to be triggered at any distance less than 15cm, and another led to be triggered at less than 3o cm. It worked so well, that we think other people should read this and tell us about how impressed they are. We are looking to use this type of output to create an output that has some gradation of effect based on distance.
' PingTest.bs2
' {$STAMP BS2}
' {$PBASIC 2.5}
time VAR Word
DO
PULSOUT 15, 5
PULSIN 15, 1, time
time = time ** 2251
DEBUG CR, "Distance = ", DEC4 time, " cm"
PAUSE 20
IF time <>
IF time = 0015 THEN LOW 0
IF time > 0015 THEN LOW 0
IF time <>
IF time = 0030 THEN HIGH 3
IF time > 0030 THEN LOW 3
LOOP
1 led and PING sensor
JON W. TURKULA, JOHN BECKER, WAYNE CONGER JR
This was an excersize in getting the PING sensor to activate a LED when the distance recorded is less than 15 cm.
This was an excersize in getting the PING sensor to activate a LED when the distance recorded is less than 15 cm.
' PingTest.bs2
' {$STAMP BS2}' {$PBASIC 2.5}
time VAR Word
DO
PULSOUT 15, 5
PULSIN 15, 1, time
time = time ** 2251
DEBUG CR, "Distance = ", DEC4 time, " cm"
PAUSE 20
IF time <>
IF time = 0015 THEN LOW 0
IF time > 0015 THEN LOW 0
LOOP
measuring distance with PING sensor
this is the basic use of a ping sensor to measure distance in an output window.
' PingTest.bs2
' {$STAMP BS2}' {$PBASIC 2.5}
time VAR Word
DO
PULSOUT 15, 5
PULSIN 15, 1, time
time = time ** 2251
DEBUG CR, "Distance = ", DEC4 time, " cm"
PAUSE 100
LOOP
Sunday, October 12, 2008
arduino + speaker + sound recognition
using ardurino with speaker to recognize the different sound frequency and display them on both ardurino and prossesing screen.
Group - Sang Hwan Park, James O'Meara, Nita Yuvaboon, Ki Ung Na, Yemeze Edozie
Labels: Sound TIles
arduino + Piezo + melody output
using ardurino connected with Piezo to play melody.
Group - Sang Hwan Park, James O'Meara, Nita Yuvaboon, Ki Ung Na, Yemeze Edozie
Labels: Sound TIles
arduino + Piezo + 'knock' + light output
using ardurino connected with Piezo to recognize simple 'knock' sound and LED light output.
Group - Sang Hwan Park, James O'Meara, Nita Yuvaboon, Ki Ung Na, Yemeze Edozie
Labels: Sound TIles
arduino + light output
using arduino code to generate simple light outputs
Group - Sang Hwan Park, James O'Meara, Nita Yuvaboon, Ki Ung Na, Yemeze Edozie
Group - Sang Hwan Park, James O'Meara, Nita Yuvaboon, Ki Ung Na, Yemeze Edozie
Labels: Sound TIles
Tuesday, October 7, 2008
LED patterns with ARDUINO
With the arduino board, we programmed LEDs to turn on and off in a sequential pattern. Our initial prototype consisted only of the arduino board which controlled the speed of flashing of a single LED.
int timer = 100; // The higher the number, the slower the timing.int pins[] = { 2, 3, 4, 5 }; // an array of pin numbersint num_pins = 4; // the number of pins (i.e. the length of the array)void setup(){ int i; for (i = 0; i < i =" 0;" i =" num_pins">= 0; i--) { digitalWrite(pins[i], HIGH); delay(timer); digitalWrite(pins[i], LOW); }} 
Below is our first code, and video of prototype.
int ledPin = 13; // LED connected to digital pin 13void setup(){ pinMode(ledPin, OUTPUT); // sets the digital pin as output}void loop(){ digitalWrite(ledPin, HIGH); // sets the LED on delay(1000); // waits for a second digitalWrite(ledPin, LOW); // sets the LED off delay(1000); // waits for a second}
Our second prototype utilized a bread board in conjunction with the arduino diecimila in order to control patterning among a group of four LEDs.
Below is our second code, and video of prototype.
int timer = 100; // The higher the number, the slower the timing.int pins[] = { 2, 3, 4, 5 }; // an array of pin numbersint num_pins = 4; // the number of pins (i.e. the length of the array)void setup(){ int i; for (i = 0; i < i =" 0;" i =" num_pins">= 0; i--) { digitalWrite(pins[i], HIGH); delay(timer); digitalWrite(pins[i], LOW); }}
