HeyChutney

1. Changes to our story.

So this week since we got the get-go by the teacher, we thought deeper into how we were going to make the story happen, with enough User Interface to encourage the users to use the product.

- we are still going through with the story and the fridge, the fridge is important to us as it really reminds us of the things that we take for granted every day.

- we will start with a prompt to open the fridge, then bring in the Kiwi! We realized the prompts and receiving of the feedback is very important and we can use the Kiwi to help with showing those messages 

- and we have finalized on what things/pollutants we have for the final project:

Meat (raising of livestock), Ice water (plastic and water consumption), Almond milk (paper carton and water consumption), Cheese (raising of livestock and electrical consumption of processing cheese)

- we would have the water rising and the floating of CO2 for the illustration of the pollution. and as said before there is no happy ending because – ultimately it is still happening with whatever choice you make.

2. Moving on to the NFC tag reader

SO omg main problem, we thought that we were okay at first as we managed to convert the first [0] part of the UID code of the fob key into an integer and thus being able to make the arduino differentiate the card and the fob. 

So in this example^ the first digit of the UID code was converted into an int and made to print 0 if that is ==16.

^this is then us realizing that changing all the strings to numbers was changing them all to 16 which made no sense if we wanted to use them to differentiate between tags

^this is us looking back at the original code and in the original code, the only way to tell the difference between the tags were to look at the UID

SO with the professors help once again,

^we got the Arduino to register the UID value into an array/code and making it recognize that it is a unique code and therefore sending a text saying that it is a card/fob

TAB 1: Week11/ghostwho

Clouds c; Ghosts g;  float[] ySpeed = new float[30];void setup(){   size(500,500,P2D);   g = new Ghosts();   c = new Clouds(); }void draw(){ background(#232323);//#232323g.MovingGhosts(400); //c.movingClouds(0, 0); c.movingClouds(1, 2); }

TAB 2: Clouds

class Clouds{  PShape Cloud1, Cloud2; float[] yPos = new float[30]; // going to make three variables under name of yPos float[] xPos = new float[30]; float[] xSpeed = new float[30]; PShape[] Cloud = new PShape[2]; color[] colour = new color[3];  Clouds() { //colours array colour[0] = #323232; //for darkest colour[1] = #494949; //for medium colour[2] = #646363; //for lightestCloud1 = createShape(); Cloud1.beginShape(); Cloud1.noStroke();    Cloud1.curveVertex( 31 , 5 );    Cloud1.curveVertex( 31 , 5 );    Cloud1.curveVertex( 3 , 24 );    Cloud1.curveVertex( 20 , 39 );    Cloud1.curveVertex( 43 , 52 );    Cloud1.curveVertex( 87 , 50 );    Cloud1.curveVertex( 125 , 34 );    Cloud1.curveVertex( 116 , 16 );    Cloud1.curveVertex( 82 , 4 );    Cloud1.curveVertex( 59 , 20 );    Cloud1.curveVertex( 59 , 20 ); Cloud1.endShape(CLOSE);Cloud2 = createShape(); Cloud2.beginShape(); Cloud2.noStroke();    Cloud2.curveVertex( 14 , 13 );    Cloud2.curveVertex( 14 , 13 );    Cloud2.curveVertex( 4 , 38 );    Cloud2.curveVertex( 28 , 64 );    Cloud2.curveVertex( 49 , 44 );    Cloud2.curveVertex( 70 , 50 );    Cloud2.curveVertex( 98 , 39 );    Cloud2.curveVertex( 116 , 45 );    Cloud2.curveVertex( 133 , 20 );    Cloud2.curveVertex( 111 , 9 );    Cloud2.curveVertex( 88 , 17 );    Cloud2.curveVertex( 60 , 6 );    Cloud2.curveVertex( 27 , 14 );    Cloud2.curveVertex( 27 , 14 ); Cloud2.endShape(CLOSE);  //2cloud array Cloud[0] = Cloud1; Cloud[1] = Cloud2;for (int i=0; i <30; i++) { //only when theres 100 no. of elements in your array      yPos[i]= random(-100,600);      xPos[i] = random(500,700);      xSpeed[i] = random(1,5);      ySpeed[i] = random(0,1);      }  }void movingClouds(int a, int b){    for (int i=0; i <30; i++) { //only when theres 100 no. of elements in your array    translate(xPos[i],yPos[i]);  Cloud[a].setFill(colour[b]);  shape(Cloud[a]);  xPos[i]+= -xSpeed[i];  if (xPos[i] <-70){    xPos[i]=600;    }   }  } }

TAB 3: Ghosts

Abandoning NFC sensor (for now) We met up one day thinking that we should try and see what could we do with NFC, given that we have two tags given to us in the package we bought. We initially thought of a fortune teller application which allowed the reader to see their ‘fortune’ when they put their phone on the sensor. Problem 1: a teammate started asking me so are we using the phone as a sensor itself? or a tag? - I instinctively thought that we could follow the ‘adopt a dog NFC project’ where the phone would run across the poster and be redirected to a website on the person’s phone. Meaning, that that would make the phone a sensor instead of using the one we bought. Problem 2: We must use the sensor we bought as we needed to use it and be redirected to Arduino and processing on the computer. Hence, we thought we could use the phone as a tag instead and have the ‘fortune’ show up on the computer screen. It seemed easy enough. Problem 3: We then went online to search whether the phone can be used as a tag. That was very confusing therefore we chose to just use the tags that came with the sensor. However, even finding the unique code/name of the tag proved to be too difficult for us to configure something in time for class on Monday therefore, we decided to ditch the subject. 

Back to square one  So we started thinking that we don't really have time to get a new one and if so we need an easier one to make it in time for Monday's class. Behold, there were 4 photocells PDResistor’s in Jiho’s Arduino kit. Hence, we decided to go with that sensor and make the application more interesting to make up for the loss in difficulty. Honestly, at the side i was still researching about the NFC sensor as i can't let a good idea go, Jiho came up with an incredible plan, where he thought of a cave game where the players have to dodge rocks by shining the light in a particular direction in order to know where to go. 

Finding out for ourselves how does the sensor works and what can we do with it Sujin and jiho decoded one code pertaining to displaying the light directed at a light sensor and seeing if it works, we then moved on to displaying that as an image on processing! So by then, we proved that we can easily use the sensor to generate readings and the communication to processing seemed stable. We then figured we should go home and start preparing for our next meeting, so our parts for that were val-sort out readings and wiring for PDR. Sujin - figuring out arduino to processing sketch, Jiho- game interface and processing sketch.

Serial communication This was the code we referenced: https://arduinobasics.blogspot.com/2011/06/arduino-uno-photocell-sensing-light.html At first, we had some problems with the sketch as it showed us continuous problems about the port being busy, or there is no such port or there is an error. We realized that we were using COM13 which was the port that the user online was using and it didn't apply to us. We then used professor’s sketch to reList all the ports that we had and use that to refer processing to the correct port. We then had problems displaying the readings as an image on the screen however, we realized that we didn't need that for the project, therefore, we abandoned that and rewrote the code as println instead. For the code given online, they also rescaled the range of readings to a fixed 0-100 which seemed neat, however, we thought that if we were to have 3 sensors we would have to create 3 more minLight maxLight adjustedLight variables which would be hard. So we looked at our idea again and realized we don't need the readings at all we just need to know which sensor reads the maxLight at that point in time. and to do that Sujin came up with the if statements   if((lightLevel1>lightLevel2) && (lightLevel1>lightLevel3))    {maxLight=lsA;}  if((lightLevel2>lightLevel1) && (lightLevel2>lightLevel3))    {maxLight=lsB;}  if((lightLevel3>lightLevel1) && (lightLevel3>lightLevel2))    {maxLight=lsC;} quite self-explanatory really but the thought process was hard :”) 

Meeting up for assembly The day after, I was surprised by how much Jiho had done with the processing sketch! His aesthetics were on point his whole game dynamics and movements and maths were all great. I marveled at how he could create all of that in one night! At first, the same serial port problems came back but after all the proofreading - I shall cut it short ya.  we found out that the processing code had a setup function in the startup screen, therefore, rendering the whole sketch to stop because setup should be only run once, therefore Sujin told Jiho to add another function: initialize. and that is what saved the day. In the videos we made, the computer screen seemed to lag, however, I think it is because I was taking a video of the whole programme running therefore it lagged.

EG. #1 finding the port between arduino and processing

code in processing: import processing.serial.*; //import serial library Serial myPort;void setup(){  //size(500,500);  println(Serial.list()); // list is provided in the library - an Array  myPort = new Serial(this, Serial.list()[4], 9600); //manually type in port name  myPort.bufferUntil('\n'); //break a chunk - line break/seperator  //when it says port is busy because the info is gg to serial monitor }void draw() { }void serialEvent(Serial port) {  String myString = myPort.readStringUntil('\n');  if (myString != null) { //when my string is empty,  //we have to skip it. this confirms we have something  println(myString);  } }

code in arduino: void setup() {  Serial.begin(9600);}void loop() {  Serial.print("valerie"); //what would show up on processing via serialPort  Serial.println();  delay(50);}

Trim function -

removes white spaces in  string -  so you can convert the numbers/ raw numbers into integers for the com to read Create the shapes first then add in the interactivity

Map function - 

maps a number from one range to another. Syntax- map(value, start1, stop1, start2, stop2)

How to filter noise signal - make it more stable 

averaging method - specify sample size, dont send actual value. save 10-20 signals into an and average out sample less responsive -  and still noisy

Arduino code:

const int numSamples = 20; //specify size with variable- never going to change it once i set it up float sampleBuffer[numSamples]; //create an array and initialize 

void loop(){ //before you print the value you average it

for (int i = 0;i<numSamples-1; i ++) {     //minus one because we are finding the 20th place as our array only has 20 sampleBuffer[i] = sampleBuffer [i+1];     }

sampleBuffer [numSamples-1] =irVal //moves the values one slot down  so that the average value can take each 20th place float sum =0; for (int i=0;i<numSamples; i ++) {    sum = sum + sampleBuffer[i]; }

float avg = sum/numSamples

Examples

simple installing of potentiometer

Creating a led to light up

The (val) is the number of the light intensity

Creating a dimming LED

same setup but different code - using the sine graph

Changing the sine equation:

t over val sine graph - so if you change the x in sin x - you’re changing the period in the graph you add 1 so you can translate the graph upwards to get +ve values

multiplying (*255/2) - change your Val value - to reach the max number for the led to register. at first graph’s midpoint is 1 so you expand the graph to house the numbers from 0-255

Creating Light dependant on Potentiometer

Ultrasonic Sensor 

Vcc - Power in. Trig - transmitter - transmit sound waves. Echo - Reciever - receives echo sound. Gnd - Ground.

sensor calculates the distance therefore giving us input

CODE:

int trigPin = 7; //trigger

int echoPin = 8; //echo

long dist;

void setup() {

Serial.begin(9600);

pinMode(trigPin, OUTPUT);

pinMode(echoPin, INPUT);

}

void loop() {

digitalWrite(trigPin,LOW); //make sure its clear of values

delayMicroseconds(5);

digitalWrite(trigPin,HIGH);

delayMicroseconds(10);

digitalWrite(trigPin,LOW); //make sure the values are clear to sensor

long duration = pulseIn(echoPin, HIGH); // long - big number // calculates the time it gets HIGH - how long it took for echo pin to receive trigger sound

dist = (duration/2)*0.0343; //dist = time x velocity

//duration divide by 1/2 cos it went back and forth

//velocity of sound 343m/s = 0.0343 cm/microsec

//therefore use this equation to calculate the distance

//hence you can print it as distance

Serial.print(dist);

Serial.println("cm");

delay(50);