How cbruiz/printhor works
Main System Components
A. Hardware Abstraction Layer (Top Level)
• Native Simulator
• STM32 Boards (SKR Mini E3, MKS Robin Nano)
• RP2040 Boards
• Nucleo Boards
B. Core Framework Layer (Middle Level)
• Motion Control System
• Motion Planning
• Kinematics
• Trajectory Control
• Temperature Control System
• I/O Management
• Task Management
• System
C. Interface Layer (Bottom Level)
• GCode Parser/Processor
• Communication Interfaces
• User Interface Components
Component Relationships
A. Hardware Interface Flow:
Hardware Boards -> Hardware Abstraction Layer (HWI) -> Core Framework
B. Control Flow:
GCode Input -> Parser -> Task Management -> Motion/Temperature Controllers -> Hardware
C. Data Flow:
Sensors -> Hardware Interface -> Controllers -> State Management -> User Interface
Specific Implementation Details
Key architectural elements:
A. Hardware Abstraction:
• hwi-boards implementations for different targets
• Common traits and interfaces
• Peripheral abstractions (ADC, PWM, UART, etc.)
B. Control Systems:
• Motion planning system with its components:
• Trajectory Planning
• Velocity Profile Generation
• Stepper Motor Control
• Thermal control system with PID controllers
C. Task Management:
• Async task system
• Event bus architecture
• Resource sharing mechanisms
Technical Specifications
Technical details:
A. Supported Protocols:
• GCode command support
• Communication interfaces
• SD Card interface
B. Real-time Components:
• Motion timing
• Temperature monitoring
• Emergency stop system
Key Features to Highlight
Important aspects:
A. Safety Features:
• Emergency stop paths
• Temperature monitoring
• Limit switch handling
B. Performance Features:
• Async task management
• DMA utilization
• Resource sharing
C. Extensibility:
• Board support addition
• Feature modularity
• Hardware abstraction layer