PX4 Dev Call: March 30, 2022

March 30, 2022

Join us

Agenda

  • Community Q&A
  • Project Updates
  • General Discussions
  • High priority queue
  • Release

Moderation

  • Community Q&A : Maximum 3 - 5 min limit for each question. If the discussion isn’t finished, ask the Questioner to create a Github Issue about it and continue discussion there.
  • Limit discussions to maximum 5 min, then it should be continued in In-Depth discussions.
  • Always consider the perspective of community members who may not have a deep understanding on certain concepts

:loudspeaker: Community Announcement


PX4 Dev Summit 2022 CFP Deadline in 3 weeks!

Timeline:

  • CFP Open: March 18th
  • CFP Closes: April 19th
  • CFP Notifications: Week of May 2nd

Since we are back in person, we are pushing for increased content diversity, and we welcome any of the below:

  • Session Presentation: 30-min
  • Panel Discussions: 30-min
  • Birds of a Feather: 45/60-min
  • Lightning Talk: 5/15-min
  • Workshop: 1.5/2-hours

Apply to the CFP directly on our Website

:people_holding_hands: Community Q&A


:construction_worker_woman: Project Updates


Updates from the team

Follow Target project

  • Trying jerk-limited trajectory controller for the orbit angle control, still reviewing and tidying PR

:thinking: General Discussions


  • @tstastny : The code style is repeatedly under discussion because we seem to have found a not completely consistent way of writing new code but a lot of style rules are not enforced and an inconsistent across the codebase. We came up with a suggestion to employ the Google style with as few exceptions as possible to account for not changing every line and our needs:
    Suggested exceptions:

    • Tabs instead of space to not change every line.
    • Column width because we have wide monitors and don’t want to waste all the space.
    • Function names in lower-case starting camel case funtionName() to be able to distinguish them easily from ClassNames. make format needs to work just like before. There should not be anything hindering further work while transitioning.

    We could use clang-format and clang-tidy to enforce the style, there are also integrations with IDEs like VS code. We should transition gradually and not change everything at once.

  • @junwoo0914 : It’s currently not efficient for developers to navigate QGC. He’s suggesting keyboard hotkeys. There’s further discussion about how the menu could be improved such that the UX for developers but also users require less clicks.

:phone: Things from the last Dev Call

  • Parameter Name limit increasing
    • Update: In discussion with @bkueng it was found that this is hard because the entire parameter system has to be changed at the same time on all sides. We can still do it but MAVLink has to be used differently and the existing parameter system has to be dealt with in some backward compatible way.
  • Flight Mode dynamic
    • Update: Some comments were added to the document. Any further readers, commenters and feedback are appreciated.

:computer: Things from the Slack Channel

:exclamation: High priority queue

Discussion based on board: High-Priority Queue · GitHub

:ear_of_rice: Release

:raised_hands: Feedback


If you have any feedback or corrections please comment on this post!

:arrows_counterclockwise: Component Updates


Updates on each sectors of PX4 System

:small_airplane: VTOL & Fixed Wing

:flying_saucer: Multicopter

:computer: System Architecture

:chestnut: OS / NuttX

:oncoming_automobile: Driver

:crown: Commander

:cactus: Simulation

:2nd_place_medal: MAVROS / DDS / ROS2

:black_joker: UAVCAN

Thanks for organizing this meeting @junwoo0914 :wink:

2 Likes