Skip to content


Here are 131 public repositories matching this topic...

kjetilkjeka commented Nov 8, 2017

Right now, Message/Request/Response is only implemented if there exists some Type ID. This is correct behavior for standard definitions. For other definitions, type ID can be resolved dynamically and needs to be implemented even though there's no statically defined type ID.

Some check based on if the definition is inside the uavcan namespace or not needs to be implemented.

Improve this page

Add a description, image, and links to the communication-protocol topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the communication-protocol topic, visit your repo's landing page and select "manage topics."

Learn more