I'm wondering what using a throttle curve does to Betaflight. It is, after all, expecting a linear curve from min to max.

Maybe it doesn't matter?

(19-May-2017, 04:38 PM)unseen Wrote: I'm wondering what using a throttle curve does to Betaflight. It is, after all, expecting a linear curve from min to max.

Maybe it doesn't matter?

Doesn't matter. You mess with throttle stick resolution a bit, so with extreme settings you might jump a few steps out of the 1000, but i wouldn't think this could be noticeable at all.

Of course, theoretically a proper throttle curve within betaflight would be better.

Yeah I'm programming the throttle curve on my radio. I haven't had any issue with betaflight while doing that. I like doing it on my radio because I have 3 different curves set up on a 3 position switch.

Why would it be better to do it in betaflight?

I have to agree with Unseen that 2 blade props seem to really feel better for me... I have them on the heavy quad and will be trying them on the lighter one tomorrow... A set of simple Dal 5045x2s are a little noisy but as I fly them they respond in a reliable way... also I seem to destroy them less (but that might just be because my crash scenarios are changing as I learn and get better)...

As for throttle curve... I tried having throttle curve in liftoff for a while because that was the default and it was horrible! It very much obstructed my ability to learn proper throttle control... it wasn't until I set it up to be linear that I started to finally feel like I could figure it out... It just seems like variations to throttle curve would cause extra work in stick movements so I can't even imagine it... maybe I am missing something as far as benefits? (always happy to be proven a newbie as you all know )

(20-May-2017, 03:27 AM)rryyyaann Wrote: Why would it be better to do it in betaflight?

Doing it in transmitter means a bit of resolution loss in the area where you make the curve steeper. Keeping it linear in tx and doing it in fc firmware would prevent that loss. But you can totally ignore that, really. There's no way imho that anyone could notice this difference.

On the other hand, not every tx has elaborate throttle curves to work with, that's why it would still be nice-to-have in betaflight, also because the current throttle-mid/throttle-expo is not much use imho.

(20-May-2017, 04:10 AM)Carl.Vegas Wrote: It just seems like variations to throttle curve would cause extra work in stick movements so I can't even imagine it... maybe I am missing something as far as benefits? (always happy to be proven a newbie as you all know )

I use throttle curve in order to work less on the throttle stick   For me, it's just that the stick travel from zero throttle to "flying throttle" feels too long. Even more so on 4" props. In return it gives me a bit more stick resolution between "flying throttle" and full throttle.

In the end, stick response simply has to "feel" right, so, whatever works for you.

(20-May-2017, 05:46 AM)fftunes Wrote: I use throttle curve in order to work less on the throttle stick   For me, it's just that the stick travel from zero throttle to "flying throttle" feels too long. Even more so on 4" props. In return it gives me a bit more stick resolution between "flying throttle" and full throttle.

In the end, stick response simply has to "feel" right, so, whatever works for you.

Sounds crazy to me...

I think I understand how though

(20-May-2017, 05:46 AM)fftunes Wrote: ... it's just that the stick travel from zero throttle to "flying throttle" feels too long...

I'm pretty sure you already know what I'm going to say here, but I'm sure many people don't, so it's worth saying...

When you start to move the throttle stick up from the lowest point, the actual value that is output to the motors does not start to increase until the throttle exceeds whatever min_check is set to in the CLI. The default min_check value is 1100.

So, the bottom 10% of the throttle is effectively a dead zone unless you change min_check.

(20-May-2017, 03:27 AM)rryyyaann Wrote: Yeah I'm  programming the throttle curve on my radio.  I haven't had any issue with betaflight while doing that.  I like doing it on my radio because I have 3 different curves set up on a 3 position switch.

Why would it be better to do it in betaflight?

As fftunes already pointed out, Betaflight doesn't really support throttle curves, so if you want them, the only place you can set them up is on your radio.

I don't personally use a throttle curve.

There is one thing that you should keep in mind if using a curve though and that's to make sure that the curve won't interfere with stick commands. As long as the throttle value goes below min_check when the throttle is all the way down and above max_check when the throttle is all the way up, there won't be an issue.

If you are using a curve that limits maximum throttle to a value lower than max_check, then you might have some fun trying to use certain stick commands where the throttle needs to be all the way up.

(21-May-2017, 11:31 AM)unseen Wrote: I'm pretty sure you already know what I'm going to say here, but I'm sure many people don't, so it's worth saying...

When you start to move the throttle stick up from the lowest point, the actual value that is output to the motors does not start to increase until the throttle exceeds whatever min_check is set to in the CLI. The default min_check value is 1100.

So, the bottom 10% of the throttle is effectively a dead zone unless you change min_check.

Absolutely, that's quite important and well worth mentioning. I usually have min_check at 1015 or 1020. I forgot to change it at first on my dbug build and the difference is very noticeable (if not to say disturbing, lol - that 10% gap makes it hard to fly intuitively).

(21-May-2017, 11:40 AM)unseen Wrote: As fftunes already pointed out, Betaflight doesn't really support throttle curves, so if you want them, the only place you can set them up is on your radio.

I don't personally use a throttle curve.

There is one thing that you should keep in mind if using a curve though and that's to make sure that the curve won't interfere with stick commands. As long as the throttle value goes below min_check when the throttle is all the way down and above max_check when the throttle is all the way up, there won't be an issue.

If you are using a curve that limits maximum throttle to a value lower than max_check, then you might have some fun trying to use certain stick commands where the throttle needs to be all the way up.

For sure, I have min check i think at 1015. On my curves all the way down is still 0 and full up is 100. I just have it set to increase at the lower end so I feel the quicker response without having to travel all the way up on the gimble. Just my preference.