Skip to content

Open questions

  • LED flashing quickly with noError. The user guide says fast red = motor error, but the drone reported no current or last motor error. Is the blink a different state (no controller, boot) or are the two out of sync? Next: note the LED with a controller connected vs not.
  • Why no beacon on the first power-up? Came up after a power cycle.
  • What is in flightplans/flightPlan.mavlink? Answered 2026-10-02: there is no such file; the directory is empty over both FTP routes. The filepath the drone reports is where one would go. See drone state.
  • Video autorecord on, 0 videos stored, 48 flights. Were they deleted, or is autorecord new?
  • Roll +3.74° at rest. Bench tilt or IMU offset? Check with a level and compare with flat-trim state.
  • Home type preference FOLLOWEE. Was Follow Me purchased/used in FreeFlight?
  • Anti-flicker reports 50 Hz in the US. Is it because no controller sent the frequency this session?
  • Bad sensor packet at first contact. Which buffer, how often, what bytes? Needs raw-frame logging.
  • GPS accuracy fields outside documented values (−124 to 119 instead of −1) without a fix. Uninitialised, or meaningful?
  • Does setting the date/time from our side change anything? Partly answered 2026-10-03: FreeFlight Pro does set it (Set current date and Set current time on connect), so the drone’s clock is real after an app has connected and an uptime before that. Whether that changes media names or log stamps is still untested.
  • 5 Hz attitude: can the rate be raised on stock firmware, or is that the ceiling for ARSDK3 telemetry?
  • ArduPilot route: install via FTP, then 3 presses. Needs Ryan’s approval; calibration session props-off first.
  • Per-unit radio NVM on the aircraft vs the generic file in the image Answered 2026-10-02: they are the same file. It is an unspecialised Broadcom template (boardnum=${serno} literal, placeholder MAC); per-unit calibration lives in the chip’s OTP. See drone state.
  • Live ro.hardware value Answered 2026-10-02 from the drone’s own system log, no shell needed: milosboard. See drone state.

  • Camera tilt range mismatch. Over ARSDK the drone reported tilt −83° to +17° (CameraSettingsChanged), but common/video.cfg says videoTiltRange = [-75, 30] and mykonos3board [-70, 35]. Different quantities (virtual gimbal vs video crop), or another config?

  • What is ckcm/ckcm.bin? Answered 2026-10-02: the live ulogcat system log, not camera calibration.

  • Why does a milosboard unit log Mykonos3 board : init done? Answered 2026-10-02: both strings are literal in the kernel, which also has its own Milos board GPIO line. Shared code under the older platform name.

  • bcmwl nvram_dump returns Unsupported on this firmware, so the radio’s runtime values could not be read back. Another way in?

Added 2026-10-02 (post power-cycle, cheap to check next shell session)

Section titled “Added 2026-10-02 (post power-cycle, cheap to check next shell session)”
  • Does the boot counter read 16? It read 15 before the battery swap, and updater.log should gain one no-op scan. Confirms the counter is per-boot.
  • Did Debug/current/ckcm.bin roll into debug_02.tar.lzo? It was at about 750 KB against a 1 MB cap.

Video stream, needs one capture to settle (added 2026-10-02)

Section titled “Video stream, needs one capture to settle (added 2026-10-02)”
  • Does the stream contain IDR frames? The NAL-type counts we have read only the outer header byte of each packet, so the 740 FU-A packets could be carrying anything. Count the second byte of each FU-A payload.
  • Why eight STAP-A per frame? Repeating SPS/PPS is one small packet per frame at most. Either the aircraft aggregates most NALs regardless of size, or it emits several slices per picture. The same capture answers both.

Comments

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