Alright guys, you convinced me. I'm switching from CF 1.13 straight to BF 3.0. What can I expect? I fly rate, blheli-s escs.

I'm not sure about current status of cleanflight, but I guess that default rates will be FAST

I mean setup-wise Is it very different? I want to change because I'm slow with the current setup so I reconfigure everything. Problem is that I will not have time to get a feel of it, I'm going straight to a local competition.

If I were you, I'd wait with change for after competition ends. You will be pleasantly suprised by how it flies, but I guess you'll need some time to get used to it. Not mentioning, that some things may just go wrong and you may not have time to reconfigure.

Keep in mind Betaflight now have their own Configurator Chrome app. It has a lot of UI improvements, providing easy access to settings only accessible in console before. I don't believe you can configure Betaflight 3.0 without Betaflght Configuration 1.8.

Prepare to start clean after flashing, do not import settings or blindly paste CLI commands. I find it best to take screenshots of key tabs on the previous version and redo them manually on every major upgrade. As always remove props, test arming and failsafe. The CLI commands for LED configuration seems to transfer well tho.

I've been using Betaflight for most of the year, and 3.0 since RC9 - it is fantastic, rivals the bess KISS tunes I've flown.

I finally did it. I'm impressed by the results, it flies great. I also finally ditched the zmr 250 frame and got a nice GepRC zx5.

(24-Sep-2016, 04:56 PM)varkokonyi Wrote: I finally did it. I'm impressed by the results, it flies great. I also finally ditched the zmr 250 frame and got a nice GepRC zx5.

Nice. Only thing i could have thought of, did you get along well with the rc rates/rates system?
As that's maybe the biggest change from a end user point of view, but i think the defaults are pretty much safe for anyone.
Easy to go from there.

Yes, they were comfortable. I will increase them a bit, but as soon as I took off, it felt very natural.

Did anyone have a throttle problem with BetaFlight?

I would have everything set correctly to the best of my knowledge, the motors would spin up on arm, yet I would get no throttle response (increased RPM) till over 25% throttle on the stick.

min_check too high.

Interesting, I never considered that. What does min check do exactly?

(31-Mar-2017, 11:37 PM)Chamathke Wrote: Interesting, I never considered that. What does min check do exactly?

min_check is the value that is used to determine if the stick is in the 'low' position. It's used primarily by the stick commands. However, if you look at the throttle value in the receiver tab as you throttle up, it starts at min_throttle when armed, but as you increase it, it only actually starts to increase once you get past min_check.

For this reason, I always set min check to 10 more than the actual value when the throttle stick is all the way down.

Just to add, the Betaflight wiki is the ultimate source of information. Well worth spending a few hours on it before you switch

Also make sure your RXRanges are set correctly