How flyonspeed/tronview works
Key Components to Include:
Data Input Layer
• EFIS Systems (MGL iEFIS, Garmin G3x, Dynon Skyview, etc.)
• Sensor Inputs (BNO055/BNO085 IMUs, ADS1115 for analog)
• Network Inputs (Stratux WiFi, Levil BOM WiFi)
• Input Handlers (located in lib/inputs/)
Data Processing Core
• DataShip Module (lib/common/dataship/)
• Event Manager (lib/common/event_manager.py)
• Common Utilities (lib/common/)
Rendering Engine Layer
• Split into three main rendering modes:
• Graphic Mode (lib/common/graphic/)
• Text Mode (lib/common/text/)
• 3D Mode (lib/modules_kivy/horizon_3d/)
Module System
• EFIS Modules (artificial horizon, traffic scope, etc.)
• HUD Modules (AOA, CDI, heading, etc.)
• General Modules (gauges, text, 3D objects)
• GUI Modules (menus, controls)
Screen Management
• How screens are composed:
• Screen Templates (lib/screens/templates/)
• Screen Implementations (lib/screens/)
• Screen Configuration System
Connection Types
• Double lines: Configuration relationships
Important Details
• Data flow paths showing how information moves from inputs through processing to display
• Module loading system
• Event handling system
• Screen template system
• Configuration management
Architectural Patterns to Highlight
• Plugin architecture for inputs and modules
• Event-driven communication
• MVC-like pattern for screen management
• Template-based screen configuration
Keep the following aspects in mind:
• Separation between data acquisition, processing, and visualization
• Modular nature of the system
• Multiple display modes (HUD, EFIS, Text, 3D)
• How configuration affects different parts of the system
• Where external hardware interfaces exist