Final Project¶

Smart Access Control System for the FabLab¶

My final project is a smart access control system for the FabLab, designed to restrict entry to registered and authorized members only. The system uses an RFID badge for identification and logs every entry and exit through a web monitoring dashboard accessible via Wi-Fi.

Summary slide¶

Video Presentation¶

Gantt Chart¶

What does it do?¶

The project is a smart access control system for the FabLab INPHB. It restricts entry to registered and authorized members via an RFID badge.

This idea came from observations made during my time at the FabLab: the physical key was often unavailable or lost, and it was difficult to know exactly who had entered the FabLab and at what time.

The objective of this project is to develop a system that allows only authorized persons to access the FabLab using an RFID badge. The system also includes a web application for logging and monitoring entries and exits, ensuring complete traceability.

Concretely:

• A member presents their RFID badge to the reader installed at the entrance.
• The ESP32 reads the badge UID and checks it against the list of authorized members stored in flash memory.
• If the badge is authorized: the green LED turns on, a confirmation beep sounds, the TFT screen displays "Access Granted", and an ESP-NOW signal is sent to the indoor module which activates the relay and unlocks the door for 5 seconds.
• If the badge is denied: the red LED turns on, a warning beep sounds, and the screen displays "Access Denied".
• In all cases, the event (access granted or denied, badge UID, timestamp) is logged in real time to a Supabase database (cloud PostgreSQL) and can be viewed via a Next.js web dashboard.
• A manual indoor button also allows anyone already inside the FabLab to open the door without a badge.

Who has done what beforehand?¶

I researched previous Fab Academy projects and existing commercial products related to access control and RFID-based systems.

• IOT FABTRACKER — by Achraf Ben Jamaa, Fab Academy 2020 A connected system for tracking people and equipment in a FabLab using IoT technologies.

• SMART DOOR LOCK SYSTEM — by Mansoor Ahmed, Fab Academy 2020 A smart door lock system using RFID and microcontroller programming.

• FAB BUDDY — by Philippe Libioulle, Fab Academy 2019 A system to manage access and usage of FabLab machines.

On the commercial side, I was inspired by FABMAN, a professional solution for managing FabLab resources and machine access.

What did you design?¶

The following elements were entirely designed by the author:

What materials and components were used? Where did they come from? How much did they cost?¶

What parts and systems were made?¶

Fabricated parts¶

Developed systems¶

What processes were used?¶

What questions were answered?¶

1. Can physical events be logged to the cloud from a microcontroller?

Yes. Each badge scan generates an HTTPS POST request to a Supabase database (PostgreSQL), which is then visible in real time from any browser via WebSockets.

2. Can two ESP devices communicate peer-to-peer without a Wi-Fi router?

Yes, using Espressif's ESP-NOW protocol. The transmission latency is below 50ms, which is imperceptible to the user.

3. Can a 3D-printed enclosure serve a permanent physical installation?

Yes, for indoor or semi-protected environments. PLA at 20% infill provides sufficient rigidity. A more robust version could use PETG or ABS for more humid environments.

4. Can the firmware of physically installed microcontrollers be updated without dismantling them?

Yes, using ElegantOTA. Both ESP devices (ESP32 and ESP-01S) expose an /update endpoint accessible over the local Wi-Fi network.

What worked? What didn't?¶

What worked ✅¶

• RFID reading by the ESP32 via SPI with custom GPIO reassignment (to avoid conflicts with the TFT screen's HSPI bus) works reliably.
• ESP-NOW communication between the ESP32 and the ESP-01S is stable and fast.
• Logging to Supabase via HTTPS works correctly (using WiFiClientSecure with setInsecure() to bypass TLS certificate verification).
• The Next.js web application displays events in real time via Supabase WebSockets.
• 3D printing of the enclosures with the Prusa MK4S+ produced precise, well-fitted parts.
• PCB milling with the Roland SRM-20 produced a clean and functional circuit on the first attempt.
• OTA firmware updates via ElegantOTA work on both ESP devices.
• The Fail-Safe (NC) mode of the electric lock guarantees automatic unlocking in the event of a power failure, meeting safety requirements.

What didn't work / Challenges encountered ⚠️¶

• SPI conflict: simultaneous use of the RFID RC522 reader and the ILI9341 TFT screen on the same SPI bus caused interference. Solution: reassigning the RFID's GPIO pins to the main SPI bus and using the dedicated HSPI bus for the screen.
• TLS certificate: the secure HTTPS connection to Supabase required client.setInsecure() due to the lack of root certificate management on the ESP32.
• ESP-01S memory: the low RAM of the ESP8266 (80KB) limited the features that could be implemented on the door module. The solution was to keep the firmware minimal (ESP-NOW reception + OTA only).
• Supabase latency: the HTTPS POST request to Supabase adds a delay of ~500ms to 1s per scan. This is noticeable but acceptable for the use case, since the physical door unlocking happens independently and immediately via ESP-NOW.

How was it evaluated?¶

The system was evaluated against the following criteria:

1. Authorized badge functional test: presenting a registered badge → verifying that the lock opens, the green LED turns on, and the entry appears as "granted" in the dashboard.

2. Denied badge functional test: presenting an unregistered badge → verifying that the lock stays closed, the red LED turns on, and the event appears as "denied" in the dashboard.

3. Indoor manual button test: pressing the Siemens button → verifying that the lock opens without a badge.

4. Network robustness test: disconnecting then reconnecting the Wi-Fi → verifying automatic reconnection and resumption of Supabase logging.

5. OTA test: deploying a new firmware version via the ElegantOTA web interface on both modules.

6. Security test: verifying that an unknown badge (unregistered UID) never unlocks the door.

7. Fail-Safe test: cutting the 12V power supply → verifying that the NC lock opens automatically (safety compliance).

8. Latency test: measuring the delay between badge presentation and physical door opening.

What are the implications?¶

Immediate practical implications¶

• FabLab INPHB security: the system effectively controls who enters the FabLab, tracks attendance, and restricts access to registered members, protecting expensive equipment.
• Traceability: the timestamped log of every access event (granted or denied) provides a valuable history for lab management.
• Remote monitoring: the administrator can check access logs from any connected device, without being physically present.

Extension potential¶

• Web-based member management: adding an admin interface to register or revoke badges without reprogramming the ESP32.
• Notifications: sending email or SMS alerts on repeated denied access attempts (intrusion attempts).
• Multi-door: replicating the system across multiple building entrances (each door module having its own ESP-NOW MAC address).
• Attendance tracking: using the access log to automatically calculate member presence hours.

Current limitations¶

• The Supabase connection uses setInsecure() (no TLS verification). In production, the Supabase root certificate should be embedded.
• PLA is not suited for outdoor installation exposed to rain or high humidity.

Licensing¶

Like all Fab Academy students, my work is supported by the MIT License, which ensures it remains open and freely accessible.

In addition, I have chosen to apply the following Creative Commons license to this project:

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

This means you are free to share and adapt this work, under the following terms:

• Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made.
• NonCommercial — You may not use this material for commercial purposes.
• ShareAlike — If you remix, transform, or build upon this material, you must distribute your work under the same license.

All Project Files¶

All files related to this project are available for download below. For details on how each file was produced, refer to the Project Development page.

• Outdoor Access Module — STL file
• Outdoor Access Module — SolidWorks file
• Indoor Door Control Module — STL file
• Indoor Door Control Module — SolidWorks file
• Front panel DXF file
• Circuit KiCad file
• Web Application Source Code
• Program 1 — ESP32 Main Controller
• Program 2 — ESP-01S Door Controller