AUTO-SYNC Index refreshed every 12h Β· Evidence-linked
Data release v20260914_020943 Generated 2026-09-14 Methodology Report missing resource
Data checked 2026-08-13. Data may be stale - beyond the review cycle. Review cycles are documented on the Methodology page. Methodology

CopterExpress/clover

SDK / API Tier A flight_control MIT
Official confirmed

ROS-based framework and RPi image to control PX4-powered drones πŸ€

Engineering Snapshot

Use cases & tasks 6
Best suited for
  • education
  • ROS developers targeting PX4
  • Raspberry Pi companion computer deployments
Primary tasks
  • Controlling PX4 drones via ROS
  • Teaching robotics with quadcopters
  • Implementing ArUco/optical-flow CV on drone
Stack & ecosystem
Resource type
SDK / API
Ecosystem
aruco Β· computer-vision Β· drone Β· education Β· mavros Β· optical-flow
License & compliance
License
MIT (Inferred)
Lifecycle & freshness Show
Maintenance
Active
Latest version
Not recorded
Last activity
2026-08-11
Last checked
2026-08-13
Verification
Official confirmed

What It Solves

Provide a ROS-centric software framework and Raspberry Pi image to control PX4-powered drones with built-in CV (ArUco, optical flow) for education and prototyping.

Primary use cases

  • Controlling PX4 drones via ROS
  • Teaching robotics with quadcopters
  • Implementing ArUco/optical-flow CV on drone

Secondary use cases

  • Using MAVROS for PX4 telemetry
  • Rapid autonomous quadcopter prototyping

When to Use

Consider when

  • Need ready-to-use RPi image
  • Target is PX4-compatible autopilot
  • Prefer ROS workflow

Verify before adopting

  • MIT license is inferred, confirm in repo
  • No explicit hardware targets listed
  • No version/release metadata provided

Start Here

website https://clovercoex.tech github api https://api.github.com/repos/CopterExpress/clover

Adoption Checklist

  • Needs verification MIT license is inferred, confirm in repo
  • Needs verification No explicit hardware targets listed
  • Needs verification No version/release metadata provided

Each check stays "needs verification" until an official source confirms it; unconfirmed items are never marked verified.

Known Limitations & Unknowns

Known limitations

  • License status inferred not confirmed
  • No hardware targets specified
  • No latest version info

Not publicly verified

  • Supported PX4 versions
  • ROS distro compatibility
  • Non-RPi platform support

Alternatives & Related Tools

Related tools

How is it used?

Start from the recorded entry points below, then validate against the technical checklist.

Technical checklist

  • OK License identified Recorded: MIT
  • OK Maintenance signal Active
  • OK Verification status Official confirmed
  • OK Source evidence attached 1 source record(s)
  • NEEDS REVIEW Latest version recorded Not recorded

Official Links

Metadata & Governance

License MIT β€” Inferred
Commercial modelUnknown
Maintenance statusActive
Verification status Official confirmed β€” Confirmed via the official repository API responses in SourceRefs below.
Latest versionNot recorded
Latest releaseNot recorded
Last activity2026-08-11
Last checked2026-08-13
First seenNot recorded

Related Resources & Dependencies

Recent Activity

new resource medium

New resource: clover

New repository resource added by the sprint promote pipeline.

Related Knowledge

Collections

  • GCS and Telemetry Protocols β€” Ground control software and telemetry protocol repositories for command, monitoring and integration work.
  • MAVLink Ecosystem β€” The protocol and its reference consumers for building or evaluating MAVLink-based UAV integrations.
  • PX4 Development and Simulation Toolkit β€” The components needed to build a local PX4 development and software-in-the-loop verification loop.