This page describes the input mapping files read by mppd in the Skycontroller image we examined. Paths are relative to the root of that image’s extracted root filesystem. That image is not the Skycontroller 2’s firmware: its own library decodes the model id it sets, 0x0913, as SKYCTRL_NG, and the Skycontroller 2 is 0x090f. Read this page as the mapping for that image, and do not assume it applies to the Skycontroller 2. The narrative of how the image was examined is at /story/firmware-adventure/. Related pages: /reference/firmware-images/, /reference/evidence-ledger/.
Status legend
Status
Meaning
Verified
The file or bytes were read and the value checked directly.
The only content of drone_manager.cfg is known_drones = ( );. The strings known_drones and cannot find 'known_drones' node in cfg file are present in usr/bin/mppd.
The format is libconfig style. Each file has one root group mapping containing version and the arrays buttons, axes, expo and invert. Every file carries its own header comments listing the action numbers, button bits and axis numbers. The comment lists are identical across all ten files (compared by parsing). Line 1 of each file is a comment of the form Default mappings for <product>.
Element
Content
Source
Status
version
1 in all ten files
line 4
Verified
buttons
Array of { action, buttons }, 8 entries in bebop/, 7 in milos/
line 71 in bebop/, line 71 in milos/
Verified
axes
Array of { action, axis, buttons }, 6 entries in every file
The tables below are the output of a parser written for this page. It reads the buttons and axes arrays and resolves names through each file’s own header lists. Within each folder, the five files differ from each other only in the line 1 comment (checked with diff against mapping_bebop.cfg in that folder). The two folders differ from each other in the buttons array and in two comment strings; the axes, expo and invert arrays are the same.
The action number for emergency was taken from each file’s own button action list. It is 26 in all ten files. A button counts as bound if an entry of the buttons array has action = 26.
File
Folder bebop
Folder milos
Status
mapping_anafi4k.cfg
bound, BUTTON_Z (0x20)
not bound
Verified
mapping_bebop_2.cfg
bound, BUTTON_Z (0x20)
not bound
Verified
mapping_bebop.cfg
bound, BUTTON_Z (0x20)
not bound
Verified
mapping_chimera.cfg
bound, BUTTON_Z (0x20)
not bound
Verified
mapping_disco.cfg
bound, BUTTON_Z (0x20)
not bound
Verified
In the milos folder, BUTTON_Z is bound to center_camera. In the milos files the word emergency appears only in the action list comment and in no other line. This describes the files in the image we examined. Neither folder is known to apply to the Skycontroller 2, which runs a different build.
Scope
Result
Status
buttons array in all ten files
Parsed as described above
Verified
axes array entries with a button mask
None; every buttons field in axes is 0
Verified
Other binding paths (code in mppd, the app side, firmware on the drone, default behaviour when no mapping loads)
Not examined
Open
Emergency handling on a real unit, in either folder
Comments
Spotted a mistake, or tried this on your own Bebop? Leave a note. Comments are kept on this site's own server.