Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
From version 6.0 onwards, there has been an increase in multirotor users complaining of problems climbing "like a rocket" or "shooting towards the moon", and the primary source of this problem is caused by the LPF filter applied to the Barometer reading.
INAV has never used this filter for years, and there have never been so many user reports with the same problem. After the filter activation merge, everything got complicated...
This PR removes this filter, which is unnecessary.
Unnecessary because, in the navigation PID controller, there is already a 5Hz LPF filter in the Velocity Z error calculation and also in the Alt-Hold Derivative term.
The tests were carried out on an F450, with a 7.000 MAh battery. This multirotor always fired like a rocket using versions 6 and 7, but not with 5.1. After testing version 7 firmware without the Barometer's LPF filter, it was found that the filter was in fact bad for estimating altitude, and also 1Hz is an extremely low cutoff frequency, it's a little crazy to have this running in the algorithm.