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

Extension fields missing from GIMBAL_DEVICE_ATTITUDE_STATUS_DATA #282

Closed
av-stefan opened this issue Sep 20, 2024 · 3 comments
Closed

Extension fields missing from GIMBAL_DEVICE_ATTITUDE_STATUS_DATA #282

av-stefan opened this issue Sep 20, 2024 · 3 comments

Comments

@av-stefan
Copy link

On both 0.12.1 and 0.13.1, I do not get access to the fields gimbal_device_id or camera_device_id which are extension fields, even when using the emit-extensions feature.

@pv42
Copy link
Contributor

pv42 commented Sep 24, 2024

There was a bug in 0.13.x that the feature was not properly set on the mavlink-bindgen crate when using the mavlink crate. This was fixed with #248 and it should work now on master. You will have to use a git dependency for now until it gets released to crates.io.

Unsure why it doesn't work for 0.12.

@pv42
Copy link
Contributor

pv42 commented Sep 24, 2024

Nevermind.
This currently depends on an older version of the MAVLink message definitions that do not have that extension field yet. Therefore it does not get generated.
https://github.com/mavlink/mavlink/blob/d6d86d3f0c90a67c275d6833931f7c712b858dba/message_definitions/v1.0/common.xml#L7013

@av-stefan
Copy link
Author

av-stefan commented Sep 25, 2024

Alright, closing since already fixed then. Thanks for the info

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