telemetry: remove gps_raw_timeout #2165
Closed
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
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.
I wonder if this timeout is necessary, and I wonder if it could cause issues sometimes. Right now I have an issue where the MAVSDK health changes the global_position and local_position to "false" for no apparent reason, and I wonder if that could be this timeout.
Also none of the other telemetry streams have a timeout. So if a message stops coming, the state is "frozen". I wonder why this one should be different. Especially given that it is a fallback (MAVSDK should rely on the flags in the SYS_STATUS message if they are set properly).