Mavlink logger: do not use reliable transfer #498
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
jnippula
force-pushed
the
mavlink-logger-speedup
branch
from
ed29f19 to
3612caf
Compare
jnippula
force-pushed
the
mavlink-logger-speedup
branch
from
3612caf to
4b265c7
Compare
|
This is obsolete PR only for testing. New implementation already merged. This PR can be closed. |
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.
Reliable transfer mode requires ack for every message send over mavlink. This slows down the logging start for several seconds causing buch of data missing in the beginning of the log.