Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mavlink receiver fixes #17438

Merged
merged 11 commits into from
May 2, 2021
Merged

mavlink receiver fixes #17438

merged 11 commits into from
May 2, 2021

Conversation

julianoes
Copy link
Contributor

This contains various cleanup in mavlink and mavlink receiver the most notable being a different handling of how to keep track of sequence numbers for various components.

Extraced out of #17404.

@julianoes julianoes requested a review from dagar April 21, 2021 13:57
Without these fields the pre-arm check would complain and fail.

Also, the voltage is adjusted to be at around 70% rather than 30% which
would almost start to trigger warnings.
Instead of only keeping track of the sequence ID of specific "supported"
components, we now keep track of any sysid/compid of an incoming
message. Before this change, unknown components (such as jMAVSim) would
completely screw up the mavlink message stats and create confusion (at
least in my case).

With this change we currently keep track of up to 8 other components.
Once we reach the limit, we will print a warning.
In my opinion this makes it much cleaner and will allow mavlink main to
directly call the receiver.
This fixes the problem where jMAVSim changed the sequence number of
MAVLink messages that it forwarded. With this change it keeps the
sequence number as it receives the messages which prevents forwarded
messages from QGC with wrong sequence numbers to be interpreted as
messages lost.
This is more inline with SITL.
@dagar dagar merged commit abee13d into master May 2, 2021
@dagar dagar deleted the pr-mavlink-fixes branch May 2, 2021 17:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants