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

Clarify what needs to happen for MAVLink Routing #109

Open

hamishwillee opened this issue Sep 6, 2018 · 1 comment

Assignees

Collaborator

hamishwillee commented Sep 6, 2018

A few notes to add for routing:

A MAVLink IP-based router does not need to check the CRC because these protocols have their own packet CRC.
Unfortunately CRC_EXTRA prevents you from routing an unknown packet.
The end user (not router) still needs to check the CRC, in order to get CRC_EXTRA and verify that the message is compatible.

@LorenzMeier -From mavlink email group:

Is it possible to disable the CRC_EXTRA check so that routers can parse messages without having to know whether or not they are supported by the end point.
If not, propose we add a compile-time flag to disable CRC checks. OK?

hamishwillee assigned LorenzMeier

Collaborator Author

hamishwillee commented Oct 8, 2018

See also #113

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