# Hardware/Pixhawk Dev Call: Dec 01, 2020

**URL:** <https://discuss.px4.io/t/hardware-pixhawk-dev-call-dec-01-2020/19753>\
**Category:** Pixhawk\
**Created:** [November 24, 2020, 5:11pm UTC](https://discuss.px4.io/t/hardware-pixhawk-dev-call-dec-01-2020/19753 "2020-11-24T17:11:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rroche](https://discuss.px4.io/user_avatar/discuss.px4.io/rroche/32/17635_2.png) [@rroche](https://discuss.px4.io/u/rroche)\
**Post date:** [November 24, 2020, 5:11pm UTC](https://discuss.px4.io/t/hardware-pixhawk-dev-call-dec-01-2020/19753/1 "2020-11-24T17:11:34Z")

</div>

# Dec 01, 2020

## Call Moderators

- @rroche @JingerZ

## Agenda Items

- FMUv5X - productization update by Holybro @Vincentpoont2
- FMUv6 update by Andrew Smith, Gumstix
- FMUv6X proposal and update by CUAV (Jinger)
- PX4 96boards Mezzanine board (Sahaj)

## Dail In

Direct link to the meeting:

> **[Jitsi Meet](https://meet.jit.si/dronecode-hardware-wg)**
>
> Join a WebRTC video conference powered by the Jitsi Videobridge

## Who’s on the call

- Jinger Zeng (Dronecode)
- Ramon Roche (Dronecode)
- Lorenz Meier (Auterion)
- Daniel Agar (PX4)
- David Sidrane (PX4)
- Sahaj Sarup (Linaro / 96Boards)
- Andrew Smith (Gumstix)
- Alex Klimaj (Ark Electronics)
- Vincent Poon (Holybro)
- Ray Stits (ModalAI)
- Chad Sweet (ModalAI)
- Jacob Christ
- Dugan Yoon
- Andres

## Meeting Minutes

**FMUv6 Update from Gumstix**

New doc for FMUv6 (not v6x) with updated pinout and diagrams for the v6 reference design

**Open Question to the group** : What is missing from the FMUv5X that we can’t get this done properly? (The schematics are just an example of the standard)

**TODO** : Host a working-level meeting to go through FMUv6 & FMUv5 in parallel for all the implicit assumptions. **Who wants to participate?**

> **[DS-01x Pixhawk Autopilot v6 Standard](https://docs.google.com/document/d/1Jc02fKTpBsyEEZjN3EuLxaeMCwfCRNYqLYy8CuCDl5A/edit#heading=h.fj4efant2uu6)**
>
> Table of contents Table of contents	2 Document Revisions	3 Contact and Public...

**96Boards / PX4 Mezzanine implementation**

Their goal is to make a bridge between FMU SOM and 96Boards specification boards, the goal is to have a plug and play compatibility with more powerful companion computers for auxiliary tasks. “Bridging both worlds!”.

**TODO** : Workgroup meeting with 96boards to define a breakout connector to the FMUv6/FMUv5 and PAB specs

> **[Google Docs - create and edit documents online, for free.](https://accounts.google.com/ServiceLogin?service=wise&passive=1209600&continue=https:%2F%2Fdocs.google.com%2Fdocument%2Fd%2F15xcM53dr5ozrxUfe-8H96f6vefeh-cTRazdUbqD76eA%2Fedit?ts%3D5f32cf60&followup=https:%2F%2Fdocs.google.com%2Fdocument%2Fd%2F15xcM53dr5ozrxUfe-8H96f6vefeh-cTRazdUbqD76eA%2Fedit?ts%3D5f32cf60&ltmpl=docs)**

**Pixhawk SIG Governance**

Discussed how we are planning to make the Pixhawk standard open and transparent to the community including:

- Product launch process (how to launch a Pixhawk based product)
- Testing and Verification
- Trademark usage
- Brand enforcement
- Qualification process

> **[Dronecode Foundation - Pixhawk SIG](https://docs.google.com/document/d/1yLt67dnONJJRMJfRODuDLdanwT0ENN5jHDEeK5EkMzE/edit#heading=h.qi838fkoyjne)**
>
> Pixhawk SIG Supported By The Dronecode Foundation Current Product Launch Process Step 1: Join SIG and Declaration of Product Plan If you are a Dronecode Foundation member already, you can declare to join the Pixhawk SIG and get the weekly...

**Holybro FMUv5X**

Working on a product based on FMUv5X, and it should be ready in a couple of weeks, hardware will be available for developers.

**TODO** : Add a comment on the spec regarding the power module connector

CUAV FMUv6x Proposal

> **[Google Docs - create and edit documents online, for free.](https://accounts.google.com/ServiceLogin?service=wise&passive=1209600&continue=https:%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1qj1q4tQTMl2Dm0bN_ujozXHoqfN281GgKIW0WiVtMzg%2Fedit&followup=https:%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1qj1q4tQTMl2Dm0bN_ujozXHoqfN281GgKIW0WiVtMzg%2Fedit&ltmpl=docs)**

* * *

## Errata and Feedback

Let me know below if I failed to capture anything the right way, and if there are any updates, or you have feedback on the call format.