Libcanard

Minimal implementation of the UAVCAN protocol stack in C for resource constrained applications.

Links:

• DISCUSSION GROUP

Usage

If you're not using Git, you can just copy the entire library into your project tree. If you're using Git, it is recommended to add Libcanard to your project as a Git submodule, like this:

git submodule add https://github.com/UAVCAN/libcanard

The entire library is contained in three files:

• canard.c - the only translation unit; add it to your build or compile it into a separate static library;
• canard.h - the API header; include it in your application;
• canard_internals.h - internal definitions of the library; keep this file in the same directory with canard.c.

Add canard.c to your application build, add libcanard directory to the include paths, and you're ready to roll.

Also you may want to use one of the available drivers for various CAN backends that are distributed with Libcanard - check out the drivers/ directory to find out more.

Example for Make:

# Adding the library.
INCLUDE += libcanard
CSRC += libcanard/canard.c

# Adding drivers, unless you want to use your own.
# In this example we're using Linux SocketCAN drivers.
INCLUDE += libcanard/drivers/socketcan
CSRC += libcanard/drivers/socketcan/socketcan.c

There is no dedicated documentation for the library API, because it is simple enough to be self-documenting. Please check out the explanations provided in the comments in the header file to learn the basics. Most importantly, check out the demo application under tests/demo.c. Also use code search to find real life usage examples.

At the moment the library does not provide means to automate (de)serialization of UAVCAN data structures, like other implementations (e.g. libuavcan for C++ or pyuavcan for Python) do. Therefore, data structures need to be parsed and assembled manually. The necessary examples are provided in the demo application.

Library Development

This section is intended only for library developers and contributors.

The library design document can be found in DESIGN.md

Contributors, please follow the Zubax C++ Coding Conventions.

Building and Running Tests

mkdir build && cd build
cmake ../libcanard/tests    # Adjust path if necessary
make
./run_tests

Submitting a Coverity Scan Build

First, get the Coverity build tool. Then build the tests with it:

export PATH=$PATH:<coverity-build-tool-directory>/bin/
mkdir build && cd build
cmake ../libcanard/tests -DCMAKE_BUILD_TYPE=Debug   # Adjust path if necessary
cov-build --dir cov-int make -j8
tar czvf libcanard.tgz cov-int

Then upload the resulting archive to Coverity.