The goal for this week was to plan how I will share the project, reflect on what is finished
and what still needs work, and communicate the main lessons from the final project development.
The general workflow was:
Summarize the current state of the pill dispenser and the progress made during final project development.
Define what is working, what is not working yet, and what questions still need to be resolved.
Plan future improvements, possible versions, and ways to continue the project after Fab Academy.
Choose a license and describe how the documentation, files, and code will be shared.
Project essence
My final project is a 16-day pill dispenser made to support an elderly user during a medication routine.
The device does not drop pills automatically when the alarm starts. First, the buzzer sounds and the OLED
shows the alarm. Then the user presses the blue button to confirm they are present, and only then the
stepper motor rotates the carousel one compartment so the pills fall by gravity.
The current version is much more complete than my first dispensing test, which only moved but did not
actually dispense. Now the design includes the mechanical carousel, the gear transmission, the removable
acrylic cover with magnets, the CNC-cut triplay base, the XIAO ESP32-C6 hub board, the RTC, the OLED,
the passive buzzer, and the button interaction.
Main reflection
I learned a lot about modularity, tolerances, and designing while thinking about the electronics.
There were many calculation mistakes, especially around size, gear motion, and how much space the
components really need. Even with room to grow, this version is a big step forward because it moves,
aligns, and dispenses through an actual mechanism.
Plan to share the work
I want this project to be understandable for two types of people: Fab Academy reviewers who need to
see the full technical development, and families or caregivers who need to understand how the dispenser
could help in daily life.
Fab Academy site
I will publish the design process, weekly decisions, final files, firmware, electronics, tests,
and final video on this documentation site.
FabCloud repository
I will upload the source files: Onshape exports, STL files, DXF files, KiCad files, and Arduino code.
Final video
The video will show the alarm, the OLED, the button press, the carousel movement, and the pills falling.
Presentation slide
The slide will focus on the final mechanism, the user flow, and what changed from the first concept.
Local demo
I will explain the project at Fab Lab Puebla and show the working prototype with the real electronics.
Future sharing
If the next version becomes more reliable, I would like to share it as an open-source assistive device.
What tasks have been completed?
Task
Status
Notes
Define final scope
Done
Reduced from 31 days to one 16-day ring.
Carousel CAD
Done
16 compartments, gravity dispensing opening.
Gear system
Done
32-tooth ring gear and 8-tooth pinion, module 2.
Acrylic cover
Done
Laser-cut cover held by magnets.
Triplay base
Done
CNC-cut structural base.
Custom PCB
Done
XIAO ESP32-C6 hub board.
Motor test
In progress
Stepper moves with AccelStepper and advances by 512 steps.
Final firmware
In progress
RTC, OLED, buzzer, button, and stepper are being integrated.
Offline caregiver interface
Pending
Based on Week 11 networking work; may be integrated after the main mechanism works.
Final testing
Pending
Needs repeated dispense tests with real pills.
What's working?
The project scope is clearer and more realistic than the first 31-day idea.
The 28BYJ-48 stepper works with the ULN2003 driver using AccelStepper.
The OLED SH1106 and RTC DS3231 work together on the I²C bus.
The buzzer can play an alarm pattern and a confirmation sound.
The magnetic cover makes refilling easier because it can be removed without screws.
The CNC-cut triplay base gives the project a stronger physical structure.
What's not fully solved yet?
The final dispense reliability still needs repeated testing with different pill shapes.
The optional line follower or IR sensor still needs a clear role in the final behavior.
The offline web interface from Week 11 is useful, but it should not distract from finishing the core mechanism.
The gear and carousel tolerances still need adjustment if the mechanism rubs or skips.
The buzzer volume depends on the enclosure and final placement.
Future opportunities
Modular rings
Turn the current 16-day ring into removable modules. Two rings could cover 32 days with one dose.
Two daily doses
Four 16-slot rings could cover morning and night medication for a full month.
Caregiver interface
Expand the offline ESP32 interface so caregivers can set alarms, check logs, and reset schedules.
Pill detection
Test the line follower, IR sensor, or another simple sensor to confirm if pills actually fell.
Better tolerances
Rework the carousel and gear fit after more physical tests. This is where the project can improve the most.
Cleaner product design
Make a stronger enclosure, hide cables, improve the refill path, and make the buttons easier to read.
What will happen when?
Moment
Work
Goal
Before final assembly
Finish prints, check magnet alignment, check gear movement by hand.
Make sure nothing rubs before powering the motor.
Electronics test
Run OLED, RTC, buzzer, button, and stepper from USB-C power.
Confirm the XIAO can run the full system without reset.
Mechanism test
Move one compartment at a time and verify the opening alignment.
Confirm 512 steps works with the real gear system.
Dispense test
Load test pills and run several alarm-to-dispense cycles.
Check if the pills fall without getting stuck.
Documentation
Record video, take final photos, upload files, and write the final page.
Communicate the project clearly, including what works and what still needs work.
After Fab Academy
Develop modular rings, caregiver interface, and better sensing.
Move from prototype to a more reliable assistive device.
What have I learned?
Modularity sounds simple, but it changes everything: the size, refill method, motor position, number of parts, and even the electronics.
Tolerances matter more than the drawing: a gear can look perfect in CAD and still rub, skip, or need more clearance after printing.
Electronics must be considered while designing the mechanism: wire access, pin count, screen placement, and motor power affect the shape of the object.
Programming became an iterative learning process: I am still learning how to program, so I developed the code step by step with AI support. I used it to understand libraries, debug errors, and combine the RTC, OLED, buzzer, buttons, and stepper motor without losing track of what each part was doing.
Smaller scope can be better: the 16-day ring is less ambitious than the first 31-day version, but it is much more possible to finish and test.
Real progress is not linear: I changed mechanisms many times, but each failed idea helped define the final one.
Dispensing is harder than moving: my first prototype only moved. This version is closer to the real problem because it actually tries to release pills.
License choice
For this project I would use a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
license, also written as CC BY-NC-SA 4.0.
This license fits the current state of the pill dispenser because it is still a prototype and not a certified
medical product.
Attribution
People can use or adapt the files, but they must credit me as the original creator.
Non-commercial
Others can learn from it, build it, or modify it, but they cannot sell it as a product without asking first.
Share alike
If someone modifies the design and shares it, their version must use the same license.
Safety note
This project is an educational prototype. It should not be used as a medical device without further testing,
validation, and responsibility from the person building it.
The documentation, CAD files, fabrication files, and images would use CC BY-NC-SA 4.0.
For the firmware, I would keep the same spirit and share the code openly with attribution,
while making clear that it is provided as prototype code.
I will share the project as an open Fab Academy documentation package: files, photos, code, videos,
tests, and honest notes about what still needs improvement. The goal is not to present it as a finished
medical product, but as a working assistive prototype and a base for future development.