All of this had me wondering, what is the advantage of dRonin over OpenFlight (or BetaFlight)? In David's videos (2016) he was talking about switching his TriFlight over from CleanFlight based, which the video was about, to BetaFlight based. I thought TriFlight was the end goal, so a bit confused about that. Were your boards already flashed with dRonin?
Ken
Ken,
The DTFc boards come flashed with an old version of cleanflight. (can't remember which version) I flash them to dRonin myself. The RCE F3FC boards come flashed with an old version of triflight. TriFlight is an OpenSource Branch/Fork that has additional functions and configuration related to the unique yaw/thrust properties of tricopters. It is merged into another base firmware. The fork/Branch is maintained by @Lauka on
gihub and he posts it up on RCExplorer.se as well. It is currently a branch of BetaFlight but has bounced back and forth between Beta/CleanFlight as support for one or the other has changed over time. The Tri routines have also been merged into dRonin by @jihlein in his branch at
https://github.com/jihlein/dronin/tree/newTriflight.
The difference between the base firmwares comes down to many things including development goals, features, and community. BetaFlight by their own definition is geared mostly to racing, and has been dropping and implied lack of interest in maintaining features that are not beneficial to racing. (ie navigation and nav sensors among others) it was originally a fork of CleanFlight. At some point, CleanFlight wanted to merge a good deal of the BetaFlight code, and made the choice to drop it's current path and Fork from BetaFlight. (it's really murky)
dRonin has a completely different lineage altogether (librepilot, taulabs, etc). It's a relatively small community with pretty much direct access to the developers. One key feature that I really like with dRonin is it's AutoTune.
So, not sure if the clears it up, or murkies it up more...
Cheers!
LitterBug