-
Updated
Jul 15, 2020 - C
communication-protocol
Here are 110 public repositories matching this topic...
-
Updated
Nov 1, 2020 - C++
-
Updated
Jul 8, 2020 - C++
-
Updated
Sep 4, 2020 - JavaScript
-
Updated
Oct 31, 2020 - C
-
Updated
Oct 30, 2020 - C
-
Updated
May 28, 2020 - Lua
-
Updated
Oct 31, 2020 - TeX
-
Updated
Apr 10, 2019
-
Updated
Mar 5, 2019 - HTML
-
Updated
Oct 29, 2020 - Python
-
Updated
Feb 28, 2019
-
Updated
Apr 25, 2018 - C++
-
Updated
Oct 13, 2020 - C
-
Updated
Jul 21, 2019 - C
-
Updated
Oct 7, 2020 - CMake
-
Updated
Dec 5, 2019 - C++
-
Updated
Oct 30, 2020 - C++
-
Updated
Mar 4, 2018 - Scala
-
Updated
Jul 30, 2019 - LabVIEW
-
Updated
Feb 8, 2020 - Julia
-
Updated
Nov 1, 2020 - C++
-
Updated
May 30, 2020 - C#
Improve this page
Add a description, image, and links to the communication-protocol topic page so that developers can more easily learn about it.
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."
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.