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

FYI Camera API changes related to ids #433

Open
hamishwillee opened this issue Aug 15, 2024 · 1 comment
Open

FYI Camera API changes related to ids #433

hamishwillee opened this issue Aug 15, 2024 · 1 comment

Comments

@hamishwillee
Copy link

Just FYI we're making some changes to camera APIs to allow addressing of non-MAVLink cameras attached to autopilot component and to allow specific cameras to be targeted in missions.
Docs in progress in mavlink/mavlink-devguide#517 (comment)

The summary is that what we would ideally like is every camera in MAVLink to be a mavlink camera, with a heartbeat and appropriate type. But autopilots don't want to expose their cameras as separate components, so we're allowing them to include an extra camera id (1-6) in CAMERA_INFORMATION and other camera messages that is used only from the autopilot to identify the attached camera.
Camera commands have an id too, which you can use to specify the mavlink component id OR this device id. You can no longer give a MAVLINk camera component id of 1-6.

The main change for an API would be that you also have to query the autopilot for CAMERA_INFORMATION, and store mapping for up to 6 extra cameras associated with the autopilot.

Cheerio

@joaoantoniocardoso
Copy link
Collaborator

Thanks for letting me know!

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

No branches or pull requests

2 participants