March 21, 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.
Meeting Link
Agenda
- PX4 v1.14.0 Release board update
- PX4 Documentation & PR sync discussion
Meeting Notes
PX4 v1.14.0
To maintainers: Could you please add the release (1.14) blocking PR/Issues that must be merged into main
before branching out?
- Tailsitter: Fix PR in progress AirspeedSelector, FailureDetector: Tailsitter attitude fixes by sfuhrer · Pull Request #21319 · PX4/PX4-Autopilot · GitHub. This is not a definite fix, but the smaller problem has been around for a while & isn’t trivial to fix.
-
DDS: Documentation needs to be checked through. Alex had it running a week ago: XRCE-DDS (PX4-FastDDS Bridge) | PX4 User Guide
- Jay: In MAVROS we used to have a chosen set of messages, how do we do it with XRCE-DDS?
- Daniel: For now we can keep it simple?
- uORB ‘core’ message set: Having this defined would be nice. Users actually wants to e.g. control motor / commands, instead of any other messages (use case).
- MAVLink: We may get into situation where we re-invent the mavlink again.
- We could also ‘version’ control the set of messages in the future
- Most controls are working well, but the only missing one is ‘Actuator control’ message use, currently in discussion with OSRF to get it into a standard message. Effort to standardize to a standardized ROS message could be done (e.g. Joint control, Motor control: these are generic enough!)
- Goal is to get actuator message into that generic ‘NAV’ message set: synapse_msgs/Actuators.msg at main · CogniPilot/synapse_msgs · GitHub
- Random 100% thrust issue: Random 100% Thrust · Issue #20275 · PX4/PX4-Autopilot · GitHub
- In the past, Alex didn’t encounter this after land detector refactor
- Micro DDS IP PR
TODO
- We need to clarify the tests needed (RC, etc)
- DDS testing from users not so familiar with ROS2 & asking for actual use cases
- Identify use cases of the DDS: Organize another call to discuss this thoroughly (controller interface, offboard control kinda use cases, etc)
PX4 Documentation synchronization discussion
Can we have a more automation on generating documentation?
Daniel: We could have each ‘module’ have a documentation? Being atomically?
Atomic: Means, having the documentation within the source code, so that it is frictionless for having a PR up for a Docs vs Development (as currently).
TODO: Organize meeting with Hamish to discuss about this & what the procedure should be.