Skip to content

Conversation

nerdCopter
Copy link
Member

@nerdCopter nerdCopter commented Mar 20, 2024

Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

Copy link
Contributor

Do you want to test this code? Here you have an automated build:
Betaflight-Configurator-Android
Betaflight-Configurator-Linux
Betaflight-Configurator-Windows
Betaflight-Configurator-macOS
WARNING: It may be unstable and result in corrupted configurations or data loss. Use only for testing!

@haslinghuis haslinghuis merged commit 3dff819 into betaflight:master Mar 21, 2024
@ChrisRosser
Copy link
Contributor

Incoming pedantry. 🤣

0.65 is not a % value. We need to multiply the number by 100 as well.
I'm not sure us makes this more understandable. If one is using Dshot then the breakpoint is not a microsecond value at all but rather a value between 0 and 2000 I think.

@nerdCopter
Copy link
Member Author

@haslinghuis , should we revert Configurator? i'm fine with such.

correct, but humans will read 0.65 as 65% quite easily. pardon any break-point mishaps ☹️

@haslinghuis
Copy link
Member

tpa breakpoint is a pwm value between 750 and 2250
tpa_rate is between 0 and 1

Take 2: #3851 😃

@HThuren
Copy link
Member

HThuren commented Mar 21, 2024

in fact a good change

chmelevskij pushed a commit to chmelevskij/betaflight-configurator that referenced this pull request Apr 27, 2024
@nerdCopter nerdCopter deleted the 20240320_TPA_language branch October 31, 2024 15:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: COMPLETED
Development

Successfully merging this pull request may close these issues.

Change TPA rate and Breakpoint to Percentages for ease of understanding
4 participants