Autel: match the SDK generation

Autel provides multiple Mobile SDK generations. The V2.5 page reviewed for this guide identifies the EVO Max series, Smart Controller V3 and particular firmware and Android requirements; it is not a declaration that every Autel aircraft is supported. Capability categories such as camera, gimbal, mission and tracking still require per-API verification against the intended product combination. Define whether the filming need is framing control, recording synchronization or subject following before evaluating a sample application. That keeps a visually impressive demonstration from substituting for a compatibility test. If a demonstration uses a different model, record that mismatch first. Similar family names may hide controller or camera differences; do not fill a purchasing-critical compatibility gap by assumption.

Parrot: separate ground and onboard code

Parrot’s Olympe provides a Python controller interface from a Linux computer, and its official repository describes compatibility with simulated aircraft through Sphinx. Ground SDK, Air SDK and PDrAW serve different roles. Air SDK concerns missions running on supported aircraft, while PDrAW addresses video and metadata. Execution location affects latency, compute resources, distribution and failure behavior. Check the supported models for the exact release rather than assuming every ANAFI-family aircraft exposes the same functionality. Moving computation onboard may reduce some communication but adds resource and maintenance responsibility. Define boundaries so a vision update does not unexpectedly affect flight behavior, and validate each execution environment separately.

Define a vendor-neutral shot contract

Our original integration design starts with a vendor-neutral shot contract: subject, recording interval, camera settings, path, abort conditions and state confirmations. A vendor adapter maps those intentions to available APIs and explicitly rejects unsupported requirements. Do not silently ignore an unsupported field and report success. A platform that accepts a camera angle may not start recording with the same timing precision as another. Measure latency and variability, and record model, SDK version and failure reasons. Portability comes from representing differences accurately, not merely presenting identical buttons. A common shot contract can include alternatives, such as a clearly declared manual camera adjustment. Make that change explicit rather than silently adding unexpected work for the operator.

YOUR NEXT STEP

Put it into practice.

Watch for these pitfalls
  • Do not infer consumer/enterprise compatibility from an SDK family name.
  • Do not treat remote commands as zero-latency camera control.

Sources and editorial scope

Explanations and exercises are original editorial material. Verify product-specific conditions against the linked documentation version.

  1. Autel — Mobile SDK V2.5 ↗
  2. Parrot — Olympe official repository ↗
  3. Parrot — Air SDK Introduction ↗
  4. Parrot — Open source Development Tools ↗

Research date: 21 October 2026. Check the linked version, supported hardware and applicable conditions. Evidence includes directly reviewed text and official search-index records.

Read the methodology and open questions →