The flight controller implements a number of critical low-level behaviors.
This document is work in progress - do not follow it literally, yet.
Installing Cleanflight Configurator (CFC)
Install Google Chrome
Install the Cleanflight Configurator for Chrome
Updating the FC firmware
TODO
(Update to BTFL 3.3.3 - although successful flight tests have been conducted with 2.4.0 and 3.0.1)
Connecting to the Flight Controller (FC)
Unplug the battery from your drone
double-check the battery is unplugged
Disconnect the Raspberry Pi from the FC
Connect the mini USB cable to your FC and to your base station
Start CFC on your base station
5. Select the correct connection port in the top right corner
Details might vary depending on available connections on your base station, but the correct port should start with:
/dev/tty.serial*
6. Leave the baud rate (number) at the default value of 115200
7. Press “Connect”
You should be greeted by a “Setup” page with a rendering of your drone:
Configuring the flight controller
CleanFlight allows modification of many parameters. We provide a starting configuration that is sufficient for flying.
Setup page
This page can be used to do a quick test of the onboard IMU. Move your drone around and verify that the rendering of the drone moves. Don’t expect it to be perfect, we still need to calibrate everything. We will come back to this page later while performing calibrations (https://ethidsc.atlassian.net/l/cp/WNont9ZB).
Ports page
This page defines which FC ports are used. Default configuration (see image below) is sufficient in Duckietown.
Configuration
Power and battery page
Failsafe page
PID tuning
Receiver
Modes
Adjustments
Servos
GPS (ignorOSD (ignore)
Race Transponder (ignore)
LED strip (ignore)
Sensors
Thethered Logging (ignore)
Blackbox (ignore)
CLI (ignore)
0 Comments