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
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
Bringing the FC software up to date
Identify the version of your flight controller:
2. Download the following new firmware for your version:
SP Racing F3 Acro:
SP Racing F3 OSD:
3.
Installing Betaflight Configurator (BFC)
Follow the instructions on the developer’s website to download the latest Betaflight configurator: https://github.com/betaflight/betaflight-configurator/releases (scroll down for download links):
Connecting to the FC
Unplug the battery
Disconnect the Raspberry Pi from the FC
Connect the mini USB cable to your FC and to your base station
Run the BFC on your base station
Verify the version on the top left of the black and yellow window popping up. It should 10.8.0 (Sec9465)
Verify the recognized devices in the top right corner. You should see (depending on your OS)
Navigate to “Options” on the left column and activate “Permanently Enable Expert Mode”
Go back to the “Welcome” page
Press on “Connect” (top-right corner)
A successful connection will lead to a page looking like this:
Familiarizing with the configurator and FC settings interface
We will explore each setting relevant to the Duckiedrone in detail later. A few high-level observations:
Find your FC firmware version (top-left or bottom-right)
Keep an eye on the FC “CPU Load”. This tells us how much effort the onboard microcontroller on the FC is busy. We should never let it go above 40% with chosen settings, with lower being better.
Bringing the FC software up to date
Verify the
TODO Write flashing instructions for Betaflight 3.3.3
TODO
0 Comments