PX4 Dev Call: February 12, 2020

Coordination Calls (Archive) PX4 Autopilot Coordination
#1

February 12, 2020

Agenda

  • Status update by component (Core Dev Team)
  • Community Q&A

Join Meeting

Meeting ID: 946 175 205
Join using your mobile/desktop

Call in using your phone, find your local number: https://zoom.us/u/aetSYKbiMF

Component update

Documentation

  • Overall improvements on SITL dependencies @JulianOes

Flight Testing

@Tony3dr

System Architecture

  • Sensors module changes to split tasks @dagar
  • CAN nodes as airframe type using existing drivers @dagar

OS / NuttX

  • PX4 reaching I/O limits. @dagar & @david_s5
  • Discussions on Socket CAN implementation

Comms

  • uOrb changes to improve the mavlink module @dagar
  • Work towards using new uorb sub to save memory and make it faster

Driver

  • No update.

Commander

  • No update.

Navigator

VTOL

  • No update.

Fixed Wing

  • Minor changes planned, and optimizations

Multicopter

  • Position controller refactor (part 6) @MaEtUgR
  • New position mode, sticks are mapped to acceleration (WIP) @MaEtUgR

MAVROS / RTPS / ROS2

  • added library to px4_ros_com to make transforms (frame & orientation) @TSC21

Avoidance

  • low pass filter to the forward-backward direction
  • A* planning fixes


MAVSDK

  • Refactor of mission transfer on-going @JulianOes
  • Moving CI from Travis to Github workflows

Simulation

  • PR from @TSC21 SITL/gazebo allows subscription to multiple distance sensors
  • On-going work on FastRTPS plugin which runs parallel to MAVLink @TSC21
  • Multi-vehicle VTOL support @Jaeyoung-Lim
  • Boat model now in SITL @Jaeyoung-Lim

Estimation

  • Bugfix for regression on master

Community Q&A

  • Remove mixer fro PX4IO (discussion)

Errata and Feedback

Let me know below if I failed to capture anything the right way, and if there are any updates, or you have feedback on the call format.