betaflight-configurator
betaflight-configurator copied to clipboard
betaflight
TPA clarification - % and μs
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
![sonarqubecloud[bot] avatar](https://avatars.githubusercontent.com/in/12526?v=4 "Published by a pub.dev verified publisher"){kind=small}
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!
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
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.
@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 :frowning_face:
tpa breakpoint is a pwm value between 750 and 2250 tpa_rate is between 0 and 1
Take 2: https://github.com/betaflight/betaflight-configurator/pull/3851 :smiley:
