How zinjpq/automatic-door works
Project type and purpose
• This is a full-stack embedded-plus-desktop application (“Automatic Door System”) that uses:
• A Python/Tkinter GUI for monitoring and control
• OpenCV for license-plate recognition
• Multiple microcontroller firmwares (ESP32-CAM, Arduino R3, Raspberry Pi, STM32) to drive door actuators (servos, LCD, infrared sensor, optional RFID)
• Purpose: capture images, detect plates, authorize doors, and physically open/close based on recognition and security rules.
File structure
Top level:
• firmware/ – per-platform embedded code
– Arduino/esp32 & r3 folders (.ino and setup headers, libraries)
– RaspberryPi (AuDo.py, MFRC522.py)
– STM32 (CubeMX project, HAL drivers, startup, linker script)
• simulations/ – Proteus schematic and libraries
• src/ – desktop application and plate-detection pipeline
– Components, Assets, Constants, Communication (http_esp32.py, mqtt_raspi.py)
– DetectPlateImage (OpenCV modules: Preprocess, DetectPlates, DetectChars, PossiblePlate/Char)
– Main.py – orchestrator
Configuration & documentation files: README.md, .gitignore, task.md.
README for additional insights
• Architecture described verbally: ESP32-CAM streams video → Python program performs plate detection → Tkinter GUI displays logs/status → On recognition, desktop app or MCU code sends UART or MQTT/HTTP commands to microcontrollers → Servos open/close door
• Hardware support for optional RFID, IR sensors
• Contributing steps and individual tasks hint at modular separation: firmware vs. app vs. simulations.
Elements
• Clear labels: e.g., “Tkinter GUI”, “DetectPlates.py”, “ESP32-CAM”, “Servo Motor”
• Image flow → detection
• Decision flow → command dispatch
• Control flow → actuation
• Status flow → GUI update
• Blue for desktop modules
• Green for network/communication
• Orange for edge devices/firmware
• Red for actuators/sensors