How xtech/self-o-mat works
Main Components Identification
• Hardware Layer:
• DSLR Camera (Multiple supported models)
• Raspberry Pi (Main processing unit)
• Arduino Controller (For hardware control)
• LED Flash System
• Printer (CUPS compatible)
• Trigger Mechanism (Buttons/Sensors)
• Software Layer:
• Core Application (C++)
• Web Interface (Angular/Ionic)
• Camera Control System
• Image Processing Pipeline
• State Management System
• API Layer
[DSLR Camera] ←→ [Raspberry Pi] ←→ [Arduino Controller]
• ↑ ↑ ↑
[Flash System] [Printer] [Trigger Button]
[Camera Controllers] → [Image Processor] → [Printer Manager]
• ↑ ↑ ↑
• [State Machine] ←→ [Booth Logic] ←→ [API Service]
[Web Frontend] ←→ [REST API] ←→ [WebSocket Updates]
Key Relationships to Highlight
• Camera Control Flow:
• Path from trigger input through state machine to camera activation
• Image data flow from camera through processing to storage/printing
• User Interface Flow:
• How web interface connects to core system
• Settings and control paths
State Management
[Booting] → [Idle] → [Agreement] → [CountDown] → [Busy]
• ↑ |
• ┘
Important Technical Details
• Protocol indicators (COBS, SLIP) for Arduino communication
• Supported camera models and interfaces
• Image processing pipeline stages
• Printer integration points
• Web API endpoints
Implementation Notes
• Use UML notation for clarity
• Version information and supported hardware models
• Notes about key configuration requirements
Architectural Patterns to Highlight
• State Pattern (for booth control)
• MVC Pattern (in web interface)
• Observer Pattern (for event handling)
• Strategy Pattern (for camera control)