Yakut

Yakút is a simple cross-platform command-line interface (CLI) tool for diagnostics and debugging of UAVCAN networks. By virtue of being based on PyUAVCAN, Yakut supports all UAVCAN transports (UDP, serial, CAN, ...) and is compatible with all major features of the protocol. It is designed to be usable with GNU/Linux, Windows, and macOS.

Ask questions and get assistance at forum.uavcan.org.

Installing

First, make sure to have Python installed. Windows users are recommended to grab the official distribution from Windows Store. Yakut requires Python 3.7 or newer.

Install Yakut: pip install yakut

Afterward do endeavor to read the docs: yakut --help

Check for new versions every now and then: pip install --upgrade yakut

Invoking commands

Any option can be supplied either as a command-line argument or as an environment variable named like YAKUT_[subcommand_]option. If both are provided, command-line options take precedence over environment variables. You can use this feature to configure desired defaults by exporting environment variables from the rc-file of your shell (for bash/zsh this is ~/.bashrc/~/.zshrc, for PowerShell see $profile).

Options for the main command shall be specified before the subcommand when invoking Yakut:

yakut --path=/the/path compile path/to/my_namespace --output=destination/directory

In this example, the corresponding environment variables are YAKUT_PATH and YAKUT_COMPILE_OUTPUT.

Any subcommand like yakut compile can be used in an abbreviated form like yakut com as long as the resulting abbreviation is unambiguous.

There is a dedicated --help option for every subcommand.

Compiling DSDL

Suppose we have our custom DSDL namespace that we want to use. First, it needs to be compiled:

yakut compile ~/custom_data_types/sirius_cyber_corp

Some commands require the standard namespace to be available, so let's compile it too, along with the regulated namespace:

yakut compile  ~/public_regulated_data_types/uavcan  ~/public_regulated_data_types/reg

Compilation outputs will be stored in the current working directory, but it can be overridden if needed via --output or YAKUT_COMPILE_OUTPUT. Naturally, Yakut needs to know where the outputs are located to use them; by default it looks in the current directory. You can specify additional search locations using --path orYAKUT_PATH.

A question one is likely to ask here is: Why don't you ship precompiled regulated DSDL together with the tool? Indeed, that would be trivial to do, but we avoid that on purpose to emphasize our commitment to supporting vendor-specific and regulated DSDL at the same level. In the past we used to give regulated namespaces special treatment, which caused our users to acquire misconceptions about the purpose of DSDL. Specifically, there have been forks of the standard namespace extended with vendor-specific types, which is harmful to the ecosystem.

Having to manually compile the regulated namespaces is not an issue because it is just a single command to run. You may opt to keeping compiled namespaces that you use often somewhere in a dedicated directory and put YAKUT_PATH=/your/directory into your shell's rc-file so that you don't have to manually specify the path when invoking Yakut. Similarly, you can configure it to use that directory as the default destination for compiled DSDL:

# bash/zsh on GNU/Linux or macOS
export YAKUT_COMPILE_OUTPUT=~/.yakut
export YAKUT_PATH="$YAKUT_COMPILE_OUTPUT"

# PowerShell on Windows
$env:YAKUT_COMPILE_OUTPUT="$env:APPDATA\Yakut"
$env:YAKUT_PATH="$env:YAKUT_COMPILE_OUTPUT"

So that you say simply yakut compile path/to/my_namespace knowing that the outputs will be always stored to and read from a fixed place unless you override it.

Communicating

Commands that access the network need to know how to do so. There are two ways to configure that: pass registers via environment variables (this is the default), or pass initialization expression via --transport/YAKUT_TRANSPORT (in which case the registers are ignored).

Configuring the transport via UAVCAN registers

UAVCAN registers are named values that contain various configuration parameters of a UAVCAN application/node. They are extensively described in the UAVCAN Specification. When starting a new process, it is possible to pass arbitrary registers via environment variables.

There are certain registers that are looked at by UAVCAN nodes to determine how to connect to the network. Some of them are given below, but the list is not exhaustive. The full description of supported registers is available in the API documentation for pyuavcan.application.make_transport().

If the available registers define more than one transport configuration, a redundant transport will be initialized.

This initialization method requires that the standard DSDL namespace uavcan is compiled.

Configuring the transport via initialization expression

Being specific to this tool, this method is not compatible with the UAVCAN ecosystem at large, but its advantages are that it does not require the standard DSDL namespace uavcan to be compiled beforehand and it allows one to force the tool to disregard the registers if they are irrelevant in the current context.

The transport initialization expression is passed via --transport/YAKUT_TRANSPORT. Here are practical examples (don't forget to add quotes around the expression):

• UDP("127.0.0.1",None) -- UAVCAN/UDP on the local loopback interface; local node anonymous.

• UDP("192.168.0.0",456) -- UAVCAN/UDP on the local network; local node-ID 456, local IP address 192.168.1.200.

• Serial('/dev/ttyUSB0',None) -- UAVCAN/serial over a USB CDC ACM port; local node anonymous.

• Serial('socket://localhost:50905',123) -- UAVCAN/serial tunneled via TCP/IP instead of a real serial port. The local node-ID is 123.

• CAN(can.media.socketcan.SocketCANMedia('vcan1',32),3),CAN(can.media.socketcan.SocketCANMedia('vcan2',64),3) -- UAVCAN/CAN over a doubly-redundant CAN FD bus using a virtual (simulated) SocketCAN interface. The node-ID is 3, and the MTU is 32/64 bytes, respectively.

• Loopback(2222) -- A null-transport for testing with node-ID 2222.

To learn more, read yakut --help. If there is a particular transport you use often, consider configuring it as the default via environment variables as shown earlier.

Next there are practical examples (configuring the transport is left as an exercise to the reader).

Publishing messages

Publishing two messages synchronously twice (four messages total); notice how we specify the subject-ID before the data type name:

export UAVCAN__UDP__IFACE=127.63.0.0
export UAVCAN__NODE__ID=42
yakut pub 33:uavcan.si.unit.angle.Scalar.1.0 'radian: 2.31' uavcan.diagnostic.Record.1.1 'text: "2.31 rad"' -N2

We did not specify the subject-ID for the second subject, so Yakut defaulted to the fixed subject-ID.

Subscribing to subjects

Subscribe to subject 33 of type uavcan.si.unit.angle.Scalar.1.0 to receive messages published by the above command:

$ export UAVCAN__UDP__IFACE=127.63.0.0
$ yakut sub 33:uavcan.si.unit.angle.Scalar.1.0
---
33:
  _metadata_:
    timestamp: {system: 1608987583.298886, monotonic: 788272.540747}
    priority: nominal
    transfer_id: 0
    source_node_id: 42
  radian: 2.309999942779541

---
33:
  _metadata_:
    timestamp: {system: 1608987583.298886, monotonic: 788272.540747}
    priority: nominal
    transfer_id: 1
    source_node_id: 42
  radian: 2.309999942779541

Invoking RPC-services

Given custom data types:

# sirius_cyber_corp.PerformLinearLeastSquaresFit.1.0
PointXY.1.0[<64] points
@extent 1024 * 8
---
float64 slope
float64 y_intercept
@sealed

# sirius_cyber_corp.PointXY.1.0
float16 x
float16 y
@sealed

Suppose that there is node 42 that serves sirius_cyber_corp.PerformLinearLeastSquaresFit.1.0 at service-ID 123:

$ export UAVCAN__UDP__IFACE=127.63.0.0
$ export UAVCAN__NODE__ID=42
$ yakut compile sirius_cyber_corp
$ yakut call 42 123:sirius_cyber_corp.PerformLinearLeastSquaresFit.1.0 'points: [{x: 10, y: 1}, {x: 20, y: 2}]'
---
123:
  slope: 0.1
  y_intercept: 0.0

Updating node software

The file server command can be used to serve files, run a plug-and-play node-ID allocator (some embedded bootloader implementations require that), and automatically send software update requests uavcan.node.ExecuteCommand to nodes whose software is old.

To demonstrate this capability, suppose that the network contains the following nodes:

• nodes 1, 2 named com.example.foo, software 1.0
• nodes 3, 4 named com.example.bar, hardware v4.2, software v3.4
• node 5 named com.example.baz

Software updates are distributed as atomic package files. In case of embedded systems, the package is usually just the firmware image, possibly compressed or amended with some metadata. For the file server this is irrelevant since it never looks inside the files it serves. However, the name is relevant as it shall follow a particular pattern to make the server recognize the file as a software package. The full specification is given in the command help: yakut file-server --help.

Suppose that we have the following packages that we need to deploy:

• v1.1 for nodes com.example.foo with any hardware
• v3.3 for nodes com.example.bar with hardware v4.x
• v3.5 for nodes com.example.bar with hardware v5.6 only
• nothing for com.example.baz

$ ls *.app*                       # List all software packages
com.example.foo-1.1.app.zip       # Any hardware
com.example.bar-4-3.3.app.pkg     # Hardware v4.x
com.example.bar-5.6-3.5.app.bin   # Hardware v5.6 only

The server rescans its root directory whenever a new node is found online, meaning that packages can be added/removed at runtime and the server will pick up the changes on the fly. Launch the server:

$ export UAVCAN__UDP__IFACE=127.63.0.0
$ export UAVCAN__NODE__ID=42
$ yakut file-server --plug-and-play=allocation_table.db --update-software

If there are any nodes online (or if they join the network later), the server will check the version of each by sending uavcan.node.GetInfo, and if a newer package is available locally, it will request the node to install it by sending uavcan.node.ExecuteCommand.

In this specific case, the following will happen:

• Nodes 1 and 2 will be updated to v1.1.
• Nodes 3 and 4 will not be updated because the newer package v3.5 is incompatible with hardware v4.2, and the compatible version v3.3 is too old.
• Node 5 will not be updated because there are no suitable packages.

Add --verbose to see how exactly the decisions are made.

This command can be used to implement automatic network-wide configuration management. Start the server and leave it running. Store all relevant packages into its root directory. When a node is connected or restarted, the server will automatically compare the version of its software against the local files and perform an update if necessary. Therefore, the entire network will be kept up-to-date without manual intervention.