# UAVCAN v1.0 and ArduPilot

**URL:** <https://forum.opencyphal.org/t/uavcan-v1-0-and-ardupilot/671>\
**Category:** Development & Maintenance\
**Created:** [November 7, 2019, 4:46am UTC](https://forum.opencyphal.org/t/uavcan-v1-0-and-ardupilot/671 "2019-11-07T04:46:02Z")\
**Posts on this page:** 1\
**Showing post:** 25

<div class="post-metadata">

**Author:** ![tridge](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/tridge/32/119_2.png) [@tridge](https://forum.opencyphal.org/u/tridge)\
**Post date:** [November 15, 2019, 9:04pm UTC](https://forum.opencyphal.org/t/uavcan-v1-0-and-ardupilot/671/25 "2019-11-15T21:04:48Z")

</div>

> [@pavel.kirienko](#):
>
> Please review the changeset derived from this discussion:

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.

---

_[View the full topic](https://forum.opencyphal.org/t/uavcan-v1-0-and-ardupilot/671)._
