{"id":254,"date":"2025-06-10T00:05:39","date_gmt":"2025-06-10T04:05:39","guid":{"rendered":"https:\/\/wp.stgeorges.bc.ca\/aidenh\/?p=254"},"modified":"2025-06-10T00:05:39","modified_gmt":"2025-06-10T04:05:39","slug":"end-of-the-year-personal-project-finale-fusion-final-project-pt-3","status":"publish","type":"post","link":"https:\/\/wp.stgeorges.bc.ca\/aidenh\/2025\/06\/10\/end-of-the-year-personal-project-finale-fusion-final-project-pt-3\/","title":{"rendered":"End Of The Year – Personal Project Finale – Fusion Final Project Pt. 3"},"content":{"rendered":"\n

This post is my final blog post for the Fusion 10 Cohort Program. In this post I will be showing you my product, SleepPlugs\u00a9<\/strong>.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

To retrace our steps, let’s go over what our original problem was.<\/p>\n\n\n\n

Our problem:<\/p>\n\n\n\n

\n

Earplugs lack features; sleep earbuds are not cheap<\/strong><\/p>\n<\/blockquote>\n\n\n\n

Foam and silicone earplugs that can be bought in bulk are cheap, easy to get, comfortable for some but may cause irritation due to their low quality and lack extra features. On the other hand, sleep earbuds on the market are quite expensive ($30~$200), may be uncomfortable for side sleepers, can be used as normal earbuds during the day, and usually have active noise cancelling or play music.<\/p>\n\n\n\n

Constraint and Scope<\/p>\n\n\n\n

For the product, I’m aiming for people who have trouble sleeping in loud environments as well as people who have trouble waking up to their alarm. IT should be cost-effective, affordable, and simplistic. It will prioritize sound cancellation, comfort, and cost.<\/p>\n\n\n\n

For this project, however, I’m more constrained by time and skill, so I’ve decided to focus on the electronics and coding side of things, as this is a STEM course. The time frame for my project is 3 months and I am limited to using fairly large Arduino boards and foam earplugs for the prototype.<\/p>\n\n\n\n

As I mentioned, this project’s aim is to maximize sound cancelling, comfort and cost, so I think success would be defined as how noise-cancelling it is (decibels reduced), how comfortable it is (ergonomics and irritation), and how cost-effective I can make it (simplicity of parts).<\/p>\n\n\n\n

Design Solution<\/p>\n\n\n\n

With that out of the way, let me show you a couple of my original design solutions and the one I eventually chose as my final design.<\/p>\n\n\n\n

I was originally going to design an actual pair of silicone earplugs with small electronics that were going to have active noise cancelling at a certain range and would allow really loud noises i.e. alarm clock ringing, to go through. This product was really redundant and I didn’t really need the selective active noise cancelling, as earplugs already block out sound, and I could actually integrate the alarm into the earbud. I also realized I didn’t actually have to make the thing true to size – I just needed to showcase the circuit.<\/p>\n\n\n\n

So after some deliberation and further research, I ended up with my current design, a pair of wired foam earplugs with vibration motors embedded in them connected to an Arduino Uno and a HC-05 Bluetooth module. The entire board was originally going to be just an ESP32 microcontroller, as it combined the both in a super small package, but the driver just didn’t download, so I scrapped it.<\/p>\n\n\n\n

\n
\"\"<\/figure>\n\n\n\n

The prototype – the Arduino Uno, breadboard, HC-05 (on the right), and the two earplugs<\/em><\/p>\n<\/div>\n\n\n\n

\n
\"\"<\/figure>\n\n\n\n

An ESP32 in comparison to a human hand, much smaller than an Arduino Uno, a breadboard, and a HC-05 all together.<\/em><\/p>\n<\/div>\n\n\n\n

\n
\n
\"\"<\/figure>\n\n\n\n

The circuit diagram of the prototype.<\/em><\/p>\n\n\n\n

To control the alarm, I also changed my original plan of having an Arduino RTC and an LED display on the breadboard itself to controlling it via a mobile app. The mobile app has a simple design with a Bluetooth devices list, a button to pick your time, a button to set the alarm, and a button to turn it off.<\/p>\n\n\n\n

\"\"<\/figure>\n<\/div>\n\n\n\n

A screenshot of the app I built with MIT App Inventor<\/em>.<\/p>\n<\/div>\n\n\n\n

\n
\"\"<\/figure>\n\n\n\n

Code of the app in MIT App Inventor<\/em>.<\/p>\n<\/div>\n\n\n\n

Project Planning<\/p>\n\n\n\n

I planned out my project using Notion.<\/a> Using it I outlined the steps that I needed to build the prototype, from preliminary research to gathering the materials. I set some deadlines for myself for the prototype, although I didn’t really follow them that well. I planned to start building the prototype in April, but it was delayed until May. I had also changed my plans midway while debating if I should use the ESP32 and looking for prebuilt Arduino controller apps. I had to rush a little to finish the Arduino and app as I didn’t expect them to take that long.<\/p>\n\n\n\n

I needed to learn about how to use the HC-05 module during the project. It was kind of complicated and inconsistent but I got it to work. I had to also learn how to use MIT App Inventor’s Alarm and TimePicker. I’ve had experience with App Inventor and it was easy to use, it was just kind of counterintuitive with its logic.<\/p>\n\n\n\n

BOM and Costs<\/p>\n\n\n\n

For my project, I needed:<\/p>\n\n\n\n