How lakhmanisahil/medical_drone works
MeddyBuddy combines operator-facing health-check prompts with autonomous MAVLink flight control and a return-flight handoff. The README describes Gazebo, ArduPilot SITL, and QGroundControl integrations; sampled scripts show the control and GUI subprocess calls, but not simulator configuration or live sensor acquisition. The GUI records completion markers, not measured health values. The STL and media assets support the physical payload and demonstration, rather than runtime processing.
Main entry points: gui.py MedResQ GUI · takeoff_waypoints.py Waypoint mission · rtl.py Return mission
Components 12
Flight control
- Waypoint mission
scripts/takeoff_waypoints.py - Return mission
scripts/rtl.py - MAVLink endpoint
Medical interface
- MedResQ GUI
scripts/gui.py - Health prompts
scripts/gui.py - Recorded markers
Payload design
Simulation and ground control
- Gazebo simulation
- ArduPilot SITL
- QGroundControl
- Demo media
media
Other components
- Operator
Connections 11
- Operator → MedResQ GUI: opens
- MedResQ GUI → Health prompts: shows prompts
- Health prompts → Recorded markers: writes markers
- MedResQ GUI → Return mission: launches
- Waypoint mission → MAVLink endpoint: sends commands
- MAVLink endpoint → Waypoint mission: returns telemetry
- Return mission → MAVLink endpoint: sends commands
- MAVLink endpoint → Return mission: returns telemetry
- Waypoint mission → MedResQ GUI: launches after landing
- Gazebo simulation → ArduPilot SITL: MAVLink simulation
- QGroundControl → MAVLink endpoint: monitors telemetry