[1.14] Fix terrain estimator validity issue #22423
Merged
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.
Solved Problem
fixes: #22357
The issues was caused by the reset function setting
_time_last_healthy_rng_data
to 0, leading to an immediate timeout at the next loop run.Issue got introduces in #21338
and fixed in #22030
I also decided to pull #22117 to reduce the likelihood of hitting another corner care that we fixed recently on the range finder kinematic consistency check.
Verified in replay using https://review.px4.io/plot_app?log=76f8ab88-738c-4a14-a9f7-dd87dd617366

Before:
After:
