Skip to content

Sequence number handled per message instead of per channel #2759

@Mykyta1995

Description

@Mykyta1995

Hi @julianoes

Sorry for bothering you, but I don’t know who else I could ask. I couldn’t find any information related to this behavior, and I would appreciate your reply.

I’m experimenting with MAVSDK and noticed a difference in message behavior. When I create a Mavsdk object with the same system ID and component ID, it automatically sends Heartbeat and Ping messages. However, the sequence numbers are different: for Heartbeat the sequence number is 6, while for Ping it is 1.

I also found this closed issue: #1499
So, my questions are:
Is this the correct behavior, or is it a bug?

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions