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

[Sponsored by Cubepilot] Cube ID via DroneCAN #23113

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

Conversation

julianoes
Copy link
Contributor

Work in progress...

This will add support for Cubepilot's Cube ID modules via DroneCAN, so that users are not limited to the Cube ID serial variant.

Signed-off-by: Julian Oes <julian@oes.ch>
This extracts the function mapping from MAV_TYPE to MAV_ODID_UA_TYPE to
the library, so that it can be re-used later by the remote ID
implementation over DroneCAN.

Signed-off-by: Julian Oes <julian@oes.ch>
More is needed.

Signed-off-by: Julian Oes <julian@oes.ch>
@PetervdPerk-NXP
Copy link
Member

Awesome, you managed to update the libuavcan and dsdl dependencies so that we can generate latest data types?

@julianoes
Copy link
Contributor Author

@PetervdPerk-NXP I just updated it and nothing seemed to break, so I'm not sure I did it right...

@henrykotze
Copy link
Contributor

We definitely need to test it on hardware, since I have updated previously to support newer data types, but there were issues translating the messages between FMU and Cannodes. I specify remember that the Servo Array Command didnt work as expected.

I will see if I can find the Issue or some internal doc which describes the issue.

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

3 participants