Posted on

Wen Hui’s Status Report for 2/8

I conducted research on the different LCD and compared their specifications. I also researched about the libraries to use for the RPi and ESP32 / Pico in terms of UART, I2C and SPI communication. I also wrote the implementation flow for how the embedded devices would communicate with one another.

I am currently on schedule.

In the next week, I hope to get started on writing the code for the Rpi after finalizing the parts list and procuring the microcontroller + LCD for the blocks.

Posted on

Team Status Report for 2/8

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 most significant risk at this point is the communication between the block’s microcontroller (Pico/ESP32) and the central microcontroller (Rpi5). The block should be able to receive the word accurately from the central microcontroller. This risk is managed by implementing and testing the most basic UART communication protocol first before implementing additional features like updating the LCD display when the correct answer is submitted.

 

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?

  • During our meeting this week, we discussed our preliminary parts list, mainly focusing on how the components are connected together within the block and the choice of the LCD.
  • We found the 9V battery, battery holder and multicolor touchscreen LCD screen with integrated ESP32. We decided to consider the option of the LCD screen with integrated ESP32 to reduce the work required to create a custom PCB since the product already comes with a PCB that connects the LCD to the ESP32. It also opens up opportunities for us to add in extra features like touchscreen capabilities or wifi communication with the central Rpi. However, there might not be an LCD of the appropriate dimensions and it is unclear if there is sufficient documentation to support our integration of the advanced LCD screen. Our alternative is to fall back on our original design of using a Rpi Pico + standard LCD screen + custom PCB.

 

Provide an updated schedule if changes have occurred.

  • If we do decide to purchase the integrated LCD with ESP32, we would not have to create a custom PCB, hence eliminating the need for the PCB design, testing and fabrication processes in our schedule.
  • Moving forward, we are going to conduct more research on the other LCD options available. We will also be doing a CAD model of all the components and decide on the block dimensions after we have procured the individual components so that we know the exact dimensions and how they would fit.