How ksdreamer/hand_exoskeleton works
Project Type and Purpose
• This is an embedded “full‐stack” mechatronics system:
• Mechanical subsystem (linkage + tendon exoskeleton)
• Electronics subsystem (ESP32 microcontroller, SC09 servo bus, power)
• Firmware & web server (Arduino sketch + HTML/JS/CSS UI)
• User devices (PC, phone) interact via Wi-Fi
File Structure
• Top‐level folders:
• mechanics/ (CAD parts in SolidWorks, 3D‐print STL & 3MF files)
• program/ServoDriver (Arduino .ino + driver headers + webpage code)
• images/ (documentation)
• Notable files:
• BOARD_DEV.h, STSCTRL.h, CONNECT.h, WEBPAGE.h (modules of firmware)
• ServoDriver.ino (main loop + setup)
Architectural Insights from README
• ESP32 runs a built-in web server and SC09 servo bus driver
• Seven SC09 servos arranged as a bus; each servo drives a finger linkage
• Web front end offers on‐device GUI for real-time control over Wi-Fi
• Serial (Type-C) used for firmware upload and debug console
Main Components and Their Relationships
a. Mechanical Subsystem
• CAD parts (SolidWorks models) → 3D‐print STL parts → assembly
• Linkage networks for four fingers; tendon lines for thumb
• Mounted directly on servo horns/arms
b. Electronics Subsystem
• Power supply (6–12 V adapter or 2×18650 battery pack) → DC jack on ESP32 dev board
• ESP32 board ↔ SC09 servo bus (SDA/SCL or serial bus lines) → 7 servos
• USB Type-C port for code upload & serial debug
c. Firmware & Software Modules
• ServoDriver.ino (setup(): initialize Wi-Fi AP, servo IDs; loop(): handle web requests & sync writes)
• STSCTRL.h / RGB_CTRL.h (low‐level servo command wrappers)
• .h (“case” actions: openHand(), moveThumb(), etc.)
• WEBPAGE.h (embedded HTML/JS/CSS)
d. User Interaction
• User device connects to ESP32_AP SSID → browser to 192.168.4.1
• HTTP requests / WebSocket (if used) → ESP32 server
• Server processes requests → CONNECT module → STSCTRL → Servo bus → mechanical movement
Architectural Patterns & Design Principles
• Layered decomposition: physical (mechanical), electronic, firmware, UI
• Event‐driven (button clicks → case dispatch in CONNECT.h)
• Modular firmware: separate headers for hardware abstraction, control logic, UI
• Single‐board host with built-in web server (no separate PC backend)