Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Preflight tests with proper primary sensor handling #2918

Closed
wants to merge 6 commits into from

Conversation

LorenzMeier
Copy link
Member

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.

@LorenzMeier
Copy link
Member Author

@mhkabir @pavel-kirienko This is the last bit needed for UAVCAN: Instead of checking if the first unit on the bus is unchanged, it checks now if the prime unit is connected when trying to arm, allowing for a complete order change as long as the highest priority unit remains on the bus. With Pavel's latest startup script change this should not be strictly required, but its the right thing long-term.

@mhkabir mhkabir mentioned this pull request Oct 10, 2015
@LorenzMeier
Copy link
Member Author

Rebased and applied.

@LorenzMeier LorenzMeier deleted the preflight_soft branch October 14, 2015 18:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant