PX4 Maintainers Call: May 16, 2023

:calendar: May 16, 2023

The maintainers meeting is a meeting for the developer team to coordinate on pressing issues and to plan the development of the PX4 Autopilot project, the community is welcome to join and listen, but won’t be able to speak unless specific access is granted ahead of time.

:selfie: Meeting Link

:notebook_with_decorative_cover: Agenda

  • v1.14 Release candidate
  • Open Mic

:memo: Meeting Notes

v1.14 Release Candidate

Daniel: Coming across some issues from users.

  • V6C is locking up after fixed-wing landing - Ryan

    • Safety issue
  • Calibration spewing errors

  • PWM default value issue: https://github.com/PX4/PX4-Autopilot/pull/21513. Related: PWM (ESC) calibration. In the long term we should re-think about how we do calibration, there’s a WIP branch.

Note: When talking with ppl separately, they raise issues.

Action Item: PRs are piling up. Let’s unblock main branch at the end of this week (resetting of 1.14 branch).

Potential regressions:

NuttX update: NuttX with STM32 Backpors by davids5 · Pull Request #21495 · PX4/PX4-Autopilot · GitHub

Parachute plugin not working

Relevant discord thread: Discord

Action Item:

  • Review how the real world parachute trigger works (PWM, etc)
  • Review the SITL implementation

FYI @rroche The docs Parachute | PX4 User Guide should accurately reflect the current hardware implementation of parachute on PX4. In summary, parachutes are automatically triggered by failsafe termination. This will set outputs to their failsafe values and you can configure those values in actuator outputs screen. You can also tell PX4 that it has a connected MAVLink parachute and it will also emit MAV_CMD_DO_PARACHUTE on failsafe.

There is also mechanism for a parachute to report its state, but this appears to mostly be “faked” - you basically get a good heathy mavlink parachute if you are getting appropriate heartbeat.