[DO NOT MERGE] LMC: Mavlink ULog rate control support #612
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
…_for_updates not set" This reverts commit f3a8744. Updating and sometimes ignoring ulog_stream_acked reduces the load, but may cause log to be corrupted due to missing definition data. Need to revert the patch to avoid broken log files.
jnippula
force-pushed
the
DP-8103-ulog-rate-control
branch
from
a72b210
to
e17c4cb
Compare
jlaitine
approved these changes
Jan 30, 2024
maseabunikie
approved these changes
Jan 30, 2024
jnippula
changed the title
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.
Introduce parameter MAV_ULOG_MAX_RT to tune mavlink logging upload message rate (default value: 0.2f).
This makes possible to reduce mavlink data rate in LMC device where CPU load is already very high.