Skip to main content
Ctrl+K

Open Edge Platform

    • Open Edge Platform Overview
    • Metro
    • Manufacturing
    • Retail
    • Robotics
    • Education
    • Health and Life Sciences
    • Federal and Aerospace
    • Libraries, Tools, Services
    • DL Streamer
    • Scenescape
    • ViPPET
    • Geti
    • OpenVINO
    • OpenVINO Physical AI
    • Platform Software
  • Open Edge Platform Overview
  • Metro
  • Manufacturing
  • Retail
  • Robotics
  • Education
  • Health and Life Sciences
  • Federal and Aerospace
  • Libraries, Tools, Services
  • DL Streamer
  • Scenescape
  • ViPPET
  • Geti
  • OpenVINO
  • OpenVINO Physical AI
  • Platform Software

Section Navigation

  • Handheld (Soldier System) Blueprint
    • Infrastructure Setup
      • System Requirements
      • Advanced Image Customization
      • Build on macOS (x86 VM)
      • Infrastructure Capabilities
        • Container Device Interface Guide
        • GPU and NPU Device Plugins
        • Power Profiles User Guide
        • Thermal Profiles User Guide
        • Power and Thermal Profiles Co-working Guide
      • Troubleshooting
    • Install OEP SDKs
    • Install Handheld Multi-Modal Application
    • Access Application User Interface
    • Operator Guide
    • Application Operations
    • Benchmarks
      • Edge Workloads and Benchmarks Guide
    • AI Playground
    • AI Agent SKILLs
      • DL Streamer Pipelines Guide
        • DL Streamer Coding Agent Guide
      • Infrastructure AI Agent Integration
    • Release Notes
      • Release Notes 2026.1
  • UAV Blueprint
    • Infrastructure Setup
      • System Requirements
      • Advanced Image Customization
      • Build on macOS (x86 VM)
      • Infrastructure Capabilities
        • Container Device Interface Guide
        • GPU and NPU Device Plugins
        • Power Profiles User Guide
        • Thermal Profiles User Guide
        • Power and Thermal Profiles Co-working Guide
      • Troubleshooting
    • Install OEP SDK and Usage
    • Install UAV Vision Analytics Application
      • Standalone Mode
      • UAV Mission Compute SDK Mode
    • How-To Guides
      • QGroundControl
      • Multi-UAV Operations in the Ground Station
      • Search Live Video with VSS
      • Switch Deployment Modes
      • Enable NPU Inference
      • Simulate a Continuous Mission
      • View Detection Logs
      • Makefile Reference
      • Troubleshooting
    • How to Customize
      • Configure the Cameras
      • RealSense Camera
      • Manage the Detection Model
      • Modify the Detection Model
      • Change the Captioning (VLM) Model
      • Change the Video Source
      • Use Your Own Videos
      • Manage Pipelines
      • Modify Pipelines
      • Customize the Telemetry Overlay
      • Tune VSS Live Search
    • Benchmarks
      • UAV-specific Benchmarks Guide
      • Edge Workloads and Benchmarks Guide
    • Agent SKILLs
      • DL Streamer Pipelines Guide
        • DL Streamer Coding Agent Guide
      • Infrastructure AI Agent Integration
      • SDK Agent Commands and MCP Tools
    • Release Notes
  • Mission Systems Blueprint
    • Infrastructure Setup
      • System Requirements
    • Deterministic Threat Detection
      • System Requirements
      • First-Time Setup
      • Get Started
        • System Requirements
        • First-Time Setup
        • How-To Guides
          • Configure the Moxa Time-Sensitive Networking (TSN) Switch
          • Configure VLANs on the Moxa Switch
          • Create VLANs on All Machines
          • Configure Precision Time Protocol (PTP), IEEE 1588v2
          • Configure Precision Time Protocol (PTP), IEEE 802.1AS (gPTP)
          • Enable Time-Sensitive Networking (TSN) Traffic Shaping (IEEE 802.1Qbv)
          • Configure the Basler Camera to Use Precision Time Protocol (PTP) Timestamps
          • Integrate Basler Cameras with Scenescape
      • How-To Guides
        • Configure the Moxa Time-Sensitive Networking (TSN) Switch
        • Configure VLANs on the Moxa Switch
        • Create VLANs on All Machines
        • Configure Precision Time Protocol (PTP), IEEE 1588v2
        • Configure Precision Time Protocol (PTP), IEEE 802.1AS (gPTP)
        • Enable Time-Sensitive Networking (TSN) Traffic Shaping (IEEE 802.1Qbv)
        • Configure the Basler Camera to Use Precision Time Protocol (PTP) Timestamps
        • Integrate Basler Cameras with Scenescape
      • Release Notes
    • Benchmarks
      • Mission Systems Benchmarks Guide
      • Edge Workloads and Benchmarks Guide
    • Release Notes

---------------

  • Intel® Edge System Qualification
  • Get Help or Contribute
  • Federal And Aerospace AI Suite
  • Uncrewed Aerial Vehicle (UAV) Blueprint
  • How to use UAV Vision Analytics
  • Switch Between Pymavlink and UAV Mission Compute SDK Deployment Modes

Switch Between Pymavlink and UAV Mission Compute SDK Deployment Modes#

UAV Vision Analytics supports two independent deployment modes. This tutorial explains the architecture difference, how to switch between them cleanly, and the HOST_IP binding requirement that trips up first-time UAVSDK mode setup.

The two modes#

Standalone (Pymavlink)

UAV Mission Compute SDK

Compose file

docker-compose-pymavlink.yml

docker-compose-uavsdk.yml

make targets

make pymav-up / make pymav-down

make uavsdk-up / make uavsdk-down

Telemetry source

PX4 SITL → mavlink-router → pymavlink (UDP)

uav-mission-compute-sdk project → MQTT

Video source

Looped local file or RealSense camera

3 RTSP camera streams from the SDK (nadir/forward/rear)

Self-contained?

Yes — PX4, router, broker all included

No — requires the separate uav-mission-compute-sdk project running first

Config file

configs/config-pymavlink.json

configs/config-uavsdk.json

Standalone mode is self-contained because it starts its own PX4 SITL and MAVLink routing. UAV Mission Compute SDK mode instead attaches to a separately-running SDK project that owns the flight simulator, camera feeds, and MQTT telemetry — uav-vision-analytics only runs the DLSPS inference container in that mode.

Prerequisites#

  • Only one mode’s stack should be running at a time — they are independent Docker Compose projects but both publish the same host ports through nginx (80/443/8555/1883).

  • For UAVSDK mode: the uav-mission-compute-sdk project cloned alongside this repo (see Get Started — UAV Mission Compute SDK Mode).

Steps#

Switch from standalone to UAV Mission Compute SDK mode#

# 1. Stop the standalone stack if running
make pymav-down

# 2. Start the SDK project's core infrastructure (PX4, MQTT, RTSP server)
cd ../uav-mission-compute-sdk

The SDK’s .env defaults to HOST_IP=127.0.0.1, which binds MQTT, the MediaMTX RTSP server, and every other published port to loopback only. Because uav-vision-analytics runs in a separate Docker container/network, it cannot reach loopback-bound ports on the host — so this bind address must be widened before starting the SDK:

sed -i 's|^HOST_IP=.*|HOST_IP=0.0.0.0|' .env
make up-sim-camera
# 3. Start uav-vision-analytics in UAVSDK mode
cd ../uav-vision-analytics
make uavsdk-up
make start-rtsp

Switch from UAV Mission Compute SDK mode back to standalone#

make uavsdk-down
cd ../uav-mission-compute-sdk && make down
cd ../uav-vision-analytics
make pymav-up
make start-rtsp

Verify#

Before starting uav-vision-analytics, confirm the SDK is actually reachable from outside its own network (this proves the HOST_IP fix took effect, rather than only discovering the failure later):

docker network ls | grep uav-mission-compute-sdk
curl -sf http://<HOST_IP>:8080/action/arm -X POST   # any reachable SDK REST endpoint

A Connection refused here means HOST_IP is still loopback-bound — repeat the sed step above and restart the SDK (make down && make up-sim-camera).

Troubleshooting#

ConnectionRefusedError / RTSP 404 in UAVSDK mode (the HOST_IP symptom above), both stacks starting but only one streaming, and an overlay that shows zeros right after switching are covered in Troubleshooting — Pipelines.

On this page
  • The two modes
  • Prerequisites
  • Steps
    • Switch from standalone to UAV Mission Compute SDK mode
    • Switch from UAV Mission Compute SDK mode back to standalone
  • Verify
  • Troubleshooting
Show Source
Enable cookies to use AI chat
Chat is locked. Click the blue chat button, then enable Functional cookies to unlock it.