This week I drew the hardware the block diagram with components and connections. I thought about our user interface and wrote some answers on our target play experience and the next steps in our work flow. I started working on the arduino control code for the dispensing mechanism of our machine, since this task is mostly separate from the game logic side. Our progress is on schedule but the team would like to work more on break to be prepared for any delay during the machine body build. For next week’s meeting I plan to have the rpi touch screen configured to display the basic mock text game, after that it needs to be integrated with the audio narration and modified for multiply game round mechanism according to our ux flow diagram.
Fei’s Status Report for Feb 22
This past week, I prepared the presentation for our team’s design review and worked partially on the game code for the challenge mode. However, I fell a bit behind due to the time spent on the presentation and two midterms.This week, I plan to focus primarily on the project, as the courses I had midterms for no longer require my immediate attention. Looking ahead to next week, I aim to complete the overall logic for the challenge mode and upload it to the newly arrived Raspberry Pi.
Min Ji’s Status Report for Feb 22
This week, I focused on finalizing the UX flow design and overall structure of how our vending machine would function, ensuring a smooth and open interaction process. The majority of my time was dedicated to testing and refining the AI narration system, assessing its effectiveness, and preparing it for integration. I successfully pushed my AI narration updates to our GitHub repository. Additionally, I verified and cataloged our hardware components to ensure we had all the necessary parts for the Raspberry Pi setup. In the process, I identified missing components, informed the team about what still needed to be purchased, and coordinated the next steps for hardware assembly. I also continued researching the spiral mechanism for candy dispensing, exploring potential implementation methods while considering mechanical constraints.
Progress is on track, but I am waiting for a teammate to upload her trivia questions to the shared Excel sheet so I can update the AI narration database accordingly. Leading up to the end of spring break, I plan to integrate the AI narration system with a speaker and Raspberry Pi, complete the narration database, and develop the standard mode into a minimum viable product (MVP). This will include implementing a 10-second timer countdown and enabling answer selection through physical buttons. My goal is to have the standard mode in a functional MVP state and ready for testing by the end of spring break.
Team Status Report for Feb 22
- 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?(written by Vicky)
So far one risk is how the unknown touch screen lag time will affect the player question-answering experience in the challenge mode, we plan to mitigate that by using one button for the user tap signal in the flappy bird logic if the touch lag time is too long. Another challenge is the integration of the project, for example so far our work division on the standard mode and challenge mode is separate. We also need to integrate the arduino motor driver side of the system with the rpi game side of the system. So we need to allocate additional time (1 week minimum before the set MVP date) after each mode is finished. We also faced the question of players being confused with how to navigate the interface and how to reset, so we need to have graphics on the screen display to show optional new player instructions. - 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? (written by Fei)
After receiving feedback from the design review presentation, we made some changes to our microcontroller choice and refined aspects of our design. It was apparent that our design was confusing for the audience. We decided to change the microcontroller because the previous option was not powerful enough for our design. Within our budget, the new selection is a better fit. This switch might delay some timelines until the new microcontroller arrives, but we’ve adjusted our plans to minimize the impact. - Provide an updated schedule if changes have occurred. This is also the place to put some photos of your progress or to brag about a component you got working. (written by Min Ji)
There haven’t been any big changes in our schedule so far. Instead, the following are the upcoming plans until the end of spring break week(~3/9):
- Assemble the rpi screen with the touch screen and buttons and upload the standard mode
- Write the arduino control code(motor + servo + lcd) for the dispense process
- Make sure the AI audio narration works with speaker + rpi
- Implement flappy bird game and upload it onto the rpi to test on touch screen
Vicky’s Status Report for Feb 15
This past week I contributed to designing the details of our gameplay logistics (how the system tracks&calculates user points) and the putting questions into the trivia question database, making the slides for our deisgn review presentation, optimizing the laptop-mock visualization of the game interface for our presentation. The progress on Rpi testing is behind due to shipment but this time is being used to build the software and control side of our system. For next week I hope to have finished testing on the rpi board and have the reset and dispense signal generated correctly.
Fei’s Status Report for Feb 15
This past week, I collaborated with my group to prepare the design presentation slides. Additionally, I identified the necessary components based on our needs and requirements, completed the Bill of Materials, and submitted all orders. I also entered questions into the trivia question database after drafting 100 trivia questions. My progress remained on schedule. For next week, I aim to refine the gameplay mechanics, incorporating Flappy Bird logic to enhance the user experience.
Min Ji’s Status Report for Feb 15
This week, as part of the design presentation preparation, I was responsible for the use case & requirements and the quantitative design requirements. In addition to group efforts, I worked on local testing of the audio narration system using my laptop. Specifically, I
- installed and configured espeak-ng, a text-to-speech synthesizer, using Homebrew on macOS.
- tested speech output by generating WAV audio files
- experimented with different voice settings to create a spooky theme voice for trivia
- created a test script to automate the process of converting trivia questions into speech output
Right now, my schedule is on schedule. I am waiting for the parts to come so that I can continue and integrate the text-to-speech into the Raspberry Pi and speaker.
In the upcoming week, I am planning to begin writing 100 trivia questions and research potential libraries for smoother voice modulation. Assuming I have all the parts, I plan to conduct initial narration tests on the actual hardware ensuring clarity and correct volume, and modify the test script.
Team Status Report for Feb 15
Part A: … with respect to considerations of public health, safety or welfare. (written by Fei)
Our machine is designed with both physical and psychological well-being in mind. By incorporating an interactive trivia experience, it encourages mental engagement, making it valuable in educational and social settings. Additionally, the voice and button-based interaction enhance accessibility, ensuring individuals with different needs can participate easily.
Safety is a key priority in our design, as vending machines must function reliably without posing risks to users. To ensure stable operation and prevent electrical hazards, our machine is powered by a 12V DC adapter. The structure, made of MDF boards and aluminum tubes, provides durability while keeping the device lightweight and stable.
Part B: … with consideration of social factors. (written by Min Ji)
Our trivia vending machine unites people in that it makes socializing exciting and enjoyable. Whether through teamwork or friendly rivalry, it’s an excellent method of breaking the ice in any environment. Trivia games also tend to make people bond naturally—whether buddies are collaborating to come up with correct answers or even playfully challenging each other. It’s a perfect way for colleagues, family members, or even strangers to bond too. Since the trivia topics can be fully customized through an online platform(website to be built), the game can be appealing to a wide range of interests, cultures, and ages, thus making it inclusive and versatile.
Beyond entertainment, our trivia machine also possesses real educational and team-building value. It can enhance learning as an interactive and engaging experience in schools, reinforcing what has been learned in a fun way. In the workplace, it is a casual team-building activity, so colleagues get to interact and think as a team. During community events or social gatherings, it gives people something to talk about and do, so the atmosphere is more lively and interesting. By combining education, competition, and openness to all, our product makes social interactions richer and more enjoyable.
Part C: … with consideration of economic factors. (written by Vicky)
Our product’s portable dimension and use in entertainment space makes it a fast moving consumer good. If launched to market it can be sold in chain department stores as a party game or a common gift option. The assembly in the production part will require some manual labor. During use of our product, the user needs to have access to network connection in order to log on to the website and enter their customized questions. The user also need to supply their own candy/treat refill for future dispensing.
- 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? (written by Vicky)
One development/change we encountered this week was to adopt the waterfall project management method, implement and update our product versions sequentially, start with a simple crude prototype and add more features gradually. This means for the following 2 weeks we aim to have both the text-based game and touchscreen game working with a simple interface. After that we will then optimize the visual interface and build the website for question customization. We estimate the making a website will take up a bulk of time and decided to implement that after finishing the game part so it does not hold up our progress.
2. 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? (written by Fei)
We have finalized more details of the design, ensuring everything aligns with our project goals and requirements. However, no changes have been made to the existing design of the system this week. The entire team is working seamlessly toward delivering the final product.
3. Provide an updated schedule if changes have occurred. This is also the place to put some photos of your progress or to brag about a component you got working. (written by Min Ji)
We modified the current status update of the tasks, and new tasks will be started in the upcoming week. A shared document of the trivia questions(approx. 300 questions in total) was made so that each team member could write questions for the sports, science, and entertainment category respectively.
Link to our Gantt Chart: sweeTrivia Gantt Chart
Link to our trivia questions database: Trivia Questions Database
Vicky’s Status Report for Feb 8
This week I contributed to our team’s drafting of the proposal presentation slides, the modified gantt chart schedule, bill of materials, and preliminary separation of working modules. I prepared speaking for our team’s proposal, created the git repository, and wrote a test program for the standard mode text game in both python(on laptop) and micropython(to be tested on rpi next week). On schedule. I will synchronize with my teammates and work together on building the question database next week. Next week I hope to deliver the complete question database together with teammates, and present my progress on programming the rpi control for the standard mode game.
Fei’s Status Report for Feb 8
Over the past week, I focused on preparing the proposal presentation slides and collaborating with my team to refine our idea and define the use cases through multiple discussions. After the presentation, we met with the professor to review feedback and clarify the next steps in the project. Additionally, I worked with Vicky to revise the project timeline, ensuring a schedule that aligns with our current ordering status. I also reviewed the source code for controlling the candy dispensing mechanism, checking the parts that matched our needs and requirements. My progress remains on track for this week. For next week, I aim to complete the BOM and draft the trivia questions.