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

Fallback to mavlink system ID if no UUID available [2] #109

Merged
merged 7 commits into from
Sep 29, 2017

Conversation

julianoes
Copy link
Collaborator

The PR #80 got lost because it was only merged into another branch.
Therefore, I'm adding it again.

This changes the logic so that you the UUID is used if available but the
mavlink system ID is used as a fallback option. The fallback happens if
3 requests for the autopilot_version are unsuccessful or if the
AUTOPILOT_VERSION.uid field is 0.
This allows to direct the MAV_CMD_SET_MESSAGE_INTERVAL commands.
We use a timeout of 0.5s to slow the retries down. Otherwise, we can run
into the case that the retries are exhausted just because many
components send heartbeats at the same time, or if somebody sents
heartbeats at a high(er) rate.
@julianoes julianoes merged commit e623eac into develop Sep 29, 2017
@julianoes julianoes deleted the uuid-or-sysid branch September 29, 2017 13:52
dlech pushed a commit to dlech/MAVSDK that referenced this pull request Jan 14, 2022
MoCap Odometry::MavFrame enum values change
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.

1 participant