Lagrange v0.4.0: drones (release notes)¶
v0.3 added arms and the electrical and thermal domains. v0.4 adds drones: rotors built from their propellers’ blades, wind and turbulence, GNSS, magnetometer and barometer, a sample quadcopter that flies on its own power system, and PX4 and ArduPilot flying it in lockstep.
Status: released on 2026-10-25 as v0.4.0, at the owner’s request.
Highlights¶
Rotors.
RotorAPI_1on rotor joints, with the propeller’s hand, its mount (puller or pusher) and its propeller file (*.prop.yaml: blade chord, twist and sections from root to tip).The
coefficientsfidelity: thrust and torque from measured CT and CP, inflow lag, Cheeseman–Bennett ground effect.The
bemfidelity: blade-element momentum on the propeller’s geometry, in climb, descent, forward flight and wind; turning the wrong way or mounted back to front, a propeller gives what a real one gives. Checked against NACA Report 640’s full-scale propeller, with nothing fitted. Each propeller is tabulated once at load, so a step is a lookup.Folding blades that hang folded when stopped and open as they spin up.
Rotors are drawn as their blades in the viewer, spinning and folding.
Aerodynamics and wind. Link drag (
AeroAPI_1) against a logarithmic mean wind with Dryden turbulence; the wind reaches the rotors (env/wind/velocity).Sensors. GNSS, magnetometer (World Magnetic Model 2025) and barometer (ICAO standard atmosphere) on the site’s geo origin, published on ROS 2 as
NavSatFix,MagneticField,FluidPressureandTemperature.Autopilots. PX4 v1.17.0 SITL through its simulator MAVLink interface, and ArduPilot Copter-4.7.2 through its JSON interface, both in lockstep (
--mavlink px4|ardupilot). Both fly a square mission, calm and in 8 m/s of gusty wind.Electrical. Small fast motors at 50 µs; a low battery sags the bus and costs thrust.
Samples.
quad_x500(URDF, overlay, USD) with generic 10-inch propellers matched to the measured APC 10x4.7 SF; variants with folding blades and with motors under the arms (pushers); two- and three-blade propellers; theopen_fieldworld; profiles for hover, gusty wind and the blade-element fidelity.Docs. The drone tutorial, from the quadcopter’s files to a PX4 mission (
docs/guide/tutorial-drone.md, run bytools/ci/tutorial_drone.sh).
Acceptance (roadmap §5)¶
Epic |
Acceptance |
Status |
Evidence |
|---|---|---|---|
Rotor aero |
|
met, with owed items |
|
Aerodynamics and wind |
Spectra and field tests |
partly met |
Dryden variances and correlation time ( |
MAVLink bridge |
Mission scenario in |
met |
|
Sensors |
Sensor tests |
met |
|
ESC and battery at 50 µs |
Coupling tests at J = 1e-5 kg·m² |
met |
|
Sample quadcopter and tutorial |
Tutorial runs in CI with SITL in a container |
partly met |
The tutorial runs headless with both SITL steps on the development machine, and in the container image without them ( |
Rebase in flight |
|
deferred |
Needs the runtime rebase (C5), which the owner deferred to v0.7 |
Known issues¶
Blade-element limits. No wake skew or blade flapping beyond the hub moment; no stall delay, so a highly pitched propeller’s thrust near static is under-predicted (aerodynamics.md §7.1).
Dryden turbulence. MIL-HDBK-1797 equation numbers are marked TODO(verify) in the code.
Viewer. Rotors at hundreds of rad/s are drawn at the frame rate, so the blades strobe.
Start-up warnings.
lagrange validateand the Python API build a run before they apply a profile, so they log that rotors and geo sensors need their site parameters even when the profile gives them.From v0.3: Jolt’s drive-wheel slip, Nav2’s occasional start-up discovery failure.
Not run while GitHub Actions are disabled: the sanitizer builds and the nightly jobs. Everything else was verified locally with colcon.
Release checklist¶
[x] Every v0.4 epic done or moved, with evidence above
[x] Release notes drafted
[x] Gated changes merged under the v0.4 mandate listed for review (
progress.md)[ ] Owner review of those merges (the aerodynamics and geo sensor schemas,
RotorAPI_1’s propeller and mount)[ ] GitHub Actions re-enabled and green on
dev[x] Released:
devmerged intomainand taggedv0.4.0on 2026-10-25 at the owner’s request (release-please could not run with GitHub Actions disabled)