Leena Al Sallakh Design

Tangible Interactions Flow Diagram for A1 The flow diagram I have created for my A1 assessment, is all connected, where I made sure pathways between each and every interaction had two options that either linked to the before interaction or the after interaction. When looking at examples, during the tech workshop and completed flow diagrams for our class exercises (that I haven't posted due to how bad they are and the amount of no common sense involved in my attempts) I came to the understanding that a flow diagram should clearly display the interactions as well as keywords to indicate which sensor is being used where etc. My flow diagram below it was I created for Ruff's Cookies; My simple but slightly complex diagram, follows a couple rules...these are rules that I have created from looking at other flow diagrams and working on an example in class with my Tutor.  The diagram must have three different types of shapes that clearly represent the questions, the answers and the res...

 My initial idea involved a RFDI chip but has since evolved and changed to using a hall effect sensor that does the same thing but is a lot easier to code.  The hall effect sensor used a magnetic to interact with, you simply tap it against and a red light flashes to notify you that it's connected. I have also coded the hall effect sensor so that when you tap against it, the warnings stop.  In the scenario with my idea, this means the hall effect sensor will be used as an overide. So parents can basically have a cookie anytime they want and control the childrens intake. The video below, shows how the hall effect sensor will be used in the scenario;

 After talking to a Tutor for advise on my code/arduino set up, there was a problem where the buzzer continues to make noise when it's not supposed to.  To fix this, it was suggested that we use a potentiometer instead of a tilt switch to see if that would change or fix things. As you can see, in the video, this was not the case. The noise still continued to happen but admittedly it was a lot easier to turn on, in my Tutor's word, the potentiometer has more stability than the tilt switch. This gives me something to think about as, while it's more stable, the interaction isn't as physical as the tilt switch, which means I might need to rethink how I will integrate it into my design.

My second experiment with the ultrasonic sensor went a lot better than I thought it would. This tutorial came from the Arduino website:  Arduino Distance Detector With a Buzzer and LED's In the below video, we can actually see an interaction where the closer you are to the sensor the higher you here the buzz, with different warning sounds as well as the lights that show three warnings! 

For my A1 tech task with the cookie, I'm looking at using the tilt switch as the turn on and off. Its the start of the interaction. To turn it the cookie jar on, you have to tilt the jar and that's when the sensor will be turned on. I have done a previous experiement with the tilit sensor, however, in the video it was used to detect vibration and was not the main instrument. In the below, video you can see how I have used the tilt switch sensor as an input that you must interact with in order to one, start the system, and two, to turn the LED light on in order to know that it's turned on. I am very pleased with the result of the tilt switch and now just need to join it with the ultrasonic sensor for my code. I hope it works!

My first experiment using the ultrasonic, didn't actually go that well... Admittedly, it could be my fault but I followed the directions to a T, crossed my t's and dotted my i's etc.  I followed the tutorial from this website:  https://howtomechatronics.com/tutorials/arduino/ultrasonic-sensor-hc-sr04/ But this happened: In the video, as you can see, I ended up removing the black cable and it seemed to work or at least respond...ish. This example didn't really help with my understanding nor did it help with my A1 assessment. 

Ultrasonic for the Win  To detect motion in order to set off the warning 'growls', I have looked at using a PIR sensor.  While I can use it, I have been advised by the world's best tutor, i.e. James (See James I am a nice person!) that it's not the best sensor to use and would basically be a massive pain trying to code and deal with its delicate sensibilities. To instead use an ultrasonic sensor to detect motion etc. They are easier to code and will get the job just as good. Basically, the moral of the post, is to avoid PIR and always listen to your Tutors, they know what's best!