This is probably caused by the known bug in PyUAVCAN v0:
https://github.com/UAVCAN/pyuavcan/issues/32
We do not have any resources committed to fixing that because v1 is the focus of the current development. Have you considered migrating to v1? Libcanard v1 is already usable:
Libcanard v0.100, implementing UAVCAN/CAN v1, is now available:
Key features:
Full test coverage and static analysis.
Partial compliance with automatically enforceable MISRA C rules (compliance report not available).
Detailed time complexity and memory requirement models for the benefit of real-time high-integrity applications.
Purely reactive API without the need for background servicing.
Support for CAN FD.
Support for redundant transports.
Compatibility with 8/16/32/64-bit platforms.
The…