ToneAlarm: ignore topic updates with 0 timestamp #11988
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Commander initially publishes a tune_control topic set to 0, which can interfere with the startup tone (as happening on the Pixhawk Cube).
julianoes
approved these changes
May 8, 2019
|
That's ok, but the right fix would be to use |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Commander initially publishes a tune_control topic set to 0, which can interfere with the startup tone (as happening on the Pixhawk Cube).
A nicer solution would be if we had a separate orb_advertise API w/o initial publication.
Fixes #11980.