Skip to content

Colibry configuration sets

Colibry is the name of the flight configuration folder etc/colibry/ in the Bebop 2 firmware 4.7.1 image. The files are plain-text configuration read by the main flight program. The narrative is at the firmware story. Related references: firmware images, boxinit services, evidence ledger.

All paths are relative to the image root (rootfs). All values are from the 4.7.1 image.

Status Meaning
Verified The file or bytes were read directly when this page was written.
Agent-cited Taken from an earlier analysis note and not re-checked against the files.
Confirmed independently A source outside the image files states it (here, the live unit’s own log, as reported by another session). Not read from the image.
Open Not established, or the value is not defined in the file named.

Six sets exist under etc/colibry/. common holds a complete set of nine files. Each board set holds a subset of those files plus three mode folders.

Set Top-level files Mode folders (each holds init.cfg) Status Source
common controller.cfg, drone.cfg, estimator.cfg, event.cfg, helper.cfg, reference.cfg, root.cfg, states.cfg, video.cfg none Verified etc/colibry/common/
chimeraboard controller.cfg, drone.cfg, estimator.cfg, event.cfg, helper.cfg, reference.cfg, root.cfg, states.cfg, video.cfg default, fvt, simulator Verified etc/colibry/chimeraboard/
milosboard controller.cfg, drone.cfg, estimator.cfg, event.cfg, helper.cfg, reference.cfg, root.cfg, states.cfg, video.cfg default, fvt, simulator Verified etc/colibry/milosboard/
milosblack drone.cfg, estimator.cfg, helper.cfg, root.cfg default, fvt, simulator Verified etc/colibry/milosblack/
milosthermal drone.cfg, estimator.cfg, helper.cfg, reference.cfg, root.cfg default, fvt, simulator Verified etc/colibry/milosthermal/
mykonos3board controller.cfg, drone.cfg, estimator.cfg, event.cfg, helper.cfg, reference.cfg, root.cfg, states.cfg, video.cfg default, fvt, simulator Verified etc/colibry/mykonos3board/

The file barometer_compensation.csv is named in etc/init.d/rcS as a per-set source file. No file with that name exists in any set in this image.

Item Observation Status Source
barometer_compensation.csv Absent from every set directory Verified etc/colibry/ (search by name over the whole rootfs returned nothing)
milosblack/root.cfg Includes ../../milosboard/reference.cfg, controller.cfg, states.cfg, event.cfg, video.cfg Verified etc/colibry/milosblack/root.cfg, lines 19 to 23
milosthermal/root.cfg Includes its own reference.cfg; includes ../../milosboard/controller.cfg, states.cfg, event.cfg, video.cfg Verified etc/colibry/milosthermal/root.cfg, lines 19 to 23
milosblack and milosthermal init.cfg One line each, @include of the matching milosboard mode file Verified etc/colibry/milosblack/*/init.cfg, etc/colibry/milosthermal/*/init.cfg

Each init.cfg selects the value of three keys. The key workingModeInitValue is the selector used by the logSet and adcFsSet tables.

Set Folder takeOffHeightInitValue demoMagicCarpetInitValue workingModeInitValue Status
chimeraboard, milosboard, mykonos3board default “default” “default” “default” Verified
chimeraboard, milosboard, mykonos3board fvt “fvt” “fvt” “fvt” Verified
chimeraboard, milosboard, mykonos3board simulator “default” “default” “simulator” Verified
milosblack, milosthermal default, fvt, simulator via @include of the milosboard file of the same name via include via include Verified

The live unit’s log names the mode folder it read, default (see Set selection). Which mode folder other runs use is not established.

The set name is the string returned by the runtime property ro.hardware. The matching lines in the image:

File Line Text Status
etc/init.d/rcS 261 COLIBRY_BARO_CSV_FILE_SRC="/etc/colibry/$(gprop ro.hardware)/${COLIBRY_BARO_FILENAME}" Verified
usr/bin/DragonStarter.sh 186 if [ "$(gprop ro.hardware)" = "chimeraboard" ] Verified
bin/ardrone3_shell.sh 8 if [ "$(gprop ro.hardware)" = "milosboard" ] Verified
bin/ardrone3_shell.sh 13 elif [ "$(gprop ro.hardware)" = "chimeraboard" ] Verified
bin/onoffbutton/shortpress_3.sh 22 (if [ "$(gprop ro.hardware)" = "milosboard" ]; then Verified
bin/onoffbutton/shortpress_3.sh 39 elif [ "$(gprop ro.hardware)" = "mykonos3board" ]; then Verified

Two boxinit files also import by the property: etc/boxinit.hosted.rc line 6 reads import boxinit.hosted.${ro.hardware}.rc and etc/boxinit.standalone.rc line 6 reads import boxinit.standalone.${ro.hardware}.rc (Verified). The image contains etc/boxinit.standalone.milosboard.rc and etc/boxinit.standalone.mykonos3board.rc and no chimeraboard equivalent (Verified). See boxinit services.

In bin/ardrone3_shell.sh, the milosboard branch sets PRODUCT="Bebop2" and PRODUCT_MODEL_ID="090c"; the chimeraboard branch sets PRODUCT="Bluegrass" and PRODUCT_MODEL_ID="0916" (Verified, lines 10 and 11, 15 and 16).

Build variant, from etc/build.prop:

Key Value Status
ro.build.alchemy.variant milos Verified
ro.parrot.build.variant milos Verified
ro.parrot.build.uid ardrone3-milos-4.7.1 Verified
ro.parrot.build.version 4.7.1 Verified

No file in the image assigns a value to ro.hardware; the property is only read (Verified by search over the rootfs for the string).

Open points:

Question Status
Which set the Bebop 2 loads. A system log file on one unit’s own storage states the board in its own words (“My hardware is milosboard”) and that the configuration was read from etc/colibry/milosboard/root.cfg with the include path etc/colibry/milosboard/default. That also settles the mode folder for that unit (default). It was reported by another session and is not in the image files. Confirmed independently
Which set other Bebop 2 units load. Only one unit was checked. Open
How common is layered under a board set. Board root.cfg files include their own sibling files by relative path (../drone.cfg, ../controller.cfg and so on). No root.cfg of a board set names common. Board files define only a subset of keys that common defines, which is consistent with a fall-back to common, but the loader that resolves includes is compiled code and was not checked. The layering reading is the earlier analysis’s. Agent-cited
Whether a key absent from a board set takes its value from common. Consistent with it: see the observation below the table. Open

Observation (Verified): the root.cfg of each board set includes paths such as ../drone.cfg and ../../milosboard/controller.cfg. No file etc/colibry/drone.cfg exists, and each mode folder (default, fvt, simulator) holds only init.cfg. Those paths land on the intended files only if the include is resolved from inside a mode folder of the set. That the loader does this is an inference and is Open; the loader was not inspected.

Observation (supporting, not proof): the mass values in drone.cfg are 0.500 kg (milosboard), 0.523 kg (milosblack), 0.604 kg (milosthermal) and 0.390 kg (mykonos3board). Parrot’s published datasheets list a weight of 604 g for the Bebop-Pro Thermal drone and 500 g for the Bebop 2 Power, and the 3D modeling datasheet calls the Bebop 2 a “500g category” drone. The 604 g figure matches milosthermal exactly and the 500 g figure matches milosboard. That pointed a Bebop 2 toward milosboard before the unit’s own log was read; the log then gave the same answer.

Observation (supporting the layering question, not proof): milosboard defines none of the keys maxVerticalSpeed, usrConfigVerticalSpeed, usrConfigMaxAngularRateRefFlying, usrConfigMaxDistance or usrConfigNoFlyOverMaxDistance, and angleRefMaxUser only in chimeraboard and mykonos3board. The limits one Bebop 2 unit reports over its normal protocol equal the common values for these: a maximum tilt of 35 degrees, a maximum vertical speed of 6 m/s and default of 1 m/s, a maximum pitch/roll rotation speed of 300 deg/s, a maximum distance of 2000 m and the geofence off. That is consistent with a board set falling back to common. The match between a protocol field and a config key is an inference from names and units. Two other reported ranges do not match any key here (a maximum altitude of 150 m against usrConfigMaxAltitude 1000.0, and a yaw rotation speed range of 10 to 200 deg/s against usrConfigRotationSpeed 180.0), so not every reported range comes from these files.

The earlier analysis note states the Bebop 2 set is milosboard layered on common; the first half is not established by the files, and the second half is the Agent-cited reading above.

Cell text “inherits or absent” means the file for that set does not define the key. The inherited value is not stated here. Values listed in a row were each read from the file named. A row is marked Open when it has at least one such cell.

milosblack and milosthermal have no controller.cfg, reference.cfg (milosblack), states.cfg, event.cfg or video.cfg of their own; their root.cfg includes the milosboard copy. A cell for those sets reads “via milosboard file” where that include applies.

Set adcFsSet default adcFsSet fvt adcFsSet simulator Status Source
common inherits or absent inherits or absent inherits or absent Open etc/colibry/common/root.cfg (defines only adcTs = 1.0)
chimeraboard 198.3642578125 198.3642578125 200.0 Verified etc/colibry/chimeraboard/root.cfg, lines 8 to 13
milosboard 198.3642578125 198.3642578125 200.0 Verified etc/colibry/milosboard/root.cfg, lines 8 to 13
milosblack 198.3642578125 198.3642578125 200.0 Verified etc/colibry/milosblack/root.cfg, lines 8 to 13
milosthermal 198.3642578125 198.3642578125 200.0 Verified etc/colibry/milosthermal/root.cfg, lines 8 to 13
mykonos3board 198.3642578125 198.3642578125 200.0 Verified etc/colibry/mykonos3board/root.cfg, lines 8 to 13

The comment in root.cfg states: Runtime operation : adcTs = adcTs/adcFs. No unit is written beside adcFsSet.

Set barometerFrequency [Hz] ultrasoundFrequency [Hz] dtGps [s] Status Source
common 75.0 15.0 0.200000002980232 Verified common/helper.cfg lines 84 and 65; common/estimator.cfg line 105
chimeraboard inherits or absent inherits or absent inherits or absent Open none of the three keys in the set’s files
milosboard inherits or absent inherits or absent inherits or absent Open none of the three keys in the set’s files
milosblack inherits or absent inherits or absent inherits or absent Open none of the three keys in the set’s files
milosthermal inherits or absent inherits or absent inherits or absent Open none of the three keys in the set’s files
mykonos3board inherits or absent inherits or absent inherits or absent Open none of the three keys in the set’s files

The comment beside dtGps reads [s] 5Hz measures + quartz clock diff with IMU.

Units from the comments: mass [kg], J [kg.m2].

Set mass Jx Jy Jz Status Source
common inherits or absent inherits or absent inherits or absent inherits or absent Open common/drone.cfg (11 lines, no mass or inertia keys)
chimeraboard 1.893 0.0172 0.0200 0.0295 Verified chimeraboard/drone.cfg lines 18 to 21
milosboard 0.500 0.001491 0.001458 0.003328 Verified milosboard/drone.cfg lines 18 to 21
milosblack 0.523 0.001491 0.001458 0.003328 Verified milosblack/drone.cfg lines 18 to 21
milosthermal 0.604 0.001491 0.001968 0.00416 Verified milosthermal/drone.cfg lines 18 to 21
mykonos3board 0.390 0.000969 0.00133 0.00343 Verified mykonos3board/drone.cfg lines 18 to 21

Units from the comments: speeds [RPM], motorA [N.RPM-2], motorB [N.m.RPM-2]. The comment beside motorA and motorB is written in French and reads Coeff quadratiques. Each array has four entries, one per motor.

Set motorsRpmMax motorsRpmMin motorA (all four) motorB Status Source
common inherits or absent inherits or absent inherits or absent inherits or absent Open common/drone.cfg
chimeraboard 7100.0 1000.0 2.0983e-07 -4.0e-09, 4.0e-09, -4.0e-09, 4.0e-09 Verified chimeraboard/drone.cfg lines 23 to 27
milosboard 12200.0 3000.0 2.15e-8 -2.85e-10, 2.85e-10, -2.85e-10, 2.85e-10 Verified milosboard/drone.cfg lines 23 to 27
milosblack 12200.0 3000.0 2.15e-8 -2.85e-10, 2.85e-10, -2.85e-10, 2.85e-10 Verified milosblack/drone.cfg lines 23 to 27
milosthermal 12200.0 3000.0 2.15e-8 -2.85e-10, 2.85e-10, -2.85e-10, 2.85e-10 Verified milosthermal/drone.cfg lines 23 to 27
mykonos3board 11000.0 3000.0 1.74e-8 2.39e-10, -2.39e-10, 2.39e-10, -2.39e-10 Verified mykonos3board/drone.cfg lines 23 to 27

Unit from the comments: [m]. Entries are in motor order.

Set motorX motorY Status Source
common inherits or absent inherits or absent Open common/drone.cfg
chimeraboard 0.149, 0.149, -0.149, -0.149 -0.186, 0.186, 0.186, -0.186 Verified chimeraboard/drone.cfg lines 31 and 32
milosboard 0.0875, 0.0875, -0.0875, -0.0875 -0.115, 0.115, 0.115, -0.115 Verified milosboard/drone.cfg lines 31 and 32
milosblack 0.0875, 0.0875, -0.0875, -0.0875 -0.115, 0.115, 0.115, -0.115 Verified milosblack/drone.cfg lines 31 and 32
milosthermal 0.0975, 0.0975, -0.0775, -0.0775 -0.119, 0.111, 0.111, -0.119 Verified milosthermal/drone.cfg lines 31 and 32
mykonos3board 0.0775, 0.0775, -0.0775, -0.0775 -0.0975, 0.0975, 0.0975, -0.0975 Verified mykonos3board/drone.cfg lines 31 and 32

Unit from the comment: In deg. The files milosboard/video.cfg and chimeraboard/video.cfg contain only a header comment.

Set videoTiltRange Status Source
common [-75.0, 30.0] Verified common/video.cfg line 8
chimeraboard inherits or absent Open chimeraboard/video.cfg
milosboard inherits or absent Open milosboard/video.cfg
milosblack via milosboard file: inherits or absent Open milosblack/root.cfg line 23
milosthermal via milosboard file: inherits or absent Open milosthermal/root.cfg line 23
mykonos3board [-70.0, 35.0] Verified mykonos3board/video.cfg line 5

The key gainsQuaternionSet is selected by gainsQuaternionSetInitValue and holds three entries: Default, Flip, Rescue. Units from the comments: KP [s-2], KI [s-3], KD [s-1], KDD No units. Within each set listed below, the theta and phi values of the three entries are identical; the entries differ in the psi values. The comments do not name the axes that theta, phi and psi refer to.

Set thetaKP thetaKI thetaKD phiKP phiKI phiKD Status Source
common 140.0 140.0 15.0 140.0 140.0 15.0 Verified common/controller.cfg lines 11 to 17
chimeraboard 64.7 0.65 14.3 64.7 0.65 14.3 Verified chimeraboard/controller.cfg lines 11 to 17
milosboard 264.7408 264.7408 33.0926 242.5376 242.5376 30.3349 Verified milosboard/controller.cfg lines 11 to 17
milosblack via milosboard file via milosboard file via milosboard file via milosboard file via milosboard file via milosboard file Verified milosblack/root.cfg line 20 (values as milosboard)
milosthermal via milosboard file via milosboard file via milosboard file via milosboard file via milosboard file via milosboard file Verified milosthermal/root.cfg line 20 (values as milosboard)
mykonos3board 171.4027 171.4027 21.4253 169.0922 169.0922 21.7435 Verified mykonos3board/controller.cfg lines 11 to 17

The key ctrlGainAltitudeSet is selected by ctrlGainAltitudeSetInitValue. Units from the comments: kp [s-2], ki [s-3], kd [s-1].

Set Name kp ki kd Status Source
common Default 4.170 1.158 5.800 Verified common/controller.cfg, ctrlGainAltitudeSet
common Freefall 2.0 0.0 15.01 Verified same
common Throttle 0.0 0.0 0.0 Verified same
chimeraboard Default 6.161 2.317 7.274 Verified chimeraboard/controller.cfg lines 56 to 69
chimeraboard Freefall 2.0 0.0 15.01 Verified same
chimeraboard Throttle inherits or absent inherits or absent inherits or absent Open not defined in the set’s file
milosboard, milosblack, milosthermal Default, Freefall, Throttle inherits or absent inherits or absent inherits or absent Open ctrlGainAltitudeSet not defined in milosboard/controller.cfg
mykonos3board Default, Freefall, Throttle inherits or absent inherits or absent inherits or absent Open ctrlGainAltitudeSet not defined in mykonos3board/controller.cfg

Units are quoted from the comment beside each key. The key maxHorizontalSpeed has no unit in its comment.

Key common chimeraboard milosboard family mykonos3board Unit (comment) Status Source
angleRefMaxUser [35.0, 35.0] [25.0, 25.0] inherits or absent [30.0, 30.0] [deg] Open */reference.cfg line 7
usrConfigMaxTilt 15.0000009536743 inherits or absent inherits or absent inherits or absent In degrees Open common/reference.cfg line 25
maxVerticalSpeed 6.0 inherits or absent inherits or absent inherits or absent [m.s-1] Open common/reference.cfg line 113
minVerticalSpeedUser -6.0 inherits or absent inherits or absent inherits or absent [m/s] Open common/reference.cfg line 106
maxHorizontalSpeed 12.0 inherits or absent inherits or absent inherits or absent none Open common/reference.cfg line 146
maxHorizontalAcceleration 3.0 inherits or absent inherits or absent inherits or absent none Open common/reference.cfg line 145
maxVerticalAccelerationForFlying 6.0 inherits or absent inherits or absent 4.0 [m.s-2] Open common/reference.cfg line 103; mykonos3board/reference.cfg
speedToReturnHome 8.0 inherits or absent inherits or absent 5.0 In m/s Open common/reference.cfg line 337; mykonos3board/reference.cfg line 31
usrConfigMaxAltitude 1000.0 inherits or absent inherits or absent inherits or absent In m Open common/reference.cfg line 139
maxSpeedIntegral (controller) [10.0, 10.0] inherits or absent [11.6667, 11.6667] inherits or absent [deg] Open common/controller.cfg line 153; milosboard/controller.cfg line 56

“milosboard family” covers milosboard, milosblack and milosthermal. For angleRefMaxUser, milosboard/reference.cfg holds only a header comment, milosblack includes that file, and milosthermal/reference.cfg defines only swipeRotationSpeed = 60.0 with the unit In deg/s (common value 180.0). The key named minVerticalSpeed in mykonos3board/reference.cfg (value -2.5, unit In m.s-1) has a different name from the common key minVerticalSpeedUser.

Each entry gives what the nearest comment in the files states. Where no comment states a meaning, the entry says so.

Prefix or name Comment text or unit Example Status Source
theta, phi, psi (with KP, KI, KD, KDD) KP [s-2], KI [s-3], KD [s-1], KDD No units; axes not named in comments thetaKP Verified common/controller.cfg lines 11 to 22
kp, ki, kd (in ctrlGain* groups) [s-2], [s-3], [s-1] for altitude, position and similar ctrlGainAltitudeSet Verified common/controller.cfg
ctrlGainSpeed kp, ki, kd [rad.m-1.s], [rad.m-1], [rad.m-1.s-1] ctrlGainSpeed Verified common/controller.cfg
motors* and motor* [RPM] for speeds; motorA [N.RPM-2]; motorB [N.m.RPM-2]; motorX and motorY [m]; motorAlpha and motorBeta [rad] motorsRpmMax Verified milosboard/drone.cfg lines 23 to 32
mass, Jx, Jy, Jz [kg], [kg.m2] mass Verified milosboard/drone.cfg lines 18 to 21
Cx, Cy, Cz (NoShell, Shell), Cr [s-1]; meaning not stated in comments CxNoShell Verified milosboard/drone.cfg lines 5 to 11
pwmMotorsModel keys [V.s/rpm], [V/rpm], [V/rpm2], [PWM], [rpm/V], [A/rpm²] motorsKv Verified milosboard/drone.cfg lines 38 to 47
rpm* in controller.cfg [rad/s2] for rpmMaxAttitudeCommandSet and rpmMaxYawCommand; [m.s-2] for rpmMinForControl rpmMinForControl Verified common/controller.cfg
height* and altitudeCommand* [m.s-2] for feedforward and command limits; [m/s2] for heightCommandMax heightFeedforwardCommandMax Verified common/controller.cfg
angleRef*, angleSaturation* [deg], In deg/s angleRefMaxUser Verified common/reference.cfg lines 7 to 17
usrConfig* user-setting limits: In degrees, In deg.s-1, In m, In m.s-1, [g] usrConfigMaxTilt Verified common/reference.cfg lines 25 to 141
maxVertical*, minVertical* [m.s-2], [m.s-1], [m/s] maxVerticalSpeed Verified common/reference.cfg lines 103 to 115
animation* [m/s], [m], [deg] per key animationSpeedMin Verified common/reference.cfg lines 168 to 277
followMe* [m/s], [m/s2], [deg/s], [m], [s] per key followMeDefaultRelativeSpeed Verified common/reference.cfg lines 153 to 159
gainQuatIdealModel* [s-1] for angle and rate, [] for acceleration, [s] for jerk gainQuatIdealModelTiltAngle Verified common/reference.cfg lines 30 to 33
verticalModel* [s-1] for Cz terms; [kg-1] for gamma terms; [m.s-2] for covR verticalModelInitCz Verified chimeraboard/estimator.cfg
battery* [Wh] for energy; [V] for voltage; [V²] and [] for model noise and beta batteryEnergyMax Verified milosboard/helper.cfg, common/estimator.cfg
shutdownVoltage, nominalVoltage [V]; the comment on shutdownVoltage reads Will be compared with the estimated no load voltage shutdownVoltage Verified common/estimator.cfg line 251
landingPower, hoveringPower, RTHPower [W] hoveringPower Verified milosboard/helper.cfg
ultrasound*, altitudeUS*, Us* [Hz] for frequency; [m] for noise and bias ultrasoundFrequency Verified common/helper.cfg lines 48 to 51, common/estimator.cfg line 105
gps* and threshold*Gps [m], [m/s], [°]; gpsLag has no unit gpsAltDeviationErrorMax Verified common/helper.cfg lines 57 to 64
altGroundDetectThreshold, flyawayDetectionActive In m; boolean altGroundDetectThreshold Verified common/event.cfg, milosboard/event.cfg
filterImu* filter coefficient arrays; no comment filterImuBCoef Verified common/helper.cfg lines 9 and 10
adcTs, adcFsSet Runtime operation : adcTs = adcTs/adcFs adcFsSet Verified common/root.cfg line 3 (adcTs and the comment); adcFsSet itself is defined in the board sets’ root.cfg, lines 8 to 13
logSet, enabledSensorsSet selectors on workingModeInitValue; logging verbosity per node; sensor enables logSet Verified common/root.cfg
fusion*, enabled* booleans; no comment fusionVzGps Verified milosboard/helper.cfg line 11

Comments

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