Skip to content

Bebop 2 Flight Controller Interface — v4.7.1

SUPERSEDED in part: read HARDWARE_REVERSE_ENGINEERING.md “Read this first”

Section titled “SUPERSEDED in part: read HARDWARE_REVERSE_ENGINEERING.md “Read this first””

This map was written early and several central claims did not survive checking against the rootfs. Specifically: there is no libColibry or libNavdata (Colibry is a config namespace read by dragon-prog), libCondor is the vertical-camera image engine and not the flight controller, setAttitude is not the pilot’s attitude setpoint, the loop rate is near 200 Hz and not 90 Hz, and the motor mixing signs are unverified. The corrections about I2C for motors, GPS on ttyPA1, and MAVLink ports existing only under ArduCopter stand. The rest below is kept for history.

The Bebop 2’s flight control stack is built on three core components:

Layer Library Purpose
Commands libARCommands Receives attitude/thrust commands from controller
Stabilization libColibry Attitude control, PID gains, flight modes
Sensors libNavdata IMU, barometer, sonar, optical flow telemetry
  • Function: ARCOMMANDS_Decoder_SetCommonControllerIsPilotingCb
  • Purpose: Signals when controller starts/stops issuing commands
  • Gate: Flight controller only responds if this is true
  • Function: setAttitude(roll, pitch, yaw, thrust, roll_rate, pitch_rate)
  • Purpose: Sets desired attitude and vertical thrust from controller
  • Thunk at: 0x00033b30 → real impl in libColibry
  • Flow: Deserialized from MAVLink → setAttitude() → Colibry stabilizer
  • Thread: ACQCON_colibry_Thread_Handler at 0x0004dd18
  • Rate: Colibry runs at ~90 Hz (sensor fusion cycle)
  • Queue: Reads ~2544-byte state frames from ringbuffer
  • Outputs: Motor commands to unified BLDC controller via I2C /dev/i2c-1
  • Function: getManualFlightUnstabilized(Manager *this)
  • Purpose: Returns TRUE if acro mode (no gyro stabilization)
  • Default: FALSE (attitude/altitude hold enabled)
dragon-prog (flight daemon)
↓ (I2C /dev/i2c-1)
Parrot Unified BLDC Controller Board
↓
Four brushless motors (roll, pitch, yaw, vertical thrust mapping)

Motor Wiring (from service manual):

  • Front-Left: Roll + Pitch + Yaw
  • Front-Right: Roll - Pitch - Yaw
  • Rear-Left: Roll - Pitch + Yaw
  • Rear-Right: Roll + Pitch - Yaw

⚠️ I2C is the motor interface, not UART. /dev/ttyPA1 is the GPS port (see rcS_gps, gps_config.txt). Test binaries BLDC_Test_Bench and test-BLDC reference /dev/i2c-1. Do NOT write to ttyPA1.

Stock Dragon telemetry (not UDP broadcast):

  • IMU data (accel, gyro) @ 200 Hz raw → downsampled to 90 Hz in Colibry
  • Barometer (altitude, vertical velocity)
  • Sonar (ground distance, confidence)
  • Optical flow (horizontal velocity from downward camera)
  • Battery voltage, motor currents
  • Routed via ARCOMMANDS protocol (binary) to ground station via WiFi, not MAVLink UDP

⚠️ UDP ports 14550/14551 do NOT exist on stock firmware. They only appear when ArduCopter is running (button 3× press). Stock Dragon’s MAVLink support is flight-plan playback only (ARCOMMANDS MavlinkStart/Pause/Stop commands via libarmavlink.so), not live telemetry streaming.

Output when ArduCopter is active (both ports are bidirectional MAVLink):

  • Port 1: udp:192.168.42.255:14550 — Primary MAVLink link (SERIAL0, typically QGroundControl)
  • Port 2: udp:192.168.42.255:14551 — Secondary MAVLink link (SERIAL1, companion scripts)
  • Intercept setAttitude() calls to modify attitude targets before they reach Colibry
  • Use case: Custom stabilization filters, aggressive damping
  • Access: Already exposed via command protocol; no firmware mod needed
  • Subclass getManualFlightUnstabilized() condition
  • Use case: Position hold, waypoint nav
  • Access: Would need firmware rebuild (not currently trivial)

3. I2C Motor Controller (Proprietary Protocol)

Section titled “3. I2C Motor Controller (Proprietary Protocol)”
  • Motor control is on I2C /dev/i2c-1, not UART
  • Single unified BLDC controller board, not four independent ESCs
  • Use case: Motor testing, characterization, custom firmware on the board
  • Risk: Proprietary I2C protocol (not documented); test binaries exist (BLDC_Test_Bench, test-BLDC) but no public interface
  • Requires: Reverse-engineering the BLDC board firmware or using Parrot’s test utilities
  • Colibry ringbuffer lives in shared memory, not on disk
  • Use case: Observer pattern (read gyro/accel raw before attitude control runs)
  • Access: Would need to mmap() the shared region; offset/layout unknown without symbols
  • Difficulty: High (no public symbols; would need to reverse with GDB on the drone)

Safe starting points with unmodified firmware:

  1. Enable telnet debug console (read-only, root shell)

    Terminal window
    # Press power button 4× fast
    telnet 192.168.42.1 # No password, root access
    # View logs, check systemctl status, read sensor data
  2. ArduCopter override (takes direct control)

    • Press power button 3× fast → ArduCopter launches from /data/ftp/internal_000/ardupilot/
    • Takes ~10s to boot
    • Publishes bidirectional MAVLink on udp:192.168.42.255:14550 (SERIAL0/GCS) and 14551 (SERIAL1/companion)
    • Bebop’s Colibry stabilizer is fully bypassed
    • Listen with:
    Terminal window
    nc -u -l 0.0.0.0 14551 # Receive broadcast telemetry from drone
  3. Dump Colibry logs (if debug mode available)

    • Check /etc/debug.conf for flags in /data/
    • DragonStarter.sh -N enables navdata logging
    • Read logs from /data/ftp/internal_000/ardupilot/logs/

Power on & confirm baseline:

  • Does it boot to a status LED pattern? (should be blue when armed)
  • Can you connect via WiFi to Bebop2-XXXXXX?
  • Can you reach 192.168.42.1 with telnet or netcat?

If targeting custom firmware:

  • The manifest.xml points to Parrot’s Gerrit (internal). Source not public.
  • Rebuild barrier is libColibry + motor bootloader (proprietary).
  • Best path: Modify command layer (ARSDK) or run ArduCopter parallel (less risky).

Built from: firmware/bebop-2-family_v4.7.1.plf extracted & analyzed with Ghidra
Symbols recovered: 8,437 functions from stripped ARM ELF
Analysis date: 2026-10-01

Comments

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