How bob12315/cuadc2026 works
CUADC 2026 is an autonomous multirotor reconnaissance and rescue system: the onboard RK3588 runs perception, mission logic, and the operator UI, while ArduPilot handles low-level flight control. The principal workflow is configuring the field, running a mission of flight and target actions, using visual detections to locate and select targets, releasing payload, then returning and landing. The graph also shows field setup, telemetry, safety, and observability as supporting capabilities. Some runtime wiring is unsampled; those relationships are omitted unless documented in the README or visible in the source index.
Main entry points: link_manager.py MAVLink link · api_routers.py Web control UI · engine.py Mission engine · mission_service.py Mission service
Components 21
Operator UI
- Web control UI
web_ui/api_routers.py - Web services
application/web_services.py - Runtime configuration
app/config.py
Mission Runtime
- Mission service
application/mission_service.py - Mission engine
missions/engine.py - Mission orchestrator
missions/core/mission_orchestrator.py - Mission actions
missions/common/actions - Action safety
execution/safety_pipeline.py - Runtime contracts
contracts/platform/common.py
Perception & Guidance
- YOLO perception
yolo_app/main.py - Target tracking
yolo_app/target_manager.py - Target localization
guidance/target_fusion.py - State fusion
fusion/fusion_manager.py
Flight & Telemetry
- MAVLink link
telemetry_link/link_manager.py - Command sender
telemetry_link/command_sender.py - ArduPilot
Field & Observability
- Field reference
field/service.py - Field profiles
field/profile_service.py - Flight blackbox
observability/blackbox.py - Core time
contracts/core/time.py
Other components
- Browser operator
Connections 22
- Browser operator → Web control UI: operates
README.md - Web control UI → Web services: routes requests
web_ui/api_routers.py - Web control UI → Runtime configuration: uses settings
web_ui/api_routers.py - Web services → Mission service: provides mission services
- Mission service → Mission engine: uses mission engine
application/mission_service.py - Mission engine → Mission orchestrator: runs mission steps
- Mission engine → Mission actions: starts actions
- Mission service → Action safety: checks authorization
application/mission_service.py - Action safety → Runtime contracts: uses execution contracts
execution/safety_pipeline.py - YOLO perception → Target tracking: updates targets
yolo_app/main.py - YOLO perception → Target localization: supplies visual targets
- Target localization → State fusion: combines target state
- Mission engine → MAVLink link: issues flight actions
- MAVLink link → Command sender: dispatches commands
telemetry_link/link_manager.py - Command sender → ArduPilot: sends MAVLink
README.md - ArduPilot → MAVLink link: returns telemetry
README.md - Web control UI → Field reference: configures field
- Field reference → Field profiles: loads profiles
field/service.py - Field reference → Runtime contracts: uses field contracts
field/service.py - MAVLink link → State fusion: provides flight state
- MAVLink link → Flight blackbox: records flight state
- Flight blackbox → Core time: uses timestamps
observability/blackbox.py