How astrohuntsman/huntsman-dome works
Main Components
a) Client Layer:
• TheSkyX Application (astronomical software)
• X2Dome Driver Interface
b) Communication Layer:
• gRPC Framework
• Protocol Buffers (protobuf) definitions
c) Control Layer:
• Python gRPC Server (on Raspberry Pi)
• Hardware Control Components
d) Hardware Layer:
• Dome Rotation Motor
• Encoder
• AutomationHAT (optional)
• GPIO Interfaces
• [TheSkyX Application Layer]
• ↓
• [C++ X2Dome Driver Layer]
• ↓
• [gRPC Communication Layer]
• ↓
• [Python Control Layer]
• ↓
• [Hardware Interface Layer]
Component Relationships
• Command flow from TheSkyX → X2Dome Driver → gRPC → Python Server → Hardware
• Status/feedback flow in the reverse direction
• Bidirectional communication between components where applicable
Important Details
a) Software Components:
• TheSkyX with X2 standard integration
• C++ X2Dome driver component
• Python gRPC server component
• GPIO control interfaces
b) Communication Protocols:
• gRPC channels between C++ and Python components
• Hardware communication protocols (GPIO)
c) Configuration Elements:
• dome_controller_config.yml
• Protocol Buffer definitions (hx2dome.proto)
Technical Details to Highlight
• gRPC service definitions
• Hardware abstraction layers
• Configuration management
• Logging system integration
• Testing/simulation capabilities
Implementation Notes
• Main application components
• Supporting libraries (gpiozero, smbus, sn3218)
• Configuration files
• Generated code components
Hardware abstraction and simulation capabilities
This system design should clearly illustrate how commands flow from the astronomical software through various layers to control the physical dome, and how status information flows back up through the system.