Wednesday, October 18, 2017

Week 8 Reflection

First Day:

Notes: add monster face, ears, something. Make a graphic maybe to make it more game like. Box was too boring I think, but if I were to add more to interface it would make it more intriguing. 

Second Day:

Talked about --->
Plans for next week:

Presentation (slide or blog post--images)
  • Arduino
    • input
      • sensor technology
    • output
      • physical computing
  • Wearable
  • Narrative
  • references
  • pictures
  • links
  • videos
  • tips
  • hints
  • details
  • ideas

  • Plug in 
    • NOT high amp
    • response sensory feedback
  • Relays
Example of previous projects: a shirt that has LEDs that measure where she is in space and react accordingly.


Adafruit Wave Shield Kit:


Friday, October 13, 2017

Noise Project

So I took apart this box that I already had and spray painted the inside (because the outside was glossy and had type on it and I just wanted a regular cardboard box).

These are the supplies I used to do all the technical things:

So, first I started soldering the wires to the board each assigned to their own position ahead of time. 

Once I soldered each wire I planned on using, I then soldered those wires to copper wires, which I plan to use as the "buttons." I decided to use copper because I had some and it's conductive and the copper would look cool against the black paint. 

After soldering all the wires to copper I clipped the copper wire ends to about half the length they were giving me enough wire to make a spiral shape and also stick through the box and reach the electrical components. 

I then poked holes in the cardboard box (thinking ahead that I needed six holes and also thinking about how large the "buttons" would be) and stuck each copper wire through keeping in mind which touch pad their belonged to.

I then assigned stickers to each "button" to match its pair (because two "buttons" are needed to activate the correct sound).

The product is done, but an issue I came across was that the copper wires would not touch each other because then the sounds would be affected and wouldn't be the sounds I intended OR there is a possibility that it would not make noise at all. 

Finished Noise Project:

Wednesday, October 11, 2017

Week 7 Reflection

First day of class was cancelled due to hurricane Nate.

Good/Bad/Ugly Instructables Posts


  • Quality Images
    • focused images
    • high res
    • well lit
    • good background
    • clearly labeled
  • Images
    • photos document, schematics, drawing, flowchart, diagram
  • Text/Words
    • clearly explained
    • not too wordy
    • does not use words that are too technical or difficult to understand
    • grammatically correct text
    • supports images (doesn't just say look at the photo/video)
  • Materials
    • references
    • links
    • data sheet or vendors
  • Narrative
    • reasoning on why they started this project
    • what its purpose is
    • doesn't have to be dry and academic, just informative in some sort of way
  • Features
    • Instructables offers a feature where you can label pictures and capture a part of the image in a square/rectangle and when hovered over can be read by the viewer. 

Instructables blog creating:
  • Be sure to take a photos as you go along
  • write as you go along
  • do not write the day before or after you finish the project because you won't remember every step you took

Final project requirements:
  • Input(s)
    • the sensors
      • thinking about hall sensor
  • wearable
    • something you hold, wear, touch, etc.
  • Arduino

  • output(s)
    • "does something in our world"
    • can have multiple if you want, but you don't have to
Could always do something similar to the video of the video of the guy moving the thing around that makes different sounds. (revert to sword.. maybe use a bat or something different from a sword. Hulk hands?? lol 

Look around a Halloween store 

    • Flex sensor....
      • something to think about

Wednesday, October 4, 2017




The Good, The Bad, The Ugly: Instructables


I thought this was a good tutorial because it explained things and gave many tips, however, I thought that it would have been better if it were a little more detailed, but overall I thought it was good.


The reason I thought this was a bad tutorial was because it didn't have an end result it just said "fix it to a motor." Also, I thought that it could have used more pictures and it didn't explain their method of the "shape" they used to cut the bottom of the bottle.


This was a horrible tutorial because most of the instructions are 1-2 words long and don't explain anything at all. There are also no list of supplies you need or what paints were used or anything in that nature. Also, the end product is ugly anyway.

(For Fun):

Week 6 Reflection

For the first day, we presented our projects and talked about all of them individually. I thought that it was very thorough and there were many interesting projects, but I think all could, in the end, be better and very fun. I think our project went fine. I was concerned about how ours wasn't an interface, however, I did not realize that there was supposed to be any sort of hands on or physical interaction.

We also discussed and were introduced to a new tool that we would be using for our later projects. We talked about what each button does, right down to the backlight for the screen and the simple hold button that can come in handy for tricky situations.

Lastely, we discussed more about ways to connect input and output. Arduinos, which is what we will be working on next class.

Day 2 we talked more about our final project and how we should be working on the noise project.
We also were introduced to an Arduino that we were able to work with and test out different inputs and outputs in the Arduino program.


Setting up where your Arduino saves:
Arduino --> Preferences --> (Browse) MacHD --> volumes --> your drive / wherever you want it on your computer

"Set Up" (like the header) = parameters, things that run once

"Loop" (like the body) = runs forever or until new code is written or it is shut down.

Variables: sit outside the rest of the written code, are ways in which to identify a specific "piece" on your board so that you don't have to go back and rewrite a bunch of things later if you change them on the board. (in example below is "int")

There are types and Functions and Variables.
Arduino is very picky and wants things to be written in specific ways.

Delay is in milliseconds. (1000 = 1 second)

Arduinos are pretty durable.

First Test:
File --> Examples --> Basics --> Blink

int pin=13;

void Setup(); {
pinMode (pin, OUTPUT);


void loop() {

digitalWrite(pin, HIGH);
digitalWrite(pin, LOW);


Week 8 Reflection

First Day: PRESENTATION DAY! Notes: add monster face, ears, something. Make a graphic maybe to make it more game like. Box was too b...