Week 3

 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 functionality to view real-time seat status on the website by logging in with a password.

Due to delivery issues, our OLED screen has not yet arrived. This directly caused our project to enter a stagnant phase because the other hardware components had already been connected to the circuit according to the pinout diagram, and the operation code for each component had also been completed. We really need this missing component to complete the overall circuit, so that we can integrate and test the completeness of the code in series. Worried about possible mishaps with the delivery, we went ahead and ordered an OLED screen ourselves.

Fortunately, by modifying previously learned infrared detection code, we successfully compiled the software part for the ultrasonic distance sensor.

code：