Alena’s Status Report for 9/28

What did you personally accomplish this week on the project? Give files or photos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).

Personally, I implemented the initial code for voice commands and have a working prompt/response system using the SpeechRecognition library. The code is able to recognize when the user says “Hey Chef,” and can parse some specific commands that the user inputs through voice. I also used the pyttsx3 library to successfully generated prompts to respond to the user.

I was also able to start the code for the microphone integration onto the Raspberry Pi pico since our parts came in. I soldered headers onto both of the picos and the microphone board.

I also did some research with Kayla to finalize our web app structure and the frameworks we will be using for front end and back end development.

Is your progress on schedule or behind. If you are behind, what actions will be
taken to catch up to the project schedule?

In terms of voice commands, we are actually ahead of schedule because they took less time than imagined. However, we are slightly behind on hardware integration because we ordered our parts later, and the PCB layout still needs to be done. This will be the main focus for the coming week.

What deliverables do you hope to complete in the next week?

I hope to have a finalized PCB layout with Michelle so we can send it to manufacturing, and also finish the microphone and speaker initialization using the pico. A stretch goal will be to incorporate my previous work on voice commands with the microphone and speaker.

Team Status Report for 9/28

What are the most significant risks that could jeopardize the success of theproject? How are these risks being managed? What contingency plans are ready?

Latency is a main concern for the project, as latency significantly affects user experience, which is a priority for the project’s success. We are mitigating this risk by hosting the web app on a Raspberry Pi which will communicate with the Raspberry Pi Pico W on the glasses via local network, which is lower latency than communication over the Internet if we were to host in AWS. We are also prototyping with the voice commands and believe they will be within expected latency bounds. Contingency plans are the same in that we will look into larger, more powerful hardware for the glasses.

Were any changes made to the existing design of the system (requirements,block diagram, system spec, etc)? Why was this change necessary, what costsdoes the change incur, and how will these costs be mitigated going forward?

No design changes and no changes to the schedule.

 

Part A (written by Kayla)

As a hands-free cooking assistant, our project is designed to ease the cooking process as well as improve cleanliness in users’ kitchens. By helping to make recipes more readily accessible with clear step-by-step guidance, our project can enable and encourage more people to cook for themselves and their families, which can lead to people having healthier meals, saving money by eating out less, and living a more sustainable and fulfilling lifestyle overall. Additionally, the hands-free nature of the product helps to reduce contamination between foods, handheld devices, and potentially other surfaces maintaining a cleaner workspace and cooking environment. Because the product is targeted mainly toward home or amateur cooks, these areas are often peoples’ own kitchens in their everyday living spaces, so improved cleanliness in these areas can also be beneficial for peoples’ overall health.

Part B: (written by Alena)

“Hey CHEF!” addresses a growing societal trend of convenience, multitasking, and technological integration in daily life. As we increasingly adopt busy lifestyles, the ability to prepare meals efficiently while minimizing the need for manual interaction with devices can enhance time management and also reduce chaos in the kitchen. Additionally, the product can cater to a range of cultural cuisines and dietary preferences, encouraging inclusivity by allowing users from various backgrounds to explore different recipes and share them socially. By recommending recipes based on what users already have, it encourages resourcefulness and economic mindfulness, while also exposing users to new recipes that they may not have heard of.

Part C: (written by Michelle)

We believe that “Hey CHEF!” will be a product desired by consumers around the world. For as long as the need for food exists, cooking will too. Hence, tools that facilitate cook/prep time will always be in demand. “Hey CHEF!” aims to utilize the desire to cook with the desire to make it an easier, simplified process. To make a product that has economic potential, we aim to make the glasses lightweight, cost-friendly, and modular, making production on a larger scale simple. The glasses will reach a large audience by eventually allowing for recipe addition, and the easy-to-use interface will allow a variety of people of different skill levels to use our product.

Michelle’s Status Report for 9/28

What did you personally accomplish this week on the project? Give files or photos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).

  • Towards the first few days of the week, I ordered all the components after clearing them with the capstone advisor + TA. 
  • We received the Raspberry Pi Pico W’s on Wednesday and the other components on Thursday. On Friday, I confirmed that I would be able to communicate with Raspberry Pi Pico W by installing “Thonny” and running a simple LED test. Alena and I then distributed our parts (I took the LCD, Alena took the microphone + speaker) and one Raspberry Pi Pico W each for solo-testing purposes.

Is your progress on schedule or behind. If you are behind, what actions will betaken to catch up to the project schedule?

  • We are slightly behind our prototyping schedule, as we held off on ordering parts until after our meeting on Monday. We are about a week behind on prototyping, but because we schedule with 2-3 weeks of leeway, it is enough to catch up.
  • I am also well into designing a third iteration of the outer casing, and each iteration takes less time.

What deliverables do you hope to complete in the next week?

  • By next week, I am hoping to have code that communicates with the transparent LCD. I will also be syncing with Alena’s progress to finalize a schematic.
  • If the schematic is completed, I will work on making the PCB with Alena and developing a fully fleshed-out design for the outer casing of the glasses.

Alena’s Status Report

What did you personally accomplish this week on the project? Give files or photos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).

This week, I worked on the initial research and testing of the SpeechRecognition library. I was able to implement some code for speech-to-text conversion in Python using my computer mic. I also researched components for the PCB, as well as a suitable microphone to use. I also did some initial prototyping/code for word splicing, but that is subject to change as we progress with the design. We also finalized the plan for our project, creating a Gantt chart for deadlines.

Is your progress on schedule or behind. If you are behind, what actions will be taken to catch up to the project schedule?

My progress is mostly on schedule, but the PCB design is slightly behind schedule. Michelle and I will work on that in the mean time while parts are being ordered.

What deliverables do you hope to complete in the next week?

By next week, I hope to have a PCB designed and ready to send to manufacturing, as well as all necessary parts ordered for initial prototyping. I also hope to finalize which speech library we will use in Python, and iron out some details regarding word splicing.

Team Status Report for 9/21

What are the most significant risks that could jeopardize the success of the project? How are these risks being managed? What contingency plans are ready?

  • The biggest risk that could jeopardize the success of our project is the unknown latency we may experience between sub-modules of our design. We will mitigate these risks by researching multiple options for the best way to communicate from our Raspberry Pi Pico W to our web server, and the best ways to communicate within the web server. In the event that we cannot find a suitable solution, we may look into better hardware while sacrificing some size/weight constraints.

Were any changes made to the existing design of the system (requirements, block diagram, system spec, etc)? Why was this change necessary, what costs does the change incur, and how will these costs be mitigated going forward?

  • There were no changes made to the existing design of the system.

Michelle’s Status Report for 9/21

What did you personally accomplish this week on the project? Give files or photos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).
  • This week, I worked on finalizing the parts list for the initial prototype of our device. I looked into the transparent LCD and speaker while Alena looked into a microphone. As a group, we decided to use a Raspberry Pi Pico W as the microcontroller for our smart glasses.
  • Following these decisions, I created a Bill of Materials for the parts required in our prototyping phase.

  • I also began redesigning the external casing for the glasses. The design process is on-hold until Alena and I finish the schematic and PCB design.
  • The team and I also spent Sunday finalizing the presentation for our proposal. During this meeting, we set up our general deadlines for the phases of our project: Research, Prototyping, Development, and Testing. We created a Gantt chart to keep track of these deadlines.

Is your progress on schedule or behind. If you are behind, what actions will betaken to catch up to the project schedule?

  • My personal progress is on schedule, but I would like to get started on the schematic design for the components and order materials listed on our parts list by early next week.

What deliverables do you hope to complete in the next week?

  • By next week, I hope to complete the schematic of our glasses with Alena and design a PCB. Assuming we are on schedule, I hope to design a prototype casing around the newly designed PCB.

Kayla’s Status Report for 9/21

This week I created mockups for the web app UI using the Figma design tool as well as researched implementation options and their details for the different components of the web app, including the database, hosting, and web scraping. My progress is on schedule with the tasks laid out in the Gantt chart, and next week I will work on replicating the UI mockups and setting up AWS hosting infrastructure for the web app, with frontend code as a deliverable.

UI mockups

Web app research notes