Week 2

In week 2, we received the components and are now commencing the practical implementation. Preliminarily,  we created a schematic diagram of the circuit connections on the simulation website. Although this website does not have the Arduino chip model we are using, the schematic diagram still serves as a valuable reference for connecting our circuit.

schematic diagram：




In the code section, we downloaded the U8glib library and quickly compiled the code segments for several individual components based on reference code.

code：



However, we also encountered some unexpected setbacks, such as the interface of the OLED display we ordered not matching our expectations, necessitating a replacement. Additionally, the Arduino Nano ESP32 has fewer pins than anticipated, which is insufficient to support our idea of using LED lights to display seat status. It was also found that the operation pins of the Arduino Nano control board and the ESP32 for the display screen were in different positions. After testing, the A4 and A5 pins of the Nano were used for connection. Nonetheless, we are continuously adjusting our plans according to the actual situation. We have already connected the other hardware components except for the OLED screen, and we unanimously agree that the screen's display function is sufficient to indicate seat availability. Abandoning the LED bulbs will not affect the core functionality of the seat occupancy detector.

As for tackling the challenge of designing the app, we found a method through literature review and case studies to implement app functionality on a computer using an Android virtual machine. We are prepared to put this into practice next week.



Comments

Post a Comment

Popular posts from this blog

Week 4

Image
Week 4 was the most crucial time for our project.  Only the screen test code displays when running; the complete code fails to display on the screen. Due to unknown reasons, the port automatically disconnects from the control board after uploading the code from Arduino, and it cannot be connected again until the control board is reset. We thought that the first version of the code, which used the U8glib library, might be incompatible with the Arduino Nano ESP32 control board. Upon investigation, the decision was made to switch to the second-generation U8g2 library. However, the problem persisted. Finally, the original SSD1306 library for control was used for coding. As for the port disconnection issue, no similar cases were found upon inquiry. Discussions suggested it might be due to logical errors in the code. Consequently, the decision was m ade to scrap the first version of the code and rewrite it from scratch. However, through continuous adjustment and review, we ultimately man...
Read more

Week 3

Image
 In week 3， it 's clear that our project progress has been significantly slowed down by various unexpected challenges and difficulties. However, we are also using these setbacks as opportunities to explore new methods and perspectives to achieve our established goals. We encountered frequent crashes while running an Android virtual machine on the computer.  After numerous attempts, we were reluctantly forced to abandon this approach. However, we still don't want to give up on the idea of ​​feeding back the status of the seat occupancy to the network, because compared to the physical OLED display screen, this is undoubtedly a function that truly helps students quickly find available seats. After a heated debate, we shifted our focus and plan to achieve the same effect through our relatively proficient web development skills. Compared to developing an app, building a website is relatively simpler. After some exploration, we approached our goal and successfully implemented the fu...
Read more