Skip to content

mavlink comp ids do not need to be the same #4

Description

@TaylorDixonHD

you have a conditional in prototype.parseChar that requires the component ids to be the same for the message to be emmited, the point of component ids is to keep track of multiple components talking and infact they should be different rather than the same.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions