- 1 Introduction
- 2 Getting started
- 3 Features
- 4 Pinout
- 5 Actuators
- 6 Onboard applications
- 7 Cross compiler
- 8 Tips & Tricks
- 9 Using the MicroUSB for serial data
No more restrictions as from now; with a few simple clicks you can run Paparazzi on the Bebop and have full autonomous flight and much more!
What you need
- A Bebop or Bebop 2 updated to at least firmware v3.3.0
- A joystick, for example this one
- A laptop with Ubuntu installed
Steps to follow:
- Install Paparazzi via the one liner to be found here. Just Cut 'n Paste (CTRL+C from webbrowser then CTRL+SHIFT+V in your Linux terminal) and press ENTER
- Start Paparazzi Center with the default configuration
- Power up your Bebop
- Press the on/off button four times short fast half a second clicks after the bebop is fully powerd up, notice the solid green light on Bebop and solid Red on Bebop 2
- Make a Wifi connection with your PC and the Bebop
- In the Paparazzi center choose "Bebop" Or "Bebop2" in the airframe dropdown menu
- Press the "Upload" button in the Paparazzi Center, wait...
- Select Flight UDP/Wifi in the session menu
- Press execute
Voila, you will get telemetry from your Bebop. Now it is up to you how and where to fly.
TIP: Good video series to watch. Although it is made for the ARDrone 2, the steps are very similar for the Bebop drone.
- Wi-Fi antennas: MIMO dual-band with 2 double-set of dipole antennas for 2.4 and 5 GHz
- Sending power: Up to 26 dBm
- Signal range: N/A
- 4 Brushless Outrunner motors
- Glass fiber reinforced (15%) ABS structure
- High-resistance EPP outdoor hull: Clip and unclip easily to adapt to indoor and outdoor flight, protects the propellers against potential bumps, can be removed to reduce wind factor
- Three-blade auto-block propellers in Polycarbonate with fast disassembly system
- Anti-vibration bumpers
Full Motor details
Handy in case for a simulator motor model
- Magnets: 12
- Stators: 9
- Layers of stator metal: 15
- Copper windings: 34
- Copper diameter: 0.29mm
- Copper resistance: over 50 cm wire ~0.3 ohm
- Flange height 7.67mm
- Flange dia22.7mm
- Axis length 19.4mm
- Axis dia 1.9 mm
- Statorheight 5.55mm
- Stator diam 18.33mm
- Flange weight 3.05g
- Flange and magnets 5.15g (Magnet ~ 1.5mm thick on a Flange dia22.7mm)
- Magnet only (and the glue) 2.1g
- No dat (yet) It ould be nice if you could demolish on of your Bebop 2 motors or a spare one and add your data here.
- Camera with "Fisheye" lens 180° 1/2,3": 6 optical elements and 14 Mega pixels sensor
- Video stabilization: Digital on 3-axes
- Video definition: 1920x1080p (30fps)
- Photo definition: 3800x3188 pixels
- Video encoding: H264
- Photo file format: RAW, DNG
- Internal memory: Flash 8 GB
- Extended memory: Micro USB
- Lithium Polymer 1200 mAh
- Flight time: Around 12 minutes
- Lithium Ion Polymer 2700 mAh
- Flight time: Around 22 minutes
- Max discharge rate 21.5A
- Max charge rate 3.5A
- Parrot P7 dual-core CPU Cortex A9
- Quad core GPU
- 8Gb flash memory
- All fixed on a magnesium shelf that acts as electromagnetic shielding and in the same run as a heat sink for heat dissipation and cooling of the all the onboard processors
- 3-axes magnetometer (AKM 8963)
- 3-axes gyroscope (MPU 6050)
- 3-axes accelerometer (MPU 6050)
- Optical-flow sensor (Fig.8): Vertical stabilization camera (Every 16 milliseconds, an image of the ground is taken and compared to the previous one to determine the speed of the Bebop Drone)
- Ultrasound sensor (Analyzes the flight altitude up to 8 meters)
- Pressure sensor (MS 5607)
- Bebop 1: GNSS (GPS + GLONASS + Galileo, Furuno GN-87F)
- Bebop 2: GNSS (GPS + GLONASS + Galileo, Baidu, )
- 28x32x3.6cm without the hull
- 33x38x3.6cm with the hull
- 380g without the hull
- 400g with the hull
|motor||16.5||4||66||with screws mounting motors|
|camera magnesium frame||7.3||1||7.3||with all screws on it|
|GPS sensor module||16.0||1||16|
|main board||107.0||1||107||measured with all wires on it|
|Dampers||2.1||4||8.4||dampers plus screws|
|Total||510.7||(511,91 measured for another BB2)|
- Operating system: Linux (kernel 3.4.11 #3 SMP PREEMPT)
- glibc: (Sourcery CodeBench Lite 2012.03-57) 2.15
- libstdc++: GLIBCXX_3.4 - GLIBCXX_3.4.16
- 6 Fans Enable
- 9 WiFi Reset
- 73 P7MU IRQ
- 81 GPS Power Enable
- 85 Fan Enable
- 89 VCAM FSYNC gyro
- 90 HCAM FSYNC gyro
- 91 DRDY MPU6050
- 124 Magneto interrupt
- 128 (video) Slew rate??
- 129 VCAM enable
- 130 (video) Slew rate??
- 132 HCAM enable
- 199 BLDC micro-controller reset (forces it into bootloader) ON/OFF
- 200 US Pulse level
- 201 On/Off button (default monitor to files running: /bin/onoffbutton)
- 202 USB Host mode pin 3V3 (HOST_MODE_3V3)
- 203 USB Host mode on
- 204 USB0 OC
- 6 Heating resistor for warming IMU sensors (125000ns period, 0ns duty)
- 8 MPU6050 clock (31510ns period, 15258ns duty) Desired frequency is 32768kHz with 50% duty cycle (period=30517us). Period was set empirically to 31517 to get a 5ms data ready period. Desired frequency is slightly modified to synchronize camera and IMU
- 9 Vertical camera clock (23ns period = 43MHz)
- 11 Horizontal camera lock (77ns period = 13MHz)
- MPU6050 Gyro + Accel MPU6050 (rotation changed in version 2)
- spidev1.0 Sonar (Only data pin connected for generating pulses)
- ttyPA1 GPS (Furuno GN-87F on v1 and Ublox Neo M8N on v2)
- /dev/hx280 Hantro (On2) Video encoder. Hantro chip video encoder used for the HCAM.
- /sys/bus/iio/devices/iio:device0 (p7mu-adc_2) Sonar ADC
The Bebop has 4 Brushless motors, which are controlled by the cypress chip on I2C-1. This Cypress chip contains custom made firmware(BLDC) by Parrot, which can be automatically updated using a bootloader in the ESC part of the mainboard. The firmware from Parrot contains a nice closed loop RPM control, which is automatically tuned inside the factory. Since version 2 Parrot changed the order and rotation direction of the motors.
For more information about how to communicate with the BLDC look at Bebop/BLDC. Or take a look at the "bebop" actuator inside the
The original programs on the Bebop
- /usr/bin/dragon-prog Main program that controls the drone
- /bin/watchdog.sh Checks if Dragon is still running and reboots dragon-prog if it somehow would not be running anymore
- BLDC_Test_Bench Controls the Brushless Motor Controllers for testing and playing sounds etc.
- bcmwl Everything with wifi
- diagnostic Outputs sensor diagnostic
- mk3_camera_eeprom Reads the front camera EEPROM
- config_mt9v117 Configure the bottom camera
For the Bebop you need to use a recent version GNU gcc-arm-linux-gnueabi (Ubuntu/Linaro 4.7.4-2ubuntu1) 4.7.4 provided with Ubuntu since 14.04 LTS.
the past you could also crosscompile with Sourcery CodeBench Lite 2012.03-57 for ARM GNU/Linux from
Greedy Mentor Graphics, previously called codesourcery. However the open'ness there is nowhere to be found anymore, so we'll say "No thanks" to Codesourcery ,now Greedy Mentor"
but if you insist , feel free restricted.
If you somehow need to compile kernel driver files to run on your Parrot Bebop, well, yes, you must use that exact compiler...
Tips & Tricks
Make sure the video_rtp_stream.xml module enabled in the airframe. Receive a video stream with e.g. avplay, vlc or a python app:
$ avplay -loglevel quiet -max_delay 50 -fflags nobuffer rtp://192.168.42.1:5000
$ vlc ~/paparazzi/var/sdp_tmp/192.168.42.1/stream.sdp
You can reset the Parrot Bebop Drone to factory settings. You will loose all your photos and movies recorded on your Bebop. To do this you need to press and hold the power button for 10 seconds. The LED will blink green and orange for a while, then green and the drone will shutdown.
Theoretically is is not important which firmware you use for Paparazzi to fly. But with the latest firware we get better Video imagery. So if you can.. use the latest firmware.
The Paparazzi volunteers test flew the Bebop with Firmware v1.98.11 and v2.0.57, v3.0, v3.2, v3.3, v3.9, v4.0.6
Note that under v4.0.x the hardware accelerated extra nifty features for the front cam don't work (yet..) nOne could use the original encoder from the v3.9 firmware if wanted. So if you need hardware assisted compressed video imagery and have a Bebop 2 do not update to v4.x just yet. Or better fix the camera not working issue...
The v4.0.6 is the latest firmware version know as of 20170610 for Bebop 1. For bebop 2 Latest know is v4.7.x If even newer firmware is available please report any (if any) issues found related to the firmware on e.g. the mailinglist.
The original Bebop2 damper are very soft and can cause oscillations around roll. You can print harder dampers from Thingiverse yourself that will degrade the video quality but remove these oscillations. Use the _nodamp airframe files in that case.
Serial bidirectional teminal access
This is handy if one e.g want to dump and set the build in GPS with software like uCenter on a PC. uCenter also run under Wine.
To do so you first have to set up a connection between U-center and the drone. This done by forwarding the GPS data from the drone to your laptop using a TCP connection. From your laptop this TCP connection is then forwarded to a wine COM port in order to make it readable for U-center.
First open a terminal and listen on your laptop for incoming TCP connections on port 12345.
$ socat -d d pty,raw,echo=0 tcp-listen:12345
Then open a telnet session (while connected to the wifi of the drone) using:
$ telnet 192.168.42.1
and forward the GPS data to the server you just created (in the telnet session):
$ nc <your_ip_address> 12345 </dev/ttyPA1 >/dev/ttyPA1
Switch back to the terminal in which you started listening to the tcp port. You should see that an incoming connection has been accepted. The port to which the connection is transferred to is also shown (see Figure).
The next step is to link this port to a wine COM port. In the following example port /dev/pts/4 is linked to ./com32.
$ cd ~/.wine/dosdevices $ ln -sf /dev/pts/4 ./com32
You should now be able to read the GPS data from u-center under the specified com port.
Using the MicroUSB for serial data
The Bebop, as wel as Disco has this tiny micro USB connector. This USB connector can also be used with help of a USB to Serial conversion board. To use the driver in current firmware OTG serving should be off. Take a look here for more information, photos, connection examples, sourcode and real life example of how to use this port.