Betaflight-configurator: PID sliders disabling

[illmillrig]

if you set the Master multiplier to 0.5, and the PD Balance slider to 1.5 and save, the sliders disable themselves.

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.86. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[illmillrig]

it's not necessarily 0.5 and 1.5. there are various combinations of slider values that when saved, cause the sliders to disable themselves.

[illmillrig]

Master Slider 0.5
PD Balance 1.2
P and D Gain 1.3

it mostly seems to happens in combinations that have the master slider set to 0.5

[illmillrig]

I think it would be better to manually have to disable the sliders via checkbox, in order to adjust individual RPY PID values, instead of guessing when i've changed those values and the sliders need to be disabled.

[Asizon]

Seems that you are using outdated Configurator version like 10.6.0, for 4.2 please use latest 10.7.0 build

[illmillrig]

for some reason I recall needing to update to 10.7 in order to flash 4.2, but could be mistaken

[Asizon]

I got it! @illmillrig you need to provide more info about your setup, and diff. Anyway, I supose that your are making PID changes with Dmin feature disabled, im able to reproduce it in this way 👍

[Asizon]

From what I can see so far, its breaks in the new functionality for PD ratio calculation that is now aplied to D, but only on Dmin disabled part. Introduced in https://github.com/betaflight/betaflight-configurator/pull/1969

[Asizon]

To reproduce:
Fresh flash
Betaflight 4.2 RC4
Configurator 10.7.0 RC2
1-go to pidtuning tab
2-disable dmin feature
3-put master slider on 0.5
4-put PD Balance slider on 1.5
5-save

[no-response[bot]]

This issue has been automatically closed because the information we asked to be provided when opening it was not supplied by the original author. With only the information that is currently in the issue, we don't have enough information to take action.

[McGiverGim]

I have reproduced with the instructions of @Asizon, I reopen this again...

[McGiverGim]

I let this open, is good to have this bug as a remember, maybe someone gets to a good fix.