Preflight tests with proper primary sensor handling #2918
Closed
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.
This branch introduces a new primary sensor parameter for each sensor which is set during calibration, and not yet enforced. I will probably switch this so its enforced if the primary is a UAVCAN device. This is not ready for testing yet. This PR will eventually solve the primary sensor handling related issues on systems with hot-plug sensors such as UAVCAN. As long as the sensor comes online before arming the system will use the right sensor and happily arm. It will only not arm if the primary sensor is not present.