Posted on

Gina’s Status Report 3/15/25

This week, I focused on sourcing and researching components needed for the LED strip circuitry. Specifically, we required a signal and power booster to meet the 5V requirement of the LED strips while operating on a 3.3V system. Although I had planned to begin LED integration, our ESP32 was confiscated by TSA at an airport, preventing direct testing. In the meantime, I wrote and prepared code in the Arduino IDE to facilitate testing once we receive a replacement next week.

The project remains on schedule. For the upcoming demo, we plan to integrate the LED system with NFC scanners and tags. This will allow the system to correctly recognize stickers on objects placed in different zones of the pad and send real-time notifications to the frontend.

Next week, I aim to finalize the LED setup by cutting the strips into four sections, each corresponding to a specific zone of the pad. The goal is to enable the LEDs to change colors—green, yellow, or red—based on backend notifications.

 

Posted on

Sarah’s Status Report for 3/15/25

This week, I focused a lot on the software backend logic and getting the skeleton set up for that. I was able to set up fastAPI and incorporate the logic we needed to communicate with the esp32 microcontroller so that integration can begin next week. I also developed a test script to ensure it was working properly so that we were able to fill our firebase database with dummy data.

Once the database had enough data with the proper fields we wanted in it, I started working more on the frontend and connecting our React Native app with firebase to display the items in the database.

The progress is currently on schedule.

In the next week, I hope to start integration with the hardware so that data from the esp32 microcontroller works with fastAPI in order to populate the database, and fastAPI can notify the esp32 when to change the LED colors.

Posted on

Team Status Report for 3/15/25

The most significant challenge we encountered this week was our esp32 microcontroller being taken away by TSA at the airport. This meant that our testing and integration process was delayed, and we had to borrow other microcontrollers to test with. We mitigated these risks by quickly ordering more esp32s and picking them up this week. We will be using these to implement and test our NFC scanning and other sensors for upcoming demos.

While connecting the NFC physical scanner to our esp32, the microcontroller was not able to detect the scanner so we suspect that the scanner must also be powered by 5V instead of 3.3V. In order to account for this, we are going to use the power booster (which has been ordered) on the NFC scanner as well.

No significant updates to the schedule have been made, we were able to overcome our loss of esp32 by quickly ordering another one and borrowing others. For the upcoming demo, we plan to integrate the LED system with NFC scanners and tags with our current prototype. This will allow the system to correctly recognize stickers on objects placed in different zones of the pad and send real-time notifications to the frontend.

Posted on

Gina’s Status Report for 3/8/25

This week, I completed the rapid prototyping of 4 pressure sensors and an LDR in Arduino IDE, with strong initial thresholds set for sensitivity. The pressure sensors are connected to GPIO pins (32, 33, 34, 35), and I’ve assigned names to each sensor for easy identification in the serial monitor. The system checks for pressure detection, and prints the sensor name and value when pressure is applied. For the light sensor, I used a TEMT6000 on GPIO 26, and set a threshold to detect changes in the light status. The sensor was sensitive enough to detect when my hand came closer to cover the circuit, simulating the fridge door closing, but it was not affected by the LED light. I’ve also connected an LED to GPIO 25 to indicate the light status — if the light is on, the LED lights up, and if the light is off, the LED is turned off. A demo video is shown here.

Additionally, Jess, Sarah and I completed the design report by Friday. I mainly focused on research and writing on hardware components, justifications, battery life, problem statement and solution overview, and system diagrams.

Overall, my team and I are making steady progress and are on schedule.

Some roadblocks included the late delivery of the LED, NFC tag, and NFC scanner, so we weren’t able to integrate everything over Spring break. However, I plan to integrate the LED system with Jess next week. Even further, with Jess’s progress on the Bluetooth (BLE) functionality and WiFi setup for the ESP32, I will be able to help put together our initial prototype + real LED strips with Wifi data transfer mechanism, which will be key for moving forward with the integration.

Posted on

Jess’s Status Report for 3/8/25

This week, I focused heavily on the design report, ensuring that our documentation clearly outlines our approach and design decisions. Over spring break, I made significant progress on the Bluetooth (BLE) functionality, successfully getting it up and running on the ESP32. I also added the device naming feature, which will help with easier identification and pairing in our system. After finalizing BLE, I shifted my attention to setting up WiFi on the ESP32. I began working on getting it up and running and will continue refining this into next week to establish a stable connection for our system.

Overall, we are making steady progress and are on schedule.

Looking ahead, I plan to continue working on setting up WiFi connectivity and ensure that we can properly reliably transfer data over our WiFi connection. After that, since we have now received our NFC tags, I can also begin testing and setting up that connection.

 

Posted on

Sarah’s Status Report for 3/8/25

This week, I put a lot of time and effort into the design report. I completed the software portions of the report and system design diagrams. Throughout the report, I went into depth on the exact frameworks we would be using and what their purposes would be. In addition, a lot of research was done on how to integrate the software with the hardware features, particularly the NFC scanning. Finally, the developer tools were set up for React Native and the app was connected to Firebase with a project created in order to set up the database.

Our progress is currently on schedule.

In the next week, I hope to finish up most of the basic skeleton frames and pages for the frontend. I also want to start basic functionality implementation, particularly in regards with the integration between the hardware pad and software database.

Posted on

Team Status Report for 3/8/25

The most significant risk for our project right now is the user-flow for the NFC tags and the technical integration logistics. To allow NFC scanning in the app interface, we are allowing users to scan the NFC tags using the built-in scanner inside their phone. However, we need to be able to integrate this feature with our software backend. This integration will be different from the NFC scanner integration on the hardware pad. The challenge in this feature of our project is having two methods of NFC scanning and integrating both methods into the software.

No changes were made to the existing design of the system but we fully decided on bluetooth for the pairing between the device and physical pad. The implementation for this feature has been started.

No changes to the schedule have occurred.

Currently, we have the basic circuit prototype built with the pressure sensors and light detecting sensor working with the ESP32 microcontroller. In addition, we have XCode and the emulator working to test our software and have started on the React Native frontend. Firebase has been connected with React Native to start with interactions with the database. Finally, the integration has also been started, with bluetooth pairing between the device and physical pad implemented and tested.

Part A written by Sarah Yang

Our product meets global factors by addressing the universal challenge of food waste through a smart tracking system that transcends cultural barriers. This silicone pad provides a solution in varying regions, from wealthy urban center to more rural areas where food waste presents environmental concerns and economic loss.

GlowFresh offers a technology solution that can be adapted across price  points and in varying environments, from fridges to workshops and even labs. The pad also has minimal language dependency as the visual LED notification system overcomes any literacy and language barriers. This makes it accessible for users regardless of their educational background or native language.

Part B written by Jessica Chan

GlowFresh addresses the global issue of food waste by helping individuals and businesses track food freshness more effectively. Food is deeply tied to culture, tradition, and community, yet managing perishable goods efficiently remains a challenge. Our smart silicone mat, with pressure sensors and LED indicators, enables users to make informed consumption decisions.

Cultural factors shape our design, as food waste habits vary across communities. In regions where food scarcity is a concern, minimizing waste aligns with financial and ethical values. GlowFresh promotes sustainability while ensuring accessibility through an intuitive app. By merging technology with cultural values, our solution encourages responsible food consumption worldwide.

Part C written by Gina Seo

GlowFresh helps reduce food waste by offering an intuitive, color-coded visual map of food expiration in real time, minimizing spoilage and encouraging better food management. This automated tracking eliminates the need for manual logging or reliance on expiration dates, preventing edible food from being discarded and reducing landfill waste. The use of eco-friendly materials, like food-safe silicone mats, aligns with sustainable practices and further supports environmental responsibility. Silicone, known for its durability, reusability, and non-toxic properties, contributes to a longer lifespan for the product and reduces the environmental impact of frequent replacements.

In addition to these features, GlowFresh’s cloud-based syncing with the app allows for seamless inventory management and expiration notifications, helping users avoid over-purchasing. By reducing food waste, which is a significant source of methane emissions from landfills, GlowFresh supports more sustainable consumption patterns. The combination of durable materials and smart technology offers a comprehensive, eco-friendly solution to food management, ultimately contributing to both resource conservation and waste reduction.

Posted on

Jess’s Status Report for 2/22/25

This week, I focused on finalizing our design slides and worked with Sarah to review the hardware components for our presentation, ensuring that everything was clear and well-documented. After receiving feedback, I shifted my attention to researching how to pair our pad with our app, with Bluetooth emerging as the most viable option. Additionally, as a team, we decided to transition from force sensors to weight sensors for better accuracy and reliability. To support this change, I began researching weight sensors that would best fit our design requirements.

Overall, we are on track, but we want to accelerate our progress to stay ahead of upcoming deadlines. Right now, we are waiting for our LEDs to arrive—once they do, we can begin assembling version 0 of our system. This initial build will allow us to test the core functionality and ensure that all components integrate smoothly.

Looking ahead, I plan to start working on the design report since the deadline is quickly approaching. At the same time, I will begin building with Gina so we can have a functional prototype before spring break. Having a physical version of our system will give us a clearer understanding of any potential challenges and allow us to make necessary refinements early in the process.

Posted on

Gina’s Status Report for 2/22/25

This week, I focused on finalizing our design slides and collaborated with Jess and Sarah to thoroughly review our hardware components for the presentation. We ensured that all elements were clearly documented and that our explanations were concise and well-supported. Additionally, after internal discussions and consulting with a Master’s-level Mechanical Engineer experienced in working with pressure and weight sensors in various projects, we decided to transition from force-sensitive resistors (FSRs) to weight sensors for greater accuracy and reliability. To support this shift, I began exploring different weight sensor options that align with our design needs. However, we are concurrently testing pressure sensors to validate our decision, as we have acquired square and small circle pressure sensors from the Ideate lab for evaluation.

Our decision to move away from pressure sensors stems from their inherent limitations in detecting stacked items. Pressure sensors measure force per unit area, meaning that if the added item distributes its weight over a large surface, the overall pressure change might be too minimal to register accurately. This could lead to unreliable or inconsistent readings. In contrast, a load cell strain gauge directly measures total force applied, making it far more effective at detecting subtle weight changes due to stacking. By using a load cell, we can ensure a much more precise and responsive detection system, which is crucial for our application.

In addition to refining our sensor choices, I addressed concerns regarding the fabrication of our electronics with FDA-safe silicone. On Thursday, I met with Cody from Ideate to discuss the scope of our project, our progress so far, and the feasibility of using food-safe silicone for the final product. We received great news—facilities are available to help us create silicone molds using FDA-compliant materials, as the Creative Soft Robotics class is currently working on similar projects involving silicone mold printing. Cody demonstrated how straightforward the process would be, as long as we finalize the sensor layout.

The decision to use a weight sensor aligns well with this fabrication plan, as we can calibrate it precisely to account for any pressure applied by the silicone casing. Additionally, Cody helped us select free acrylic sheets that I can laser cut (since I already have clearance for laser cutting) to create plates for sandwiching the strain gauge weight sensor. This setup will provide a stable and effective means of integrating the sensor into our final design.

Looking ahead, I plan to begin drafting the design report since the deadline is quickly approaching. Simultaneously, I will start assembling the prototype with the team to ensure we have a functional version before spring break. Having a physical build will give us a much clearer understanding of any potential integration challenges, allowing us to refine our design early in the process. We’re making steady progress, but accelerating our pace now will help us stay ahead of upcoming deadlines.

Posted on

Team Status Report for 2/22/25

The most significant risks to our project currently is deciding how to connect and pair the physical pad to the user device. This risk is being managed as we have come up with a few methods, such as bluetooth and are researching how to implement it.

We made a few slight changes to our design, particularly in the hardware where we have decided to implement a booster. This is needed as the LED inputs only take 5V data signals but the ESP32 microcontroller outputs 3.3V. Thus, we are using the booster to step up the voltage to the appropriate level. Another change we’ve made is using weight sensors instead of pressure sensors. This way, when we have stacked items, the sensors will detect a change in weight whereas pressure sensors won’t. The operation of the sensors themselves are relatively similar so our design doesn’t have to change to adjust.

No changes to our schedule have been made yet as our team is still on track.

We worked a bit on rapid prototyping this week and are finishing it up. We have used a website online to mimic our basic circuit and ensure basic functionality is working :