PROGRESS UPDATE OF FINAL YEAR PROJECT

The D-Day of the presentation of the Final Year Project was conducted on 7/6/2023. Two accessors evaluated me. After the presentation, Nor Shafiqin Shariffudin, who are one of the accessors gave me a lot of comments regarding to personal data that stored at Firebase. Her concern was,  is it the cloud are safe to stored personal data of user? My answer to that question was, only the admin or invited other user can access the cloud. Aside from that, she was satisfied with the project. Another one of my accessor commented that she likes the ideas of the biometric atm  and would love to see the project is being developed more with the industries. At the end of the week, I organized back my draft full report and come out with a draft of technical paper since the due date of the technical paper submission to the coordinator is on Friday (16/6/2023).

This week, my main goals are to get the project data and make a poster for the presentation I have coming up. The purpose of getting information like phone numbers, account numbers, and fingerprints is to measure how well the project is going and how well it is working. I will put this information on the poster to show how well the project did. Once I have all the data, I'll put it on the poster for the presentation. The project's progress will be shown on the poster through graphs, charts, and important statistics. It will do an excellent job of showing what the project has done and what it can do. By putting the collected data on the poster, I can show the audience what the project has done and how well it has worked. The poster is a visual such as a graph, to help people understand how far this project works.  Figure 1: Database User Figure 2: Amount of Register Account & Storage Figure 3: Poster of the project

After programming and testing the website, it was time to make the casing for the project. I bought a case from Mr DIY, a popular hardware store.  I sized the case to fit the LCD panel, keypad, fingerprint scanner, and servo motor. I had to be accurate so each component fit with the casing. I wanted people to easily access all functions. I slowly cut the case with following the measurement of my components. The detail was essential throughout. I needed to ensure the LCD are clear to seeing, the keypad had enough area for comfortable use, the fingerprint scanner was conveniently positioned for authentication, and the servo motor had enough room to function without obstructions.  I wanted the hardware and software to work together. The improved of the casing will protect internal components and looked good to users. It has to be ergonomic, functional, and attractive.  All the processes can be seen below. Figure 1: Cutting Process Figure 2: Assembly Process Figure 3: Final Product

During week 10, I began executing a fully developed project. I have provided a video below for you to review.

This week, I encountered an issue with the LCD display in my project. Upon initial testing, as shown in Figure 1, the LCD was unable to display any content. After conducting a thorough troubleshooting process, I discovered that the problem stemmed from the weak internet connection between the ESP32 and the cloud. To resolve this, I decided to switch to a different Wi-Fi connection with a stronger signal. The positive outcome of this adjustment can be seen in Figure 2, where the LCD successfully displays the desired information. Figure 1 Figure 2

This week, I made progress in developing a website using Google Firebase. The main objective of incorporating Firebase was to establish a reliable storage solution for user information. The website securely stores essential user details, including their account number, phone number, and even an image of their fingerprint. Figure 1 illustrates the process where users successfully capture and upload their fingerprint images to Firebase for secure storage. Figure 1 The user information, including their account number, fingerprint image, and phone number, is organized and categorized based on the user's phone number within the Firebase database (refer Figure 2) Figure 2