# Supporting UAVCAN v1 in PX4 v1.11 **URL:** \ **Category:** Applications & Usage\ **Created:** [October 25, 2019, 5:07pm UTC](https://forum.opencyphal.org/t/supporting-uavcan-v1-in-px4-v1-11/658 "2019-10-25T17:07:08Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![mrpollo](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/mrpollo/32/69_2.png) [@mrpollo](https://forum.opencyphal.org/u/mrpollo)\ **Post date:** [October 26, 2019, 7:28pm UTC](https://forum.opencyphal.org/t/supporting-uavcan-v1-in-px4-v1-11/658/5 "2019-10-26T19:28:29Z")
Hey Philip, thanks for the feedback. I think the UAVCAN community agrees with you; we want to avoid fragmentation. The UAVCAN protocol needs the support of the community to prevent this. The goals and justification behind v1 are mainly motivated by the demanding needs of the ecosystem, and the current UAVCAN implementing vendors. Pavel and Scott made an excellent summary here (Oct. 2018). > [@Stockholm Summit recap](https://forum.opencyphal.org/t/stockholm-summit-recap/170): > > This post is a brief recap of the major design decisions that were made during the Stockholm Summit (Oct 2nd-3rd, 2018) and during the preceding discussions on Github. The objective of the summit was to discuss the main goals related to the transition from the current pre-release version of the specification (termed “UAVCAN v0”) to the first major stable release (termed “UAVCAN v1.0”). The experience accumulated in the three years since the release of v0 showed that certain major breaking change… Pavel has a follow-up post (Jul 2nd) with a better context for the move and covers the benefits in full. > [@UAVCAN: a highly dependable publish-subscribe protocol for real-time intravehicular networking](https://forum.opencyphal.org/t/uavcan-a-highly-dependable-publish-subscribe-protocol-for-real-time-intravehicular-networking/557): > > This write-up is loosely based on the materials presented at the [PX4 Dev Summit in Zurich on June 20th, 2019](https://px4developersummit.sched.com/event/QWAr/uavcan-a-highly-dependable-publish-subscribe-protocol-for-hard-real-time-intravehicular-networking) by Pavel Kirienko (Zubax Robotics) and Scott Dixon (Amazon Prime Air). What UAVCAN is? The following diagram is designed to aid one’s understanding of the place of UAVCAN among the other communication protocols used in relevant industries. We define a two-dimensional space where one dimension represents the effort required to obtain a verified and validated deployment; and the other dime… It’s been a long road to standardize behind v1, and there’s still lots to do. The team has a plan forward and would benefit from your support as an implementing vendor. I think we ( **the UAVCAN team** ) understand your concerns, and we are willing to discuss how this move affects your hardware and, most importantly, how it benefits your customers. Let’s work together. * * * **UAVCAN v1 FAQ by Scott Dixon** > [@UAVCAN V1 FAQ s](https://forum.opencyphal.org/t/uavcan-v1-faq-s/479): > > 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 specific messages. The messages in v0 were designed with px4 systems in mind and we are more than willing to work with that community to define a regulated, public set of datatypes that could be similar to the v0 definitions (if that is the outcome of the design process). When … --- _[View the full topic](https://forum.opencyphal.org/t/supporting-uavcan-v1-in-px4-v1-11/658)._