| commit | 5021edb133102f59b0ca591e780a83f49dd2b24d | |
| author | ctzsnooze <chris.thompson@sydney.edu.au> | |
| Fri, 12 Apr 2019 12:05:37 +0000 (12 22:05 +1000) | ||
| committer | ctzsnooze <chris.thompson@sydney.edu.au> | |
| Fri, 12 Apr 2019 12:05:37 +0000 (12 22:05 +1000) | ||
| tree | 5627a9947658b52d9de8ba78c1582ca17c54387d | treesnapshot (tar.gz zip) |
| parent | 9ad2cc84452b8dcfa385bc5d8ea3cf9ab86ad046 | commitdiff |
set dyn_notch_min_hz minimum to 70hz
dyn_notch_min_hz provides a lower frequency limit below which the dynamic notch cannot go.
The current minimum is 100hz.
For low rpm quads (>7" to X class), when the dynamic notch mode is 'LOW', we should allow the user to enter the lowest possible value that can be detected by the FFT.
That is theoretically the centre of the second bin. In low mode that is half-way between 31 and 63hz. In practice, that value will be biased upwards a little bit by the uppers shoulder. In practice the lowest value returned by the FFT is likely to not be less than 60hz.
This PR lowers the limit from 100hz to 60hz, allowing access to the full range of possible FFT tracking frequencies in LOW mode for low rpm quads.
dyn_notch_min_hz provides a lower frequency limit below which the dynamic notch cannot go.
The current minimum is 100hz.
For low rpm quads (>7" to X class), when the dynamic notch mode is 'LOW', we should allow the user to enter the lowest possible value that can be detected by the FFT.
That is theoretically the centre of the second bin. In low mode that is half-way between 31 and 63hz. In practice, that value will be biased upwards a little bit by the uppers shoulder. In practice the lowest value returned by the FFT is likely to not be less than 60hz.
This PR lowers the limit from 100hz to 60hz, allowing access to the full range of possible FFT tracking frequencies in LOW mode for low rpm quads.
| src/main/cli/settings.c | diffblobblamehistory |