Skip to content

Lesser-known and undocumented control surfaces, Bebop 2 firmware 4.7.1

Static read of the Bebop 2 4.7.1 firmware’s lesser-known commands and control surfaces by one agent, 2026-10-05. Status: Agent-cited, with these claims re-checked by the commissioning session: dragon-prog imports the decoder-registration symbols for the whole Animation family (cancel, candle, dolly slide, dronie, flip, horizontal panorama, horizontal reveal, parabola, spiral, vertical reveal) and the Follow_me family (start, stop, configure relative and geographic, boomerang, candle, dolly slide, helicoid and swing animations, stop animation, target framing, target image detection), 26 symbols in all, with the same search finding the control ARDrone3PilotingPCMD; libarsdk.so exports 717 g_arsdk_cmd_desc_ symbols (the agent’s 716 excludes one pointer table); bin/dragon_ipc.sh exists; usr/bin/DragonStarter.sh reads persist.dragon-prog.post_cmd; and bin/demoCarpetUSBflashing.sh exists in the image (its call in rcS is commented out). An import is not proof that a callback is registered or reachable; the agent’s registration scan was not re-run. Not re-derived: every message id, the acceptance behaviour of any animation, the send2bhv dispatch, and everything marked Inference.

Documentation of a product the owner has, not a procedure. Nothing here was sent to any aircraft. The animation and follow-me commands move the aircraft autonomously; their acceptance gates (state, battery, speed) were not traced, unlike the flip’s (bebop2-flip-acceptance.md).

Static analysis only. Rootfs firmware/extracted/bebop-2-4.7.1/rootfs, flight program usr/bin/dragon-prog, shared library usr/lib/libarsdk.so, disassembly dp.dis (vaddr = file offset + 0x10000 in .text). No connection was made to any drone, controller, network host, or mcbebop tool. Tags: Verified (I read the instruction, symbol, listing or config this session), Agent-cited (from an existing note), Inference, Open.

The vendored ARSDK XML (264 commands, ardrone3.xml + common.xml only) is a small slice of what libarsdk.so actually describes (716 command descriptors across 23 projects) and a smaller slice still of what dragon-prog implements. dragon-prog registers decoders for 106 commands and generators for 139 state/event messages, all drawn from the Ardrone3, Common, Animation, Follow_me, Controller_info, Thermal_cam and Sequoia_cam projects; every other project in the shared library (Minidrone, Skyctrl, Jpsumo, Rc, Gimbal, Mapper, Powerup, Wifi, Rth, User_storage, Battery, Generic, Debug) has descriptors present but zero call sites in this binary, which is the expected negative control for a product-specific build. The biggest gap between “vendored XML” and “what the aircraft will actually accept” is not a secret command, it is an entire feature the vendored snapshot never included: the Follow_me / Animation project (project ids 134 and 144), which carries nine animation types (flip, candle, dronie, parabola, spiral, horizontal/vertical reveal, horizontal panorama, dolly slide) and a parallel follow-me subsystem with five of its own choreographed animations, all fully wired into dragon-prog with working decoders and generators. None of it is exposed by the 264-command XML the project’s own tooling is built on. Within Ardrone3/Common itself, six commands marked support="090c" have no decoder or generator in this binary (mostly return-home and FlightPlan edge events), and conversely 27 commands marked deprecated or “none” in the XML are still fully implemented (legacy sound alerts, legacy GPS/outdoor/wifi setters, legacy Animations/StartAnimation). The clearest second-flip-path finding is the pre-existing one: Animation.Start_flip and Ardrone3.Animations.Flip are two independent decoders that both deliver message 152 (ANIMATION_START) to the same feature, with the direction enum reordered between them. Outside ARSDK, the sharpest hidden surface is a local-only Unix-socket control channel, dragon_ipc.sh over @/com/parrot/dragon_ipc, whose send2bhv verb lets anything with shell access inject an arbitrary numbered message straight into the behaviour mailbox, bypassing every ARSDK decode and filter step. A second is a config-driven vision-based flight mode, DemoMagicCarpet, off by default, switched on by a USB file drop or the factory FVT boot mode. A third is a persisted property, persist.dragon-prog.post_cmd, that lets anyone set extra command-line flags for dragon-prog itself, taking effect on every future boot.

Quantity Count How counted
g_arsdk_cmd_desc_* symbols in libarsdk.so 716 dynamic symbol table, filtered to DO entries under .data.rel.ro, excluding one false match (g_arsdk_cmd_desc_table, a pointer array, not a descriptor)
Commands in vendored XML (ardrone3.xml + common.xml) 264 ET.parse, counting <cmd> under every <class>
ARCOMMANDS_Decoder_Set*Cb symbols imported by dragon-prog 110 llvm-objdump -T, name list
Of those, confirmed registered (a bl/b to the PLT stub found in COMMANDS_Receive_ThreadHandler) 106 scripted scan of dp.dis; 4 imported-but-unregistered are AnimationStartVerticalReveal, ARDrone3SoundStopAlertSound, SequoiaCamRadiometricCalibStart, ThermalCamDeactivate – each was registered via a shared tail-call/branch rather than its own bl, confirmed present when the search pattern was widened from bl to bl|b
ARCOMMANDS_Generator_Generate* symbols imported 139 same method
Of those, call sites found in dp.dis 138 of 139 ARDrone3GPSSettingsStateHomeChanged has no direct call site in dragon-prog’s own code (it is exported from libarsdk.so as a bare symbol match but the real used name is the longer ARDrone3GPSSettingsStateHomeTypeChanged, confirmed by call-site grep); treated as a likely false positive, not a hidden command
XML commands flagged support containing 090c 150 (various version-qualified forms) direct XML attribute scan
XML 090c commands with neither a registered decoder nor a found generator 6 listed below
Firmware descriptors with a confirmed decoder or generator call site, but absent from the vendored XML entirely 56 all from projects Animation (144), Follow_me (134), Controller_info (140), Sequoia_cam (147), Thermal_cam (142), plus Ardrone3.Piloting.FlatTrim and its two state/event counterparts
BEHAVIOUR_FEATURE_COMMANDS_MSG_* message-id names recovered from the behaviour dispatch table 157 read the 0x574ae0 pointer table directly until the first non-BEHAVIOUR_... string
Of those, never posted anywhere in dragon-prog via the generic poster at 0x6a374 61 scripted scan; includes FLIP (21, the pre-ARSDK3 message id, superseded by ANIMATION_START=152 per the existing flip note), all RC_*, all MAPPER_MINI_*, several wifi/audio/video legacy ids

Positive control used throughout: every “not found” result above was re-run with the same script against a command known to exist (e.g. ARDrone3PilotingPCMD, event 15 FLIP_COMMAND, message id 152) before being reported as a true absence.

Firmware commands present and wired, but missing from the vendored public XML

Section titled “Firmware commands present and wired, but missing from the vendored public XML”

All of these have a confirmed decoder registration (REG) or a confirmed generator call site (GEN) in dragon-prog. “Project(class,cmd)” is the numeric id triple read from the g_arsdk_cmd_desc_* struct.

Command Project(class,cmd) Status Args What it is
Animation.Start_flip 144(0,4) REG Type:enum Agent-cited in bebop2-flip-acceptance.md: a second decoder for the same flip feature as Ardrone3.Animations.Flip, with the enum order FRONT/BACK/LEFT/RIGHT instead of FRONT/BACK/RIGHT/LEFT. Both feed message 152 ANIMATION_START
Animation.Start_candle 144(0,18) REG Provided_params, Speed, Vertical_distance, Play_mode Verified wired to message 152. Inference: a scripted upward camera-reveal animation (“candle”)
Animation.Start_dronie 144(0,8) REG Provided_params, Speed, Distance, Play_mode Verified wired. Inference: a scripted backward-and-up pull-away shot
Animation.Start_parabola 144(0,16) REG Provided_params, Speed, Vertical_distance, Play_mode Verified wired. Inference: a scripted parabolic-arc camera move
Animation.Start_spiral 144(0,14) REG Provided_params, Speed, Radius_variation, Vertical_distance, Revolution_nb, Play_mode Verified wired. Inference: scripted spiral orbit
Animation.Start_horizontal_panorama 144(0,6) REG Provided_params, Rotation_angle, Rotation_speed Verified wired. Inference: a yaw sweep without translation
Animation.Start_horizontal_reveal 144(0,10) REG Provided_params, Speed, Distance, Play_mode Verified wired. Inference: forward reveal shot
Animation.Start_vertical_reveal 144(0,12) REG (imported, registered via shared tail branch) Provided_params, Speed, Vertical_distance, Rotation_angle, Rotation_speed, Play_mode Verified wired. Inference: climb-and-reveal shot
Animation.Start_dolly_slide 144(0,20) REG Provided_params, Speed, Angle, Horizontal_distance, Play_mode Verified wired. Inference: lateral dolly-style pass
Animation.Cancel 144(0,3) REG (none) Verified wired to message 153 ANIMATION_STOP. Cancels whichever of the above is running
Animation.Availability / *_state events (one per animation type above, plus Animation.State) 144(0,*) GEN varies Verified: generator call sites exist for all of these; they report progress/availability of the running animation back to the controller
Follow_me.Start 134(0,1) REG Mode:enum Verified wired (no message id captured for this one – the callback does not call the generic poster at 0x6a374, so its message id was not resolved this session). Inference: begins subject-tracking flight
Follow_me.Stop / Stop_animation 134(0,2 / 0,11) REG (none) Verified wired; Stop_animation posts message 153
Follow_me.Configure_relative / Configure_geographic 134(0,8 / 0,6) REG Use_default, Distance, Elevation, Azimuth Verified wired. Sets the follow-me framing geometry
Follow_me.Start_boomerang_anim 134(0,16) REG, msg 152 (direction/type const 3) Use_default, Speed, Distance Verified
Follow_me.Start_candle_anim 134(0,18) REG, msg 152 (const 8) Use_default, Speed, Vertical_distance Verified
Follow_me.Start_dolly_slide_anim 134(0,20) REG, msg 152 (const 9) Use_default, Speed, Angle, Horizontal_distance Verified
Follow_me.Start_swing_anim 134(0,14) REG, msg 152 (const 7) Use_default, Speed, Vertical_distance Verified
Follow_me.Start_helicoid_anim 134(0,12) REG, msg 152 (const 6) Use_default, Speed, Revolution_number, Vertical_distance Verified
Follow_me.Target_framing_position 134(0,22) REG Horizontal:i8, Vertical:i8 Verified. Moves the subject’s position in frame
Follow_me.Target_image_detection 134(0,24) REG Target_azimuth, Target_elevation, Change_of_scale, Confidence_index, Is_new_selection, Timestamp Verified. Feeds a vision-detected target box to the aircraft (this looks like the controller-side input to the follow-me tracker, not a telemetry output, despite the “state”-sounding name)
Follow_me.State / Mode_info / *_anim_config events 134(0,*) GEN varies Verified generator call sites; telemetry back to the controller about follow-me status
Controller_info.Gps 140(0,1) REG Latitude, Longitude, Altitude, Horizontal/Vertical_accuracy, North/East/Down_speed, Timestamp Verified wired, no resolved message id this session. This is the controller volunteering its own GPS fix to the aircraft – used by the aircraft’s own navigation/return-home when it has no fix of its own. Already present as ControllerInfoGps/ARDrone3GPSSettingsSendControllerGPS style commands in general ARSDK use, but absent from the vendored subset
Controller_info.Barometer 140(0,2) REG Pressure, Timestamp Verified wired. The controller volunteering a barometric pressure reading
Sequoia_cam.Radiometric_calib_start / _status / _result 147(0,3 / 1 / 2) REG / GEN Id / Cam_id, Value, flags Verified wired. Multispectral camera accessory calibration, irrelevant to a plain Bebop 2 unless the Sequoia accessory is attached
Thermal_cam.Activate / Deactivate / Camera_state / Charging_status / Calibration_infos 142(0,1/2/3/7/6) REG / GEN Cam_id, flags Verified wired. Relevant to the FLIR/“Thermal” variant board (milosthermal), present in this generic build but gated by hardware that may not exist on a stock Bebop 2
Ardrone3.Piloting.FlatTrim and its state/event pair 1(0,0), 1(4,0), 1(34,1) REG / GEN (none) Agent-cited gap, confirmed independently: PROVENANCE.md already notes this command is absent from both the vendored snapshot and current upstream, “although the firmware accepts it.” Verified here by reading the descriptor directly (g_arsdk_cmd_desc_Ardrone3_Piloting_FlatTrim exists, project 1 class 0 cmd 0) and confirming the decoder registration at 0x58668, which posts message 6 FLAT_TRIM

XML commands marked supported on 090c (Bebop 2) with no handler found in this binary

Section titled “XML commands marked supported on 090c (Bebop 2) with no handler found in this binary”
Command Project(class,cmd) XML support Deprecated What it would be
Ardrone3.PilotingState.ReturnHomeBatteryCapacity 1(4,15) 090c:4.3.0 no Event: percent battery needed to return home. Inference: superseded by a differently-named event this binary does generate (not traced further)
Ardrone3.GPSSettingsState.ResetHomeChanged 1(24,1) 0901;090c yes Event confirming a home-location reset. Deprecated in the XML, and no generator found – consistent
Common.MavlinkState.MavlinkPlayErrorStateChanged 0(12,1) 0901:2.0.29;090c;090e yes FlightPlan error event, deprecated
Common.FlightPlanSettings.ReturnHomeOnDisconnect 0(32,0) 0901:4.1.0;090c:4.1.0;090e:1.4.0 no Setter for return-home-on-disconnect during a FlightPlan run
Common.FlightPlanSettingsState.ReturnHomeOnDisconnectChanged 0(33,0) same no Its paired state event
Common.FlightPlanState.LockStateChanged 0(17,2) 0901:2.0.29;090c;090e no FlightPlan lock state event

All six are FlightPlan/return-home adjacent and all are plausibly handled by the separate Mavlink-flightplan subsystem (CommonMavlinkStart/Stop/Pause are registered) under names this session did not individually trace through to these specific XML entries; treat the “no handler” result for these six as Open rather than a confirmed gap, since the search only matched on exact normalized command name and a renamed internal symbol would not be found by this method. The six project-0/1 “no handler, no generator” commands overall are rare: 258 of 264 vendored commands do have a matching decoder, generator, or XML support value consistent with “not supported here” (none, deprecated, or a different product).

XML commands marked deprecated or unsupported on 090c that the firmware still runs

Section titled “XML commands marked deprecated or unsupported on 090c that the firmware still runs”

These are the inverse finding: commands the public XML says are gone or not for this product, confirmed still live in dragon-prog.

Command Project(class,cmd) XML says Firmware has
Ardrone3.Sound.StartAlertSound / StopAlertSound / SoundState.AlertSound 1(35,0/1), 1(36,0) support="none" REG at 0x56bdc/0x56b64, message ids 154/155; GEN for the state event
Ardrone3.SpeedSettings.Outdoor / SpeedSettingsState.OutdoorChanged 1(11,3), 1(12,3) deprecated="true" REG at 0x5c528; GEN
Ardrone3.NetworkSettingsState.wifiSecurityChanged 1(10,1) deprecated="true" GEN present
Ardrone3.SettingsState.MotorSoftwareVersionChanged / P7ID 1(16,3/6) deprecated="true" GEN present both
Ardrone3.GPSSettings.SetHome / GPSSettingsState.ResetHomeChanged support 1(23,0) deprecated="true" REG at 0x575dc, message id 107
Ardrone3.PROState.Features 1(32,0) deprecated="true" GEN present
Common.Network.Disconnect 0(0,0) support="none", deprecated REG present
Common.OverHeat.SwitchOff 0(6,0) support="none", deprecated REG at 0x57274, message id 123
Common.Animations.StartAnimation / StopAnimation / StopAllAnimations 0(24,0/1/2) support="0902;0905;0906;0907;0909" (older drones, not 090c) REG present at 0x61678/0x615f4, message ids 133/134 – the legacy pre-ARSDK3 animation trio still works on the Bebop 2 alongside the newer Animation.Start_* family
Common.Audio.ControllerReadyForStreaming, Common.Headlights.intensity, Common.GPS.ControllerPositionForRun 0(20,0), 0(22,0), 0(16,0) support lists only older product codes, not 090c All REG present with working message ids (141, 136, 111/112)
Surface Reached by What it does Needs debug mode? Status
dragon_ipc.sh over Unix socket @/com/parrot/dragon_ipc Local shell only (telnet/ssh after the button-4x root hook, Agent-cited to bebop2-firmware-hooks.md) Three verbs: switch_wifi_band (message id 1, force 2.4/5/auto), dragon_shutdown (message id 0, clean stop), and send2bhv <senderId> <msgId> <dataSize> <dataValue> (message id 100). Verified by reading the script and by tracing the dispatcher in dragon-prog (BEHAVIOUR_Feature_Timers_Callback region, 0x712f0-0x71494): message id 1 and 100 are both read via pomp_msg_get_id and dispatched, id 100 reads a %u%u%u%u payload. send2bhv is a raw escape hatch into the same behaviour mailbox that every ARSDK command funnels into, taking a numeric message id and a 1/2/4-byte value with none of the ARSDK decode, range or type checking that a real command gets No – works on stock firmware, but needs a local shell Verified
persist.dragon-prog.post_cmd property sprop persist.dragon-prog.post_cmd "<flags>" from a local shell; read by usr/bin/DragonStarter.sh (POST_CMD=$(gprop persist.dragon-prog.post_cmd)) and appended to every future dragon-prog launch Appends arbitrary command-line flags to dragon-prog on every boot/restart. Firmware’s own rcS_mode_wifidev uses this exact mechanism to set -V 2 -kkk -n (verbosity + unidentified flags + one more) “for immediate application” when switching into wifi-dev mode No Verified (script read directly)
DemoMagicCarpet flight state / demoMagicCarpet config flag etc/colibry/common/states.cfg:42 (demoMagicCarpet = false; by default) with per-mode override demoMagicCarpetInitValue ("default" vs "fvt" in etc/colibry/*/{default,fvt,simulator}/init.cfg); also reachable by dropping files via bin/demoCarpetUSBflashing.sh over USB mass storage (/usb/ardrone/skel/magic_c*.txt, demo.xml) A dedicated FSM state, ControlStateDemoMagicCarpet (state id 14 in the FSM, confirmed by name in _ZTVN8Mykonos327ControlStateDemoMagicCarpetE and cross-referenced against the Flip acceptance report’s state table), backed by vision-based carpet pattern detection (VisionCarpetDetection, sensors.visionCarpetData.*, RCarpetHorizontal/RCarpetAltitude* thresholds in config). Inference: a position-hold/trajectory demo mode that uses a printed pattern on the ground as a visual anchor, intended for trade-show or FVT bench demos rather than end users fvt mode or a USB file drop; off by default in normal flight Verified existence and gating; behaviour of the state itself Open (not traced)
etc/init.d/rcS_mode_fvt factory test mode Boot-time selection via persist.running-mode property, normally set by the FVT station rather than a user Runs dragon-prog directly (not via DragonStarter.sh), wipes /data/mmc/media, then blinks the status LED in a loop once done. Already extensively documented by adb-survey.md’s FVT1-8 script table (Agent-cited) covering OTP fuse programming, rate-table IMU calibration, per-motor spin-direction checks, and a real test flight with telnet access and wobble scoring Yes – FVT running mode Agent-cited (adb-survey.md) + Verified (read rcS_mode_fvt directly)
etc/debug.conf via DragonDebug.sh Run on every boot and every dragon_shell.sh (re)start of dragon-prog; file edited from a local shell Toggles dynamic_debug (kernel dynamic-debug prints), kmemleak, meminfo, ckcmd (command logging to tcp/file/both via ckcm_log.sh), BLACKBOX (flight blackbox recording to $ARDRONE3_BLACKBOX_PATH), SYSMON (background sysmon.sh) No – reads the flag file unconditionally if it exists Verified (script read directly)
Ardrone3.PilotingSettings.SetAutonomousFlight* family (MaxHorizontal/VerticalSpeed, MaxHorizontal/VerticalAcceleration, MaxRotationSpeed) ARSDK command, support present but version-gated oddly across products Verified REG for all five (message ids 102-106) – these set the speed/acceleration envelope used by autonomous moves (MoveTo, FlightPlan, return-home), separate from the user-facing SpeedSettings.Max* the stock app surfaces. PROVENANCE.md notes upstream has since dropped this whole family; this firmware still honours it No Verified

The single most consequential finding is send2bhv. It is the one surface found this session that defeats the entire ARSDK validation chain by design: every networked ARSDK command passes through a generated decoder that checks argument types, ranges and enum membership before it ever reaches the behaviour mailbox (message 152 ANIMATION_START, message 15 PILOTING_COMMAND, etc. are all examples of that path). send2bhv hands a raw message id and up to 4 bytes of payload straight to the same mailbox with none of that. It is local-shell-only, so it does not change what a phone app or a networked attacker can do, but it is the cleanest confirmation that the real safety boundary in this firmware is the ARSDK decoder layer, not the behaviour/feature/FSM layer underneath it – the layers this session’s earlier flip report showed are otherwise quite carefully gated.

The second most interesting finding is the sheer size of the Follow_me/Animation gap between what the project’s own XML tooling exposes (264 commands) and what the aircraft will actually run (every animation type plus the full follow-me subsystem). None of this is secret in the sense of being absent from Parrot’s wider public ARSDK documentation – it is simply absent from the two-file vendored snapshot this project built its tooling against, which only pulled ardrone3.xml and common.xml. Anyone driving the aircraft only through that snapshot’s 264 commands cannot trigger a spiral, a dronie, a candle, or any follow-me animation, despite the aircraft accepting and fully implementing all of them.

Third, DemoMagicCarpet is the most “Flip-like” find in spirit: an entire FSM state and vision pipeline that a stock user would never see, gated to off by a single config boolean and a mode string, with a USB-drop activation path that looks built for trade-show demo units rather than retail use.

  • The exact behaviour of DemoMagicCarpet’s process/entry functions was not disassembled; only its existence, gating config, and FSM state id were confirmed.
  • Follow_me.Start’s message id, and Controller_info.Gps/Barometer’s message ids, were not resolved (their callbacks do not call the generic poster at 0x6a374 that this session’s scripts searched; they likely write through a different path not traced).
  • The six “no handler found” project-0/1 commands in the XML-vs-firmware table were only checked by exact normalized name; a renamed or merged internal handler would not show up with this method.
  • libcrashdump.so, libflird_client.so, macgyverd, and the network/discovery JSON on tcp 44444 were not opened this session; only dragon-prog, libarsdk.so, libarcommands.so, init scripts and colibry config were read.
  • Minidrone/Skyctrl/Jpsumo/Rc/Gimbal/Mapper/Powerup/Wifi/Rth/User_storage/Battery/Generic/Debug project descriptors were confirmed absent from dragon-prog’s call sites (the expected negative control for a Bebop2-only build) but their descriptor argument lists were not individually reviewed, since they are not reachable on this aircraft.
  • The Debug project (139: Get_all_settings, Set_setting, Settings_info, Settings_list) has descriptors in libarsdk.so but no decoder or generator call site in dragon-prog at all – genuinely inert in this binary, not merely unsupported-but-present. Worth a second look in libdrone.so or another binary this session did not examine.
  • Is the send2bhv unix-socket path reachable from anywhere other than a local shell (e.g. from a privileged app the stock firmware runs), or is root/telnet access via the documented button-4x hook always a prerequisite?
  • What do the -kkk and -n flags passed via persist.dragon-prog.post_cmd in rcS_mode_wifidev actually select in dragon-prog’s argument parser? Not traced this session.
  • Do any of the nine Animation.Start_* commands or the five Follow_me.Start_*_anim commands carry the same kind of state/speed/battery acceptance gating that bebop2-flip-acceptance.md found for the flip, or are they gated more loosely? Not traced.
  • Which of the six “no handler” project-0/1 XML commands are genuinely absent versus routed through a differently-named internal symbol this search missed?

Comments

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