Homepage GitHub

Development & Maintenance

Alternative transport protocols (9)

This post is the result of my limited research into alternative transports conducted over the last two weeks. It is assumed that the reader is familiar with the latest draft of the specification v1.0. (Aug 2019 edit: th…

Weekly dev call ( 2 ) (24)

A periodic conference call among the maintainers and developers of the UAVCAN specification is to take place every Wednesday at 17:00 UTC at https://whereby.com/Zubax. Time zone Time UTC 17:00 Central European…

UAVCAN: a highly dependable publish-subscribe protocol for real-time intravehicular networking (3)

This write-up is loosely based on the materials presented at the PX4 Dev Summit in Zurich on June 20th, 2019 by Pavel Kirienko (Zubax Robotics) and Scott Dixon (Amazon Prime Air). What UAVCAN is? The following diagram i…


Why were the application specific datatypes removed in UAVCAN v1? While the application specific message definitions were removed from the core specification v1 does not prohibit or even disown the concept of application…

Idempotent interfaces and deterministic data loss mitigation (1)
Pyuavcan -> Nunavut migration? (6)
Weekly dev call - Meeting notes ( 2 ) (21)
Proposed New design tenet (2)
On CAN adapters and stateless interfaces (2)
Big-endian vs. little-endian in the context of bit-level encoding (7)
Queue Disciplines and Linux SocketCAN (3)
Libuavcan RX timestamps on S32K (1)
Library-independent code generation (8)
Uavcan file extension (7)
PyUAVCAN design thread (9)
Data type compatibility assurance (7)
Unique-ID for node-ID acquisition (2)
Time abstractions for libuavcan v1 (2)
Two-Factor Authentication (8)
SI namespace design (15)
How libuavcan v1 is implementing on-target testing (1)
The UAVCAN talk at the PX4 Dev Summit, June 20 (3)
Yukon design megathread ( 2 3 4 5 6 ) (118)
GUI Tool – Next Generation ( 2 3 ) (51)
Pydsdlgen is hard to say (13)
[Future] Zero-cost serialization constraint (2)
Rational expressions in DSDL constants (10)
Latest v0 specification (2)
Does v1 allow the same data type to be exchanged over multiple ports? (3)
Max interfaces in the specification (2)