PX4 Dev Call: September 14, 2022

rroche · September 7, 2022, 5:00pm

September 14, 2022

Join us

Agenda

Community Announcement
Community Q&A
Project Updates
General Discussions
Weekly Overview
High priority queue
Release

Community Announcement

Community Q&A (No deep technical discussions)

Guideline for asking a Question

Specify what you are trying to achieve
Specify what environment / platform you are using
Prepare a Link or Document to help understand if possible
First, ask the question on the Slack or create a Github Issue!
If you take over 5 minutes for the question, please continue in Slack or a Github Issue.

Q.1 : Underwater drone, using barometer for depth estimate, EKF problem - Markus

There’s a big latency (500ms) between barometer measurement to estimate changes
Moving drone up & down, and checking baro data & ekf height estimate
Mathieu: With acceleration measurement, the estimate should follow quickly
TODO: Will share log.

Q.2 : Hardware ver handling for different pixhawk versions

In rc.sensors, we need to handle different combinations? (SOM + Carrier)
Holybro carrier boards
In theory, putting the fmu onto any carrier boards should work anyways
TODO: Base board versioning discussion to happen

Project Updates

P.1 : Parity Error PR

P.2 : ModalAI VOXL2 support - Parameter duplicate problem

github.com/PX4/PX4-Autopilot

Adding build support for the ModalAI VOXL 2 platform

PX4:main ← modalai:modalai_voxl2_pr_1

opened 04:28PM - 30 Aug 22 UTC

katzfey

+15255 -36863

Please use [PX4 Discuss](http://discuss.px4.io/) or [Slack](http://slack.px4.io/…) to align on pull requests if necessary. You can then open draft pull requests to get early feedback. ## Describe problem solved by this pull request This is the first pull request to add support for the ModalAI VOXL 2 single board computer. ## Describe your solution This is the bare minimum of code to test the build environment for VOXL 2 ## Test data / coverage A simple "Hello World" message output shows that PX4 is running

TODO: Will rebase, and check CI output
Everytime you fly, some parameters change, and the whole hash changes anyways, and it ends up having QGC doing the param sync again, and this is not ideal for low speed data links
There’s volatile metadata that should handle this more gracefully.
There are 2 parameters that’s changing specifically: COM_FLIGHT_UUID, LND_FLT_LOW. These however shouldn’t really be parameter, why are we using it as param?

github.com

PX4/PX4-Autopilot/blob/e115095f705d058162c430620f754fb0155fdb6e/src/modules/commander/commander_params.c#L779-L791


      
          /**
           * Next flight UUID
           *
           * This number is incremented automatically after every flight on
           * disarming in order to remember the next flight UUID.
           * The first flight is 0.
           *
           * @group Commander
           * @category system
           * @volatile
           * @min 0
           */
          PARAM_DEFINE_INT32(COM_FLIGHT_UUID, 0);

General Discussions

D.1 : Pixhawk 6C tests

Losing height estimation after getting shaked

Issue Tracker on Github: Pixhawk 6c - Issue Tracking · Issue #19943 · PX4/PX4-Autopilot · GitHub

D.2 : RC not working

TODO: Test in different boards (V6X, V5X etc.)

Weekly Overview

Github

Recently updated Issues / PRs in PX4-Autopilot Link

Pull Requests
*
Issues
*

Slack

Last Dev-Call

PX4 Dev Call: April 27, 2022

High priority queue

Discussion based on: https://github.com/orgs/PX4/projects/24

Topic		Replies	Views
PX4 Dev Call: July 13, 2022 PX4 Autopilot	0	605	July 6, 2022
PX4 Dev Call: October 05, 2022 PX4 Autopilot	2	828	October 7, 2022
PX4 Dev Call: May 11, 2022 PX4 Autopilot	0	879	May 4, 2022
PX4 Dev Call: July 20, 2022 PX4 Autopilot	0	923	July 13, 2022
PX4 Dev Call: August 24, 2022 PX4 Autopilot	0	661	August 17, 2022