How marshallrichards/turbodrone works
High-Level File Structure Analysis
• Top level
• README.md – project introduction, setup instructions, status & roadmap
• src/
• receive_video.py – module to connect to the drone’s video stream, decode frames, and display or process them
• remote_control.py – module to assemble and send control packets (throttle, yaw, pitch, roll) to the drone
• requirements.txt – Python dependencies (e.g., socket, curses, OpenCV if used)
• There are no web-frontends or databases—this is purely a networked CLI application.
Key Architectural Insights from README
• The drone exposes a Wi-Fi SSID (e.g., Hiturbo-S20-XXXX) that your computer must join.
• Video is received over a UDP stream.
• Control commands are sent via a custom UDP/TCP protocol that mimics the mobile app.
• All packet formats and heartbeats were reverse-engineered from decompiled Android APKs and verified with Wireshark.
Main Components
a. User’s Workstation (Left-hand side)
• Python Runtime + Virtual Environment (venv)
• receive_video.py module
• remote_control.py module
• OS Network Stack & Wi-Fi Dongle driver
b. Wireless Network Layer (Center)
• 802.11n/ac Wi-Fi channel
• SSID “Hiturbo-S20-XXXXXX”
c. Drone Hardware (Right-hand side)
• Flight Controller & Firmware
• Downward-facing optical flow sensor
• 1080p camera module
• Onboard Wi-Fi transceiver
d. External Tools (Optional/Overlay)
• Wireshark (for packet inspection during development)
• jadx (for APK decompilation)
Relationships & Data Flows
• receive_video.py → UDP video stream → Drone camera
• remote_control.py → UDP control packets → Drone flight controller
• Bidirectional heartbeats (UDP) maintain the session
• The Virtual Environment and Python interpreter wrap both modules in the same host boundary
Architectural Patterns & Design Principles
• Modular CLI design: separate concerns (video vs. control) in two executable modules
• Network-centric design: everything is modeled as packet streams over UDP
• Reverse-engineering feedback loop: external tools feed into protocol implementation
• Optional callouts for development tools (Wireshark, jadx) to show the engineering workflow