Team Status Report for 4/12/2025

The most significant risk that could jeopardize the project is the load cell amplifier. Since there is so much noise, we are currently unable to get any good reading (as shown in the picture below). From the research we’ve done, its likely due to the fact that HX711 load cell amplifiers work best for load cells that measure higher weights and that soldering can add to noise since we need a specific type of wire. However, we had to solder the wires because the load cells wires were so fragile, they kept on breaking. Aneesha and MM are looking into other solutions to explore such as force sensors. We decided to replace the battery pack with another buck booster converter to achieve better accuracy on the voltage that we need for a good reading. Additionally, we ordered another pack of SD cards, since we do not have any spares left. Both of these cost less than $40, keeping us under budget. The team will work on testing (accuracy of pills being dispensed, website re-sizing to devices, mobility needed to operate device, etc) as listed in the design report section 7. More specifically, we will pull up the website on a variety of screen sizes and go through the motions of the website to make sure everything is rendering appropriately. We will conduct about 60 dispense trials across a variety of pill sizes and record the accuracy of the dispensing. 

MM Demangone’s Status Report for 4/12/2025

I have completed quite a bit over the past two weeks. Last week, I spent time on deploying our website, connecting the RPi and website to the websocket, and refining the communication between the two. I had changed the model to store the servo angle, so our device can alternate between 0 and 180 degrees. I had fixed a bug involving overpopulating the google calendar with pill notification events. This week, I spent a lot of time refining the load cell amplifier code, soldering the load cell amplifier, soldering both of the load cells, and testing out the load cells. Also, after Aneesha had reflashed the SD card, I had set up the SD card with github, dependencies, etc. Unfortunately, the readings off of the load cell amplifier are extremely noisy, and is prolonging the amount of time we expected this task to take. Aneesha and I are both working on fixing this, by exploring other force-measuring devices, as load cell amplifiers with a greater precision measurement will not arrive in time for demo day. Next week, I hope to get a lot of software testing done as well as pill dispensing testing. I will make multiple accounts, edit parts of each account, make sure the correct pill amount is dispensed during this testing. Further detail on all of the steps for how I will conduct this testing is listed in our design report section 7. I have included some of my commits below detailing my work.

https://github.com/tkoda1/Capstone/commit/52153443769970d5b3bec07acddcc8a33940e788

https://github.com/tkoda1/Capstone/commit/8e2f1ede953c83bf4c23725f7553dc5e17deab63

https://github.com/tkoda1/Capstone/commit/9b43286ae90b60116683018f09225a7b4d29f412

MM Demangone’s Status Report for 3/29/2025

This week I accomplished several main tasks: integrated the speaker into the RPI5, connected websockets across the web app and the RPI5, tested and integrated RPI5 code I wrote in previous weeks, deployed to EC2, and continued to work on the 180 degree servo motor motion with my team. I did fracture my femur and tore my labral, so walking around campus will be difficult as I am on crutches for the next 8 weeks. I am on schedule with all of my tasks. Next week, I will work on preparing for the demo with my team and continue to work with Aneesha and Taylor to physically build our project

MM Demangone’s Status Report for 3/22/2025

This week I worked with Aneesha on the hardware components. We had spent Sunday re-setting up our RPi5 again as the SD card was fried due to a wiring mishap. We had spent Wednesday’s class soldering wires to our servo driver. Since then, we spent time working on getting the servo motors to move, and I had set up remote SSH on the RPi5. We have successfully created code so all 6 servo motors move, upon the user manually instructing which motor to move, via bluetooth. This is obviously for testing purposes, not as the final product. While the servo motors are moving, they are not moving a whole 180 degrees, so we will continue to work on that. I had also created some code for the load cell amplifier to read the weights, but haven’t had the chance to test it as we need plates to be on both side of the load cell amplifier. Additionally, I had set up websockets on the RPi5, however, I haven’t tested it yet because our app needs to be deployed to EC2. We have realized that most web browsers do not support bluetooth, so we will eventually pivot away from bluetooth and towards web sockets. I am going out of town tomorrow, so I am submitting my status report a few days early. There are quite a lot of github commits, as we ssh into the raspberry pi and need to pull any changes we want to test, but I have included some of my “highlight commits.” I am ahead of schedule in regards to the weight sensor, but a bit behind with the web socket communication between the RPi and the web browser due to delays with EC2 deployment. However, it does work via bluetooth, so we simply need to change the method of transmission. Next week I hope to test my websocket code on the RPi5 after deploying it to EC2 and have the servo motors move 180 degrees. 

https://github.com/tkoda1/Capstone/commit/888f203d0ef824a518d87993ad75c521b3fe1026

https://github.com/tkoda1/Capstone/commit/e4ef905aae6ae3cb90adfed0ad1f6eed6445f6b7

https://github.com/tkoda1/Capstone/commit/e340b7608117ff9f28c711fab6af92b836bdd7b0

MM Demangone’s Status Report for 3/15/2025

This week, I had worked on the ethics assignment with my team as well as several project-related tasks. I had made the pill refill notification, set up and configured the raspberry pi (bluetooth, settings, etc.), and set up web sockets on the web app. With Aneesha, we worked together to set up the bluetooth code for our devices to communicate with each other, in the form of communication via chat. I was running a little behind schedule this week, as it had taken me longer than expected to figure out the bluetooth, but as of now, I am back on track with my schedule. I am leaving for Washington DC from Friday to Monday, so I will work on more tasks earlier in the week. Deliverables that I hope to complete this week would be continuing to build on the bluetooth code. Specifically, having the bluetooth code send over information when the dispense button is clicked, and setting up the server/client scripts upon logging into the web app. If I have time, I will work on writing the sensing code for the load cell and assembling it, although this task isn’t due for a couple weeks.

Team Status Report for 3/8/2025

The most significant risks that could jeopardize the project are the performance of the servo motors turning with the pill dispensing disks on it. Given the torque the motors operate at and the weight of the pill dispensing disks, we believe that it should work. However, in case this doesn’t work, we have been adjusting our pill dispensing disks to be a lighter weight.

A change we had made to our design was choosing a different load cell. This had cost us an additional $10 and fits into our budget. We had ordered a new cell because we had mistakenly purchased a 780g cell, thinking it was a 780mg cell. After completing the design tradeoff section of the design report, we realized this design mistake, and we bought a 100g load cell instead. This did not impact our schedule as the delivery was through Amazon. 

For the week 4 specific status report, part A was written by Aneesha, part B was written by MM, and part C was written by Taylor.

Part A: Our product seeks to improve the problems associated with the medication taking process globally. The device provides automated medication management, which is crucial for people with limited hand mobility, elderly individuals, and people with cognitive impairments who may forget to take their medications in a timely manner. By ensuring accurate dosing and reducing the risk of medication errors that can impact anyone across the world. Additionally, by integrating an app with our machine, our product aligns with global trends in digital health and telemedicine, where digital services are increasingly being used for medication management in both developed and developing countries.

Part B: Our product addresses several cultural aspects. For example, family members who have taken on a caregiver role to care for a loved one can find this product beneficial to either: (1) give the loved one more independence by receiving reminders via the app not via the caregiver (2) take some weight off of the caregivers shoulders of remembering which pills their loved ones need to take at a specific time. By giving loved ones some more independence, it can allow them to stay in their homes longer before moving into assisted living or prevent them from hiring in-home care. This is great for individuals who might have financial concerns. 

Part C: While this project does not focus on environmental impact it was designed with environmental factors. The project was designed so in the long run consumers could potentially reduce the waste of pill bottles used. Additionally the project this week was designed this week to be smaller then the original design so it would take less energy to power. Additionally the project is designed to be safe for organisms to consume medication out of being non toxic. Additionally the product is designed using sustainable 3D printing materials.

MM Demangone’s Status Report for 3/8/2025

Over these past two weeks, I had worked on a variety of tasks. First off, I had worked on the design proposal, specifically sections 3, 5, 7, 8, project diagrams, and general formatting. Additionally, I had gone through the process of updating our markups and ordering a new load cell. I began working on my ethics assignment. Lastly, I had finished one of my tasks due on the 10th; I had added the pill notifications to alert users to take the medication on our web app. I have included the link to the pill notification alert Github below. For this upcoming week, I plan to finish my ethics assignment, implement bluetooth on the software and hardware sides, and implement the pill refill notification. I am on track with our project’s schedule.

 

https://github.com/tkoda1/Capstone/commit/ce95b24671d35565f74222b3641833a28e5b7784

MM Demangone’s Status Report for 2/22/2025

This week, I had prepared for and given the design review presentation. I had also picked up our packages that were delivered to the ECE receiving room. I had begun working on our design review presentation, primarily the cost breakdown, testing sections, and formatting our timeline. Based on the questions and comments made in our presentation, I have added those recommendations into the design report. However, based on the design feedback my group receives this week, I plan on going back through these sections and adjusting what is needed. For the upcoming week, I plan on finishing the design report (due Saturday) as well as working on the MySQL database creation (due Friday). I plan on meeting with my group this week to begin distributing parts, so we can work on our respective tasks. I am on track with our project schedule!

Team Status Report for 2/15/2025

Similar to last week, the most significant risks that could jeopardize the success of the project is the 3D printing and integrating the entire system, as our team does not have collegiate technical training in robotics or 3D printing. To manage these risks, we are working on the CAD model and will print as soon as possible, giving us ample time to adjust if necessary. Additionally, we have been working with TAs to make sure our circuitry and power supply will suffice. There were design changes that we had made, namely adding a servo driver, speaker, load cell, and power supplies to our design. This was necessary as we explored our proposal more and incorporated feedback from our presentation, professor, and TAs. This did increase our final cost, as shown in the linked spreadsheet. However, we are still within the constraints of the $600.00 budget.

Part A was written by MM, Part B was written by Aneesha, and Part C was written by Taylor:

Part A: In terms of public health, safety, and welfare, our product allows users to make sure they are taking their correct medication at the correct time, whether they are prone to forgetting if they took their medication, taking too much medication, etc. It is important that our product dispenses the correct dose, however, or else it can pose potential medical risks to the client. Additionally, our product will be safe by using medical-grade cleaning. While we will not have this for DemoDay, as it is a prototype, our final product will be sterile by using ethylene oxide gas sterilization and UV-C light sterilization. We have chosen ethylene oxide sterilization to sterilize the plastic body of our dispenser since our product, made of plastic, would be sensitive to other sterilization methods evolving heat. We have chosen UV-C light sterilization to sterilize our electronics, since the gas and heat sterilization can damage our electronic components, such as the speaker and RaspberryPi 5.

Part B: Our automated pill dispenser is designed with key social factors in mind, particularly accessibility, healthcare disparities, caregiving, economic considerations, and digital inclusion. By ensuring timely medication intake through automated dispensing and scheduled notifications, the device supports individuals who struggle with medication adherence, such as elderly patients, disabled individuals, and those in underserved communities. It also alleviates the burden on caregivers by enabling remote monitoring, reducing stress, and allowing family members or healthcare providers to track adherence in real-time. We are also prioritizing accessibility in our web app design as it is user-friendly, adjustable to different screen sizes, and designed for individuals with limited technology experience. We are also ensuring privacy and security of patient health information by encrypting data. By addressing healthcare accessibility, caregiver support, and digital inclusion, the dispenser enhances independent medication management and overall quality of life.

Part C: Our pill dispensing device helps with economic factors by making sure people take their medication correctly, which can save money on healthcare costs. When people forget to take their medicine or take too much, it can lead to serious health problems that require expensive hospital visits or treatments. By reducing the amount of hospital visits, our product can reduce a user’s overall medical costs. We keep production costs low by using affordable medical-grade plastic. Also, we choose cost-effective, widely-available, and energy-efficient electronic components, such as the RaspberryPi 5 and servo motors. For sterilization, we use ethylene oxide gas and UV-C light, which are cheaper and safer for our materials compared to heat-based methods that could damage the plastic parts. Since our device is lightweight and compact, it’s easier and cheaper to ship, making it more accessible to our target users.

 

https://docs.google.com/spreadsheets/d/1A78EFYzDSM-yG8J1KksYfQ9CtJF7ld6q7F0CRFXgZSU/edit?usp=sharing

Final Design

Initial Design-compressed

MM Demangone’s Status Report for 2/15/2025

For this week, I had revised the components that we need for our design. I had drawn out several block diagrams and iterations of our design as we were optimizing our hardware. I have completed the medication Django form and model to be used in our web app and have pushed it to our GitHub. I also worked on the design presentation, namely the block diagram, solution approach, software implementation, hardware implementation, testing, and verification. Additionally, I will be presenting the design presentation in class on Monday, so I have spent time preparing for that presentation as well. I am on track with the schedule that we had set! Next week, I will complete MySQL database creation to store the users’ medications. Additionally, I will start writing some code for the RaspberryPi, so once it arrives, we will be ready to start testing and vetting the code. Lastly, I will work on the Design Proposal document with the rest of my team.

Final Design

High-level Block Diagram