Back to Parent

Outcome


Intention

The problem area we are interested in is social isolation, particularly the social isolation of immigrants and refugees in the current political climate. Our solution involves an interactive device set up in a public space, which senses the high-five's from people. A pressure sensor on the hand-shaped board would sense and count the handprints of passers-by who volunteer to send a high-five to immigrants. The number count of high-five's would be linked to the clocks, located both in the place with the sensor and another public place with a high number of the immigrant/refugee population. The clock hand, connected to a servo, would point to a certain color programmed on Neopixel based on the number of high-five counts and replicate the sound of a real clock every time it moves. When it reaches the “love O’clock”, which is the maximum number of counts set on the clock, it would play music. This real-time interaction and data shared allow a more human-level connection between people who live in different socioeconomic, political circles. Through our solution, we aim to show social support to people who are unseen and unheard. We hope to push this social campaign forward and reach a larger population. 

8
Show Advanced Options
7
Show Advanced Options
Process

1. Ideation and planning

We first started off mapping out the interactions among the devices. We drew a diagram of the interaction between the sensor and three devices (Neopixel, Servo and Piezo). Based on the feedback we received, we switched our sensor from a touch sensor to a pressure sensor. For this prototyping stage, we decided to keep the switch we currently have in order to perfect the interaction prototype first. 

2. Build the circuit and pseudocode

The first requirement we fulfilled was planning how the Neopixel, Servo, and Piezo would receive and process the input from the pressure sensor. We discussed several methods we could potentially take; one option was to have every pressure input publish an event which triggers interactions of the devices, and another option was to have one device count the number of high-fives and publish the number to other devices. At last, we came to a conclusion that it is most effective and efficient in terms of the process operation and our team collaboration if we have the Piezo be the only one to receive the signals from the sensor, and publish for other devices to respond. 

3. Coding and build individual devices

We took a 'divide and conquer' approach for this step. We each worked on our device to create the interactions we were envisioning.

Neopixel: When it receives the signal from Piezo, Neopixel counts the number of signals, and based on the counts it displays different colors. We envision that the 'Love O'Clock' would mean having at least 1 million people's high-five's. However, for the convenience of this prototyping process, we decided to reduce the number to 15 to effectively test the interactions. 

Servo: Likewise, Servo would also receive the signals from Piezo and count the number of signals. At every count, Servo would move 24 degrees clockwise to accord with the 15 LED lights on Neopixel (= 360 degrees/15 LED lights). The challenge we faced with Servo, however, is that Servo does not rotate full 360 degrees, and its maximum rotation range is 180 degrees only. Hence, for this stage, we coded the Servo to reverse back to the starting point once it reaches the 180-degree limit.

Piezo: Piezo senses the signals from the pressure sensor (in this current stage, pushdown button). Based on the number of counts, Piezo plays different sounds. At every high-five, Piezo beeps once, and at every quarter it plays different melodies. We utilized the notes of the Westminster clock, which signifies the time progression through the completeness of the melody it plays. 

4. Paired 3 devices 

Our devices were paired from the beginning, but we still had some fine-tuning left to coordinate the three devices' interaction together. We confirmed that each device successfully fulfilled its task individually upon the signal the Piezo receives from the push-down button.

5. Adjust and test code

We have been continuously adjusting our codes to fine-tune the interactions of the devices. We have yet to improve on the consistency of the workings of these devices at an individual level and at a group level. We will continue to work on this for the next week and complete our project.


3
Show Advanced Options

Outcome

List of Parts:

  • 3 Breadboard
  • 3 Particle Argon
  • 1 FSR Sensor
  • 1 Neopixel
  • 1 Piezo
  • 1 FSR Sensor
  • 1 Servos
  • 17 Resistors
  • 2 USB Micro B Cable
  • 21 Jumper Wires

Sketches:

6
Show Advanced Options

Code for Side A - Piezo & FSR

Currently, we are using a pushdown button instead of FSR. 

Show Advanced Options

Code for Side B - Servo

Show Advanced Options

Code for Side C - NeoPixel

Show Advanced Options
Show Advanced Options
Drop files here or click to select

You can upload files of up to 20MB using this form.