FabSafe
Innovation that cares, secure access to build a risk-free future
FabSafe
Is a security and access control system for dangerous machinery in fablab environments, specifically designed to ensure user safety and responsible use of equipment such as saws, laser cutters, and other high-risk tools. The system uses a fingerprint reader to authorize access, controls the power on/off of machines via a relay, and sends real-time notifications through Telegram to inform about usage, access time, and machine status. Additionally, it includes an inactivity timer that notifies the user if the machine has been on for an extended period and allows remote or fingerprint-based shutdown.
Benefits:
- ✔️ Safety: Only authorized users can operate the machines.
- ✔️ Control: Real-time logging of who uses each machine and when.
- ✔️ Accident prevention: Automatic shutdown in case of prolonged inactivity.
- ✔️ Notifications: Instant alerts via Telegram for supervisors and users.
- ✔️ Adaptability: Easy integration with different types of machines and fablab environments.
Components List:
- ESP32-S3: Microcontroller for system logic and Wi-Fi communication.
- Fingerprint Sensor Module (R307 or FPM10A): For user authentication.
- Solid State Relay (SSR): To control the power supply of the machine.
- Current Sensor (ACS712): Optional, to detect if the machine is physically on or off.
- LCD Display (16x2 or 20x4): To show messages like "Access Granted" or "Machine On".
- Power Supply (5V or 12V): To power the ESP32, fingerprint sensor, and relay.
- Emergency Button: Optional, for manual shutdown in case of emergencies.
- Enclosure: To protect the system and give it a professional look.
- Jumper Wires and Breadboard: For prototyping.
- Telegram Bot: For sending notifications to users and supervisors.
Project Final Schedule Projection
Objective:
Complete the functional prototype of the biometric access control system for the FabLab bench saw, ensuring its secure operation and traceability, by May 26.
Commitment:
Considering my available time (4h in the mornings, 2h in the evenings, and 8h on weekends), I have structured the following technical plan. I acknowledge that it is ambitious, but I am committed to fulfilling it with the following adjustments:
Key Phases and Goals:
🔌 Hardware Integration (April 22 - May 5):
Priority: Have the biometric system and emergency button functioning by April 30.
Risk: If the sensor fails, I will use a temporary RFID module while I fix the error.
💻 Software & Control (May 6 - May 19):
Critical goal: The admin interface must register accesses and alerts by May 12.
Contingency: If there are delays, I will simplify the dashboard (only basic logs) and improve it post-delivery.
🚨 Final Validation (May 20 - May 26):
Final test: I will simulate a real workshop day in the FabLab on May 25 to validate security.
Detailed Step-by-Step for Activities:
This is a detailed plan for the tasks, dates, and deliverables:
Phase 1: Hardware Integration (April 22 - May 5)
| Date | Task | Deliverable |
|---|---|---|
| April 22 | Biometric tests (validate false positives) | Sensor accuracy report |
| April 24 | Relay → Bench saw connection | Video: Relay activates/deactivates machine |
| April 25 | Integrate emergency button (power cutoff) | Functional circuit with safety |
| April 27 | Configure LCD: Timer + alerts | Display shows real-time data |
Phase 2: Software & Control (May 6 - May 19)
| Date | Task | Deliverable |
|---|---|---|
| May 6 | Program admin interface (notifications) | Dashboard with access log |
| May 8 | Local database (authorized users) | JSON/MySQL with 3 test users |
| May 11-12 | Full debugging (code + connections) | 100% integrated system |
| May 13-14 | Stress tests (overload/failures) | Stability report |
Phase 3: Final Validation (May 20 - May 26)
| Date | Task | Deliverable |
|---|---|---|
| May 20 | Review with instructors (feedback) | List of priority adjustments |
| May 21 | Post-feedback adjustments (e.g., biometric sensitivity) | Version 2.0 of the prototype |
| May 25 | Final test in real context (FabLab) | Full demonstration video |
| May 26 | Technical documentation (circuit + code) | PDF/README.md uploaded to platform |
Critical Milestones (Checkpoints):
- April 30: Functional biometric system + emergency.
- May 12: Admin interface receiving data.
- May 20: Instructor feedback integrated.
- May 25: Test in real scenario (FabLab, EAN Lab).
Conclusion:
This schedule is my prioritized roadmap, but I will maintain flexibility to iterate based on testing and feedback. I will progressively update the documentation to reflect progress and changes.