Team Status Report for 4/26/2025

The most significant risk that could jeopardize the project is the SDcard becoming corrupted right before the final demo. We think that we should boot up a spare, just in case it does become corrupted. No further changes were made to our design that we haven’t already mentioned. Everything is working now, except for the load cell amplifier, which we are continuing to work on.

We performed the following unit tests:

  • Bluetooth messaging between client and server script
  • Web socket messaging between client and server script
  • Dispense button decreasing the quantity left and tracking when taken
  • Servo motor moving 180 degrees, and moving it 180 degrees multiple times
  • Reading “snack” weight off of load cell
  • Playing speaker audio
  • OAuth navigation
  • Google Cal API adding correctly to your account’s google calendar
  • Sending an email at specific time
  • Each web app page rendered correctly on each screen size
  • Accessing the web app across multiple browsers
  • Dispensing pills consecutively (3+ times) on each dispensing compartment 
  • Email notifications are sent based on the user’s inputted timezone (not our timezone)

We performed the overall systems test:

  • Clicking the dispense button dispensed a pill, moves servo, and play speaker audio
  • 3 unique users, each with their own medications, cannot see or access any medication besides their own
  • Adding/modifying/deleting pills and users are accurately updated in mySQL (and email notification as appropriate)
  • Flowing through the web app progression with all screen sizes

Findings and design changes from tests:

  • Adjusting the size of widgets on the web app, to make sure they are accessibility friendly
  • Switching from Bluetooth to web sockets as bluetooth is not supported on safari
  • SSL and certificate, as you could not access the web app on Chrome without this
  • Installing a pipe in the dispensing compartment to avoid pills getting stuck
  • Adding padding into the rotating discs to decrease their volume, as smaller pills tended to “collect” in the big disc slots
  • Recording the servo motor’s position (adjusting the pill model in the web app) so it can rotate 180 clockwise, 180 counter clockwise, etc.
  • Potentially removing the load cell amp and load cell if it continues to be noisy

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

This week I worked on the web app as well as the load cell amplifier. I modified the displays of some notifications on the web app, and added the email feature to be sent every time a user adds a new medication. I also flushed out all of the bugs for the automated email feature. For the load cell amplifier, I had soldered it and tested it on both the RPi5 and the arduino. Additionally, I worked on the poster, finishing the product pitch, system architecture, system design, and system evaluation. We still are having trouble with the load cell amplifier, which puts us a bit behind, but we have already talked to Professor Qin about it, and he said it was alright if it needs to be taken out. Next week, I plan to work on the load cell amplifier, finalize the presentation and paper, and prepare for the final demo.

Team Status Report for 4/19/2025

This week our team worked on the physical housing. MM bought supplies, Taylor installed pipes, and Aneesha tested the new design. Aneesha did testing on the dispensing and MM did testing on the software application. Taylor did testing on both the hardware and software systems and spent time designing the new dispense system. Aneesha and MM worked together on testing the load cell on an arduino. The whole team worked on the presentation. The biggest challenge we faced was the load cell amplifier still not working. MM ordered another load cell amplifier, and is still waiting for it to arrive. However, at this point, it may need to be removed from the design entirely. Additionally, pills kept getting stuck in our original funnel design, so we decided to switch to a pipe-shape instead. This fixed our issue, and we have adapted our structure accordingly.

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

This week I had worked on the load cell amplifier issue by writing code for an arduino and testing the load cell with Aneesha. Unfortunately, this did not work, and we will need to change our design. Additionally, I figured out how to make our web application accessible on Google Chrome by creating a certificate and using wss. I fixed some coding bugs, such as a user’s personal alerts being the only alerts to pop up, sizing across different size screens (phone), and general bugs as they came up. I also went shopping to buy pipes for our project, as we had to do a change in design. Next week, I plan to solve some additional software bugs (overpopulation in google calendar when editing a form, not automatically saving the disposal time, being able to delete a pill). If the load cell amplifier arrives, I can work on that, and hopefully this issue no longer persists. Besides the load cell amplifier dilemma, everything is on track.

I have learned a lot of new tools and skills in this project. I gained familiarity with the RPi, as I have not worked extensively with it. Additionally, it was my first time working with the load cell, load cell amplifier, and speaker. I did learn those skills as well. There were a few software packages and deployment add-ons that I have never used before: celery, celery beat, installing certificates. I learned about all of these tools through the internet, primarily through google search or AI engines. I have links commented throughout the github of the resources that I referred to.

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.