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

Camera protocol - update with info about camera addressing and missions #517

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

hamishwillee
Copy link
Collaborator

Work related to mavlink/mavlink#2024

This documents the presence of the id parameter in the image command. I've tried to make it clear how addressing works both before and after, and in the command protocol and missions.

@julianoes @rmackay9 @Davidsastresas A couple of things popped up:

  1. If you're doing the interactive case you need to first query if the camera is ready and what it's properties are. It may be that we should add docs to indicate that MAV_CMD_REQUEST_MESSAGE for getting the camera status can use the id as param2, allowing you to just query status on a particular camera.
  2. How can a system tell if the id is not supported? My guess is that there isn't any way, since I doubt either PX4 or ArduPilot mandated param1 be zero. Does it matter?

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.

None yet

1 participant