Skip to content

Settings decisions for this aircraft

Deliberate changes to the drone’s configuration, as distinct from the observations in the other files. One row per decision: what changed, who decided, why, and what the aircraft read back afterwards. Values here were read from the drone, never assumed.

Anything in this file can be undone with one send_command. All of it is in /data/dragon.conf on the aircraft, which survives power cycles.

setting value how it got there
geofence (NoFlyOverMaxDistance) on set by FreeFlight Pro, kept on Ryan’s decision
max distance 150 m tightened from 2000 m, Ryan, 2026-10-02
max altitude 30 m as found
max tilt 8° as found
max vertical speed 1 m/s as found
max yaw rotation speed 13 °/s as found
max pitch/roll rotation speed 80 °/s as found
return-home delay 30 s restored after the app changed it to 3 s
return-home minimum altitude 20 m as found
banked turn off restored after the app enabled it
hull protection off as found (no hull fitted)
outdoor mode on as found
video autorecord on as found
country US, automatic as found

2026-10-02: distance limited to 150 m and actually enforced

Section titled “2026-10-02: distance limited to 150 m and actually enforced”

Ryan asked for the three settings FreeFlight Pro had changed to be reverted, and for the max distance to be tightened. Those two instructions conflict on this aircraft, so the geofence was not reverted and that was said plainly rather than resolved quietly.

Parrot’s wording for NoFlyOverMaxDistance is “1 if the drone can’t fly further than max distance, 0 if no limitation on the drone will be done”. The aircraft had shipped to us with the geofence off against a 2000 m limit, which is to say with no enforced limit at all. Reverting it would have made tightening the distance cosmetic.

Ryan confirmed afterwards: the geofence stays on, so the 150 m is enforced.

Read back from the aircraft: geofence 1, max distance 150, return-home delay 30, banked turn 0. Done through mcbebop with arming, the reason recorded, then disarmed.

2026-10-02: two settings restored after the phone app changed them

Section titled “2026-10-02: two settings restored after the phone app changed them”

Connecting FreeFlight Pro 5.2.7 changed three settings without being asked to, apparently by pushing its own stored preferences on connect. Return-home delay (3 s back to 30 s) and banked turn (on back to off) were restored. See drone state for the before and after.

The general caution, worth repeating here because it governs this whole file: for any app that syncs preferences, opening it is a write. Only a before-and-after read can tell you what moved.

  • Max altitude is 30 m, which is low for anything but a close hover. It was found that way rather than chosen.
  • The return-home minimum altitude is 20 m against a 30 m ceiling. If a return-home triggers, the aircraft climbs to 20 m first. Those two numbers are close together and worth thinking about deliberately.
  • Outdoor mode is on and hull protection is off, which is correct for flying outside without the indoor hull, and wrong if the hull goes on.

Comments

Spotted a mistake, or tried this on your own Bebop? Leave a note. Comments are kept on this site's own server.