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

Move 20300.CBAT to dronecan section #46

Open
David-OConnor opened this issue Oct 3, 2023 · 1 comment
Open

Move 20300.CBAT to dronecan section #46

David-OConnor opened this issue Oct 3, 2023 · 1 comment

Comments

@David-OConnor
Copy link

Hi! The cuav/equipment/power/20300.CBAT.uavcan power supply data seems more practical than the ones in uavcan/equipment/power. I'm designing a CAN-based power supply, and it's the best match to the data I'd like to output.

Thoughts on moving this to dronecan/equipment/power or similar? It was presumably designed with a specific device in mind, but it seems like a better general option than the ones in uavcan.
@tridge
Copy link
Member

tridge commented Oct 5, 2023

we could move it if we use OVERRIDE_SIGNATURE to prevent a signature change

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
2 participants
@tridge @David-OConnor