Clover
Robot / hardware buildEducational quadrotor platform pairing a PX4 flight controller with Raspberry Pi and ROS; this entry selects Clover 4.2 construction and the documented ROS Noetic image route. [1] [5] [8]
Build & first use →Official website
- For
- Robotics educators and developers able to assemble and configure PX4 and ROS systems [1]
- Cost
- No current cost or bill of materials established yet.
- Source rights
- Named licenses are documented by part. Includes noncommercial terms. Review licenses
- Unknowns
- tools not fully established. Review gaps
Source researched · Not tested by us
Sources checked · Research details
Licenses & related hardware
- License
- CC-BY-NC-SA-4.0 (noncommercial), MIT · Details by part
Overview
Clover pairs a PX4 flight controller with a Raspberry Pi companion running ROS. This entry selects the Clover 4.2 assembly documentation and the image route described as Raspbian Buster, ROS Noetic and Python 3. The assembly index covers several aircraft versions and identifies 4.2 through the serial-number prefix; a generic Clover label is not enough to select replacement parts. [1] [5] [8]
Is this for you?
- Known limitations
- Hardware and documentation use noncommercial Creative Commons terms while platform software is MIT
- Separate hardware and software revisions are not a qualified pair
- Complete image and matching PX4 payload not preserved by this review
- No assembly or flight validation performed
What you need
Hardware & parts
Assembly & first use
Cost
No current, complete configuration-specific build cost has been established for this profile.
3D preview
Preview not available yet. The reviewed design license includes a noncommercial restriction. The original design is linked; a hosted derivative needs a separate reuse decision.
Model sources
The reviewed design license includes a noncommercial restriction. The original design is linked; a hosted derivative needs a separate reuse decision.
Project notes
Match the frame and controller variant
The 4.2 model page separates polycarbonate decks and guards from carbon-fiber arms and central plates, specifying 2 mm stock for those listed pieces. The separate hardware repository contains DXF, STEP and Inventor files for selected parts. This review preserved that repository at commit 422b00d9e3113c7fe22633d03b59240d1be6a314; it was not fabricated or qualified against the software revision. [7] [12]
The assembly guide allows COEX Pix and Pixracer installation paths, with different mounting arrangements. It also specifies motor orientation, ESC and PDB connections, camera mounting and the flight-controller-to-Pi USB connection. Its warning about motor screw length is specific: it calls for M3x5 screws because longer screws can reach the windings. A parts substitution should be reconciled with the selected assembly, not inferred from a photograph. [6]
The Pi image does not replace flight-controller setup
The image guide distinguishes version 0.22 onward, using ROS Noetic and Python 3, from the older 0.21.2 route with ROS Melodic and Python 2. The separate setup guide recommends COEX-patched PX4 and requires airframe, radio, sensor and flight-mode configuration through QGroundControl. The Pi image and PX4 firmware therefore need their own version records. Neither binary payload was flashed or boot-tested here. [8] [10]
The primary archive contains platform and image-building sources. That availability does not establish a complete, tested dependency set or current compatibility of every external package. No current delivered kit or first-working-system cost was verified. [1] [8] [10]
Marker navigation needs a measured map
The documented map route requires the camera to be configured and ArUco detection, map detection and vision-position output to be enabled. The map file records marker ID, marker size, position and rotations; the rotation fields are in radians. A printed marker's appearance alone does not encode its physical size or its placement in the room. [9]
The guide exposes a map image, pose and debug view for checking the active configuration. It also explains that the published frame differs depending on whether vision-position output is enabled. Those are useful setup checks before interpreting a position estimate, but this review did not validate camera calibration, marker recognition, position accuracy or flight. [9]
What we checked
Source research only; no installation, physical build or performance test performed. No affiliate links added.
Not yet established
- Requirements: tools
- A step-by-step setup summary
Updates
Source files and licenses
Available project sources support research coverage; complete build and commercial qualification remain separate.
| Layer | Availability / license |
|---|---|
| mechanical design | available · CC-BY-NC-SA-4.0 Selected external hardware repository under noncommercial share-alike terms; component/revision matching and manufacturing validation remain separate. [7] [11] [12] |
| electronics | available · CC-BY-NC-SA-4.0 Selected external hardware repository under noncommercial share-alike terms; component/revision matching and manufacturing validation remain separate. [11] [13] |
| firmware | not found · License not fully assessed PX4/COEX firmware route identified, but complete matching firmware source/payload and submodules not preserved in this review. [1] [10] |
| software | available · MIT Clover platform source; external ROS/PX4/dependencies retain their own terms. [1] [3] |
| documentation | available · CC-BY-NC-SA-4.0 Explicit documentation-specific grant in primary README; not the software MIT license. [1] |
Selected marker-navigation route needs configured markers/maps rather than a pretrained learned model or training dataset.
Source licenses differ by layer
Clover's platform software is MIT-licensed. Its README separately assigns the documentation CC-BY-NC-SA 4.0, and the preserved hardware repository carries that same noncommercial share-alike license. The hardware archive includes editable COEX Pix and PDB board files, but their revisions still need matching to a chosen aircraft. The software license must not be treated as permission covering every hardware and documentation use. [1] [3] [11] [13]
This profile records those available sources and configuration boundaries. It does not claim a reproduced aircraft, an unrestricted commercial hardware license, or tested autonomous flight. No fabrication, assembly, firmware installation or flight was performed. [6] [8] [10] [11]
References
Each source links to the exact revision we read. “Used for” shows where this page relies on it.
Project sources
- S001 CopterExpress/clover: README.md
Revision, date & where cited
github.com · revision
28e8970· Accessed Oct 1, 2026
Used for: Overview, Is this for you?, What you need, Hardware & parts and 3 more - S002 CopterExpress/clover: commit 28e8970
- S003 CopterExpress/clover: LICENSE
Revision, date & where cited
github.com · revision
28e8970· Accessed Oct 1, 2026
Used for: Is this for you?, Source files and licenses - S004 CopterExpress/clover: files
Revision, date & where cited
github.com · revision
28e8970· archive file inventory · Accessed Oct 1, 2026 - S005 Clover docs/en/assembly.md
Revision, date & where cited
github.com · revision
28e8970· Accessed Oct 1, 2026
Used for: Overview, Hardware & parts - S006 Clover docs/en/assemble_4_2.md
Revision, date & where cited
github.com · revision
28e8970· Accessed Oct 1, 2026
Used for: Hardware & parts, Assembly & first use, Match the frame and controller variant, Source files and licenses - S007 Clover docs/en/models.md
Revision, date & where cited
github.com · revision
28e8970· Accessed Oct 1, 2026
Used for: Assembly & first use, Match the frame and controller variant, Source files and licenses - S008 Clover docs/en/image.md
Revision, date & where cited
github.com · revision
28e8970· Accessed Oct 1, 2026
Used for: Overview, Is this for you?, What you need, The Pi image does not replace flight-controller setup and 1 more - S009 Clover docs/en/aruco_map.md
Revision, date & where cited
github.com · revision
28e8970· Accessed Oct 1, 2026
Used for: What you need, Assembly & first use, Marker navigation needs a measured map - S010 Clover docs/en/setup.md
Revision, date & where cited
github.com · revision
28e8970· Accessed Oct 1, 2026
Used for: Is this for you?, What you need, Hardware & parts, Assembly & first use and 2 more - S011 Hardware repository license
Revision, date & where cited
github.com · revision
422b00d· Accessed Oct 1, 2026
Used for: Is this for you?, Source files and licenses - S012 Preserved Clover 4.2 fabrication paths
Revision, date & where cited
github.com · revision
422b00d· selected archive inventory · Accessed Oct 1, 2026
Used for: Is this for you?, Match the frame and controller variant, Source files and licenses - S013 Preserved COEX electronics paths
Revision, date & where cited
github.com · revision
422b00d· board archive paths · Accessed Oct 1, 2026
Used for: Source files and licenses
Videos
- S014 COEX (YouTube channel)
The project’s own YouTube channel, linked from the project’s own documentation. Not reviewed by us for accuracy.Revision, date & where cited
YouTube channel COEX · youtube.com · Accessed Oct 4, 2026
- S015 Доставка груза на Клевере 4 на Олимпиаде НТИ 2019 / Clever 4 on NTI Olympics 2019 (YouTube video)
Video from the project’s own channel (COEX), linked from the project’s own documentation. Not reviewed by us for accuracy.Revision, date & where cited
YouTube video COEX · youtube.com · Accessed Oct 4, 2026
- S016 Clover Drone Kit autonomy compilation (YouTube video)
Video uploaded by Oleg Kalachev, linked from the project’s own documentation. Not reviewed by us for accuracy.Revision, date & where cited
YouTube video Oleg Kalachev · youtube.com · Accessed Oct 4, 2026
- S017 Simulating Clover drone in Gazebo (camera, optical flow, rangefinder, LED strip) (YouTube video)
Video from the project’s own channel (COEX), linked from the project’s own documentation. Not reviewed by us for accuracy.Revision, date & where cited
YouTube video COEX · youtube.com · Accessed Oct 4, 2026
Correction guidance · Discussion is not enabled · Profile format 0.6.0-draft.1
Change history
2026-10-04 — Added 4 YouTube reference(s) (S014, S015, S016, S017): official channel or videos linked from the pinned upstream sources. Existing claims, source-check dates and evidence are unchanged.