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

Can't send CAN frames with extended id over mavlink #999

Open
Aleksw3 opened this issue Dec 19, 2024 · 0 comments
Open

Can't send CAN frames with extended id over mavlink #999

Aleksw3 opened this issue Dec 19, 2024 · 0 comments

Comments

@Aleksw3
Copy link

Aleksw3 commented Dec 19, 2024

I am attempting to send data on the can bus using mavlink. My current setup is connected through mav serial.
When using the function can_frame_send, found in the v20 dialect of ardupilotmega like so:

con.mav.can_frame_send(target_system=1, target_component=0, bus=0, len=0x8,id=0x1e0be281, data=b'22223333')

I receive a message with an arbitration of 0x281 on the other side, which seems to correspond with the standard format (11-bits) of can arbitration. As i am working with DroneCan I need to be able to transmit messages using extended arbitration (29-bits) .
The function class MAVLink_can_frame_message seems to serialize the mavlink message correctly, but somewhere after that the upper 18 arbitration gets lost. Is there something in the code blocking me, or is there a setting I need to change somewhere?

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

1 participant