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.

Sign up for GitHub

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

Jump to bottom

MAV_CMD_SET_MESSAGE_INTERVAL (and GET) clarifications #173

Open
hamishwillee opened this issue Mar 3, 2019 · 0 comments
Open

MAV_CMD_SET_MESSAGE_INTERVAL (and GET) clarifications #173

hamishwillee opened this issue Mar 3, 2019 · 0 comments

Comments

@hamishwillee
Copy link
Collaborator

MAV_CMD_SET_MESSAGE_INTERVAL

  • A system can have multiple logical and physical channels - which one does this apply on? (ie it can't be system global).

    • This would make sense as physical channel, because everything on one channel gets the same rates. But the code works by logical channel and there is no way to untangle the associated potential physical channels - so I think we're going to have to use logical channel and know that there is no way to resolve contention.

  • Should the interval persist? If this is up to implementation, should we say so.

  • Any ideas on what to do if multiple systems on channel are asking for different rates?

  • MAV_CMD_GET_MESSAGE_INTERVAL

    • Same question about "which rate"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hamishwillee