Leena Al Sallakh Design

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...

The more I work on my chosen initial concept the more complex it becomes as I find myself trying to design for everything, the whole experience of going to the bathroom. It's becoming more and more difficult to try and factor in the Arduino side of things, to figure out the sensors needed and how I would code the mechanics of the product. From talking to some of my colleagues and my Tutors, I have more of a direction in terms of how I would build it, so to speak. The images below are my crappie (apparently architectural) sketches as I try and figure out how I will simplify my idea and go about manufacturing and coding it. By the end of the session today, the one thing I really took away from today, was that I have a lot to do…I probably, no I definitely, bit off more than I can chew…

 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.

In our week 4 tech workshop, we were provided with advice and how best to test your code and your inputs as a result.  For auto formatting – Ctrl + T Signal testing, wiring input > need more than just power, basic circuit in slides Multimeter > can test if circuit is complete Serial monitor to display serial functions Serial print to check if its running correctly and can use to get range etc Next step to test what’s happening Test each input at a time, set up one and test that so you know its working, so you can start figuring out what’s wrong Versioning code extremely important Using fault testing tools to detect things Start from base and then do trial and error to tweak the code already there for your purpose   It's important to note that our wiring diagram must be as good as perfect or our code won’t work without it. A trigger, what a switch could be…could use time of day as an event…and they have a trigger event system To code and figure things out, we were a...

Using the same example from previous exercises in Tech Workshops, the fading light example, I tried to re-code it using two different inputs.  The first was with a temperature sensor that turned the light on when it ranged between 50 to 55. The second attempt was using the same input with the potentiometer, but coding so that when the potentiometer is turned within a certian range the light will turn on.  I tried to create proximations to make this work. It was through the serial printer that we checked that it was possible as it depended on the room temperature.                                                         The second exercise was to try and find a differnt piece of code and use different sensors to test. In the following videos I followed an example to make the fan work. However, I found an issue w...

During week 3, to analyse different types of interactions, we renacted how to turn on a switch. The Exercise:  Simulate a switch (action and reaction) Sketch, make, speed, quantity Low-fi models sketches Use scrap materials to represent a sketch 8 Two Low-fi models, a standard on/off and a slider on/off      Video demonstrations of the Low-fi models and how they work