ekf2: define max number of range finders separate from max number of … #14102
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.
…mutli uORB topics
Describe problem solved by this pull request
Increasing
ORB_MULTI_MAX_INSTANCES
led to a hard fault in ekf2. This in unintuitiveDescribe your solution
Decouple max number of supported range finders from max number of multi uORB instances
Describe possible alternatives
Dynamically allocate the range finder subscription array
Test data / coverage
Tested in SITL