Posts

Showing posts with the label Sensors

Week 13.2 - A3 Finalising Code

Image
 Yikes! lets begin with that. It has been one hell of a ride with this code. For most of the duration of A3 I have been trying to code infrared leds and transmitters...NOT BEAM BREAKERS. It was only until last week Thursday during our tech workshops that I was finally introduced to them. Thank God for that, I was about to pull my hair-that you can't seen under my hijab-out. The Beam breakers are amazing, whoever designed them is honestly my hero. While it has taken me a couple hours to get the code, (and its still not perfect 100%) they have taken my code to not working to everything is working as it should with the expection of the display screen that is clearing at the moment. But the detection is just amazin and how accurate it is and how each stage correlates with each other. It's late and I'm happy.  The video below demonstrates the working interactions, with a couple things missing (such as buttons) for how my design will monitor the bag and inform the user through li...

Week 12.4 - A3 Coding

 A3 Coding - Wasn't on the right track but now I hopefully am Coding for this has been a nightmare. The good news is that I finally got the LED light working, where I can turn it on and off with the remote thanks to the help of another collegue. The video below shows that achivement. The bad news is that instead of trying to use the infrared led senders and transmitters that I have, I have been strongly advised to switch and insteead buy beam breakers, which I found and orderded today cause trusty Jaycar don't have it. Though good news as well is that the display screen works! The video below shows me using code from this website:  https://lastminuteengineers.com/oled-display-arduino-tutorial/ The website was a massive help and explained each component of the code, so I understood it and know how to covert and adapt what I need into my final A3 code.

Mid-Break.3 - A3 Coding for IR receiver

Image
Coding for A3 - IR The coding for A3 is quite fustrating. I'm not sure what I'm doing is correct and since its infared its hard to see what's working or not. Without the serial monitor, I would not be able to tell if it works. (The code I have been working on for this post was from https://www.dfrobot.com/blog-648.html (project 14)) Which is a good thing I guess, as it would tick the subtle box, with nothing showing... As you can see in the video below, the demonstration by itself only shows me clicking the remote but there is no visual que/output that can be seen/ That is until you look at the monitor on the computer where you can see that something is happening on an invisible line. Below are also some pictures of my simple set up. I sadly coudn't get the LED to work with this code.

Week 10.3 - A3 Concept Progress - Monitor Device

Image
Design directions for my product has finally simplfied to where I am happy with. I have a more solid position thatn I did before. I actually feel confident in this direction. So from the images below, I have started to focus on the monitoring device in more detail. I have very briefly mentioned in this in one of my crappy drawings but never focused on it as I felt it was too simple for this project and scope etc. But basically, the monitoring device is for people with spinal cord injuries to keep track of their colostomy/catheter bag and to notify them when it gets 3/4 full etc. It's a device that monitors the fluids going in using 3 IR receivers and 3 IR LEDs (senders) where I plan to code it so that if the link between the two receivers is blocked for more than 10 seconds than it means its a constant and not a spontantous block, like would happen when fluid etc first enters the bag. These notifcations, (excuse the crappy band and hand, literally drew it 2 secs) would be displayed...

Feedback, Attention & Status

Image
Feedback, attention and status From a previous class we were taught what the above mentioned are in relation to our arduinos. Feedback – objects immediate reaction to input Attention – object communicating with the user that there has been a state change Status – output that indicates the object current status They can be many different things, it just depends on what your inputs and outputs are and the interactions. The same experiences could be created using Arduino components, haptic motors, buzzers and LED’s Status is passive, attention is active When something goes wrong you might draw the users attention to something (hence active etc) Daily stack challenge using Arduino e.g. https://vimeo.com/29710376 Attention, the blinking light and display screen blocks Each block has weight, colour differentiates between each other How can you lead through the interaction in the simplest way? Knock knock project (simple calculator) https://vimeo.com/60773296 Getting...

Arduino Coding - Hall Effect Sensor

 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;

Arduino Coding - Potentiometer

 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.

Arduino Coding - Ultrasonic Experiment x2

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! 

Arduino Coding - Tilt Switch

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!

Arduino Coding - Trying Ultrasonic

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 not PIR

Image
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!