telemetry delay for FX protocol warnings - #1172
Merged
Merged
Conversation
This file contains hidden or 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
2 participants
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 PR duplicates the telemetry delay that was added to the V761 and SGF22 Protocols.
Eliminates the "telemetry lost", "telemetry recovered" warnings in OTX and ETX.
Tested using the latest master branch 1.3.4.55.
Using the Q560 sub protocol flying the Cirrus SR22 (QIDI-580) and
Also the QF012 sub protocol flying the QF012 model (SBD Bomber).
Telemetry warnings originally 10 to 15 times per flight and dropped to zero after this PR. Battery telemetry still working.
Added a small update to Protocols_Details.md for the QIDI-580.
Thanks - Rich