Week 4


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 made to scrap the first version of the code and rewrite it from scratch.

However, through continuous adjustment and review, we ultimately managed to rectify the code, ensuring the smooth implementation of all functionalities. Nonetheless, our device components remain exposed, affecting both its appearance and stability. So we must prepare a suitable container for the device.

Final Code:



Outlook:

Circuit connection:


Our seat occurrence detector successfully passed a series of practical functionality tests, and it interacts well with the web interface. We also shot an instructional video introducing its main features.

The performance of the website:




Overall, our project has largely met expectations, despite the continuous challenges along the way. Looking back, we still remember our initial goals."

Comments

Popular posts from this blog

Week 3