PX4 Dev Call: October 26, 2022

rroche · October 19, 2022, 5:01pm

October 26, 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 : How to customize QGC

Resources

Project Updates

P.1 :

General Discussions

D.1 : Board orientation is hard coded in QGC (Sensor calibration tab)

Have you checked SENS_BOARD_ROT?
The enums are hard-coded, so doesn’t use the metadata from the flight controller
Right now the MAV_SENSOR_ROTATION_ROLL_90_YAW_270 entry is therefore missing.

github.com/mavlink/qgroundcontrol

QGC does not support all sensor orientations

opened 10:43AM - 26 Oct 22 UTC

Jaeyoung-Lim

Report: Bug

## Expected Behavior Board orientation can be configured for all values in http…s://mavlink.io/en/messages/common.html#MAV_SENSOR_ORIENTATION are available. ## Current Behavior The entries in https://mavlink.io/en/messages/common.html#MAV_SENSOR_ORIENTATION have 35 entries, but the board orientations supported by QGC only has 30 entires. ![image](https://user-images.githubusercontent.com/5248102/198005799-0b3df3b5-1e93-4509-827d-5d536d4ae7f5.png) This leaves out the orientation `[MAV_SENSOR_ROTATION_ROLL_90_YAW_270](https://mavlink.io/en/messages/common.html#MAV_SENSOR_ROTATION_ROLL_90_YAW_270)`, which I needed for setting up a tailsitter ## Steps to Reproduce: Please provide an unambiguous set of steps to reproduce the current behavior 1. Connect a autopilot to QGC and start a calibration routine ## System Information - Operating System: [Ubuntu 18.04] - QGC Version: [daily] - QGC build: [daily] - Flight Controller: [Pixhawk4] - Autopilot (with version): PX4 ## Log Files and Screenshots - [QGC Console Logs](https://docs.qgroundcontrol.com/en/Support/Support.html#reporting-bugs) - Autopilot logs when available (post a link). - Screenshots of QGC to help identify the current issue/bug behavior.

D.2: ModalAI PR Review process - Eric

How to get reviews for the PR (need external feedback)

Is there a way to integrate a build server hosted in ModalAI, to get it triggered from the PX4 repo?

Jenkins, Github Actions, Gitlab CI are all possible
Using container and authenticating it from PX4 side is also a possibility

D.3 : SITL Test CI failing

Possible causes:

Something related to the cpu resource starving

Action items:

Need to have a snapshot of what went wrong / evidences of what happened
Maybe putting in top output?
Check if the SITL is hanging, and implement a way to catch that & kill the script early, to not waste bandwidth.

Idea: why don’t we make the SITL test optional / last test before merge? To reduce the bandwidth used.

Maybe we can create a script to run SITL conditionally, depending on which part of the code was modified.

Do we even need to use Gazebo for the MAVSDK test?

We should also use the new Gazebo & DDS communication instead of UDP & SITL gazebo.