|0.2.1||Nov 6, 2021|
|0.2.0||Oct 31, 2021|
|0.1.0||Jul 11, 2021|
#613 in Embedded development
Used in 8 crates (6 directly)
This project implements (most of) UAVCAN v1.0. As the UAVCAN website explains, "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."
This is currently an independent project, not affiliated with the UAVCAN Consortium.
||The main library with all core transport-independent functionality|
||Rust types corresponding to the UAVCAN public regulated data types|
||Compatibility for bxCAN embedded CAN controllers|
||Compatibility for Linux SocketCAN interfaces|
||Experimental UAVCAN/Serial transport|
||Experimental UAVCAN/UDP transport|
||A client library for plug-and-play node ID allocation|
||Access to the software image CRC|
||A tool to calculate and write the CRC of a software image for use with
||A DSDL processor that generates Rust data types and serialization code|
||A procedural macro that generates Rust data types and serialization code from inline and/or external DSDL files|
Other crates (
canadensis_filter_config) are re-exported in various places, so you normally will not need to depend on them directly.
This code is intended to conform to version 1.0-beta of the UAVCAN specification.
Most of the functionality works. Some parts are incomplete:
- There are some tests, but there are probably several bugs in areas that have not been tested.
- The amount of dynamic memory allocation can be reduced, or at least documented better.
- It needs better documentation
- Runs on embedded devices
- Uses dynamic memory allocation, but only when necessary
- Supports UAVCAN/CAN (classic CAN and CAN FD)
- Supports UAVCAN/Serial and UAVCAN/UDP (these transports are not fully specified yet, but the canadensis
implementations were compatible with
pyuavcanwhen they were released)
Licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.