UAVCAN v1.0 and ArduPilot

Fantastic, thanks! The v0/v1 compatibility is a major relief and I appreciate the foundation you are laying for extensions.
I should also mention an idea I have been thinking of implementing at the API level to make MAVLink2 extensions easier to use. Right now it just uses zero-fill when a sender is not aware of an extension and the recipient is. That is very easy at the transport level, but for some data types zero is not a great value. I’m thinking of adding an API that allows the recipient to ask if a specific field was provided. Something like this for C:

bool mavlink_msg_extension_available(const mavlink_message_t *msg, uint8_t field_offset);

used like this:

bool freemem32_available = mavlink_msg_extension_available(msg, offsetof(mavlink_meminfo_t, freemem32));

the basic idea is that the mavlink_message_t does already have the information needed to tell the caller if a particular field came from zero-fill or not, we just don’t have a convenient API for consumers of the extensions at the moment.

I think the same idea could work for extensions in UAVCAN v1.