UAVCAN is an open lightweight protocol designed for reliable intravehicular communication in aerospace and robotic applications over CAN bus, Ethernet, and other robust transports. It is created to address the challenge of deterministic on-board data exchange between systems and components of next-generation intelligent vehicles: manned and unmanned aircraft, spacecraft, robots, and cars.
The name UAVCAN stands for Uncomplicated Application-level Vehicular Communication And Networking.
A quick introduction can be found in the UAVCAN Guide. Also have a look at the article "UAVCAN: a highly dependable publish-subscribe protocol for real-time intravehicular networking".
UAVCAN is a standard open to everyone, and it will always remain this way. No licensing or approval of any kind is necessary for its implementation, distribution, or use. Voluntary monetary donations are welcomed via Open Collective.
First, read the UAVCAN Guide. To learn the technical implementation details, read the UAVCAN Specification. Familiarize yourself with the regulated DSDL repository. If you have questions or feedback, bring them to the forum.
Pick one of the free open source implementations (MIT licensed) for use in your application:
None of the implementations suit your needs? Write your own! UAVCAN is a very simple protocol; an experienced developer can easily create a custom implementation from scratch to address the unique needs of their application.
The open source tools will help you design, develop, and maintain your UAVCAN-based application:
Please reference UAVCAN in scientific or technical publications.
Join the forum to start a new discussion. Also, feel free to participate in the weekly dev call.
timokroeger opened an issue “Feedback message handler only called 32 times (SocketCAN)” at UAVCAN/pyuavcan