It’s possible that you can brick your flight controllers due to human error (where FC doesn’t talk to computer anymore, just timeout or says connection fail). You might still be able to fly using that FC as normal, but there is no way you can connect the board to Cleanflight or Betaflight configurator.
In this post we will explain how to setup and configure SBUS and Smart Port telemetry with F3 flight controllers on Betaflight, and F1 Naze32 FC on Cleanflight, with Frsky X4R-SB Receiver.
Here I explain how to flash/update BLHeli_S firmware on your ESC using Cleanflight FC Pass-through.
Mischa, a group member of MI (multicopter international) kindly shared with us how he soldered a memory chip on a Naze32 Acro board.
If you haven’t checked out Boris’s Betaflight, then you are missing out! It’s a modified version of current Cleanflight firmware, with many excellent performance improvements.
Naze32 rev 6 has just been released, I am excited and curious to find out what it is all about :) Is the New version Naze board worth upgrading to?
For those using Cleanflight, here are a few CLI commands that might help you improve your multicopter’s performance! Many people are running these now and having good feedback.
It’s not the first time I heard someone had a quadcopter, lost radio signal, and it just flew away and never be found. This is why setting up failsafe properly is important when there is problem with your radio connection. There is also safety concern regarding what failsafe behaviour should be which we will discuss later.
Just like many other flight controller, when tuning PID I always start with P, then I, and lastly D. Sometimes I go back and find tune P and I, as D changes the effect P and I it has on the quadcopter. The concept of PID has been explained a few times in my previous post, and previous previous post. The Naze32 works pretty well straight out of the box, on my mini quad with stock PID. I did changed a few CLI parameters, before I start playing around with PID.