PX4 Dev Call: January 29, 2020

January 29, 2020


  • Status update by component
  • Open section for the community (Please add your agenda items)
    • Anyone can propose topics for discussion

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


Flight Testing

System Architecture

  • Simplification of sensor pipeline -> single flow of data
    • Calibration parameters applied later in sensors module
    • (can also be temperature calibration)
  • Work towards multiple estimators

OS / NuttX



  • See System Architecture above.


  • Fixed preflight checks not
  • @bkueng started nicer architecture for preflight checks


  • No update

Fixed Wing

  • No update



  • Verification of dependencies for avoidance ->
  • MAVROS SITL CI tests are now redundant.
  • questions regarding dropping ROS


  • No update



Open section for the community

  • https://github.com/PX4/Firmware/issues/14053
  • CI: GitHub workflows build times have the same speed but scale even better than the Jenkins runners, and are nicely integrated, and maintained by GitHub, not by us.
  • PX4IO sometimes broken on startup: https://github.com/PX4/Firmware/issues/13892
    • Should we dumb PX4IO down so it’s just a pass-through failsafe device?
    • Do we still need fixedwing manual mixing? Not sure. -> Rather parachute/abort for regulations.
    • Maybe add developer mode with simple pass-through mode.
    • Low latency cross-fire input to FMU.
    • PWM outputs still need to be accessible for VTOL.
  • @LorenzMeier: UAVCAN node: what is required?
    • Does it need direct RC interface or not?
    • Startup of UAVCAN is late in sequence.

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.

I am a beginner in this field but i have a deep interest in learning pixhawk architecture and its development.
beginners faced difficulties in undersatnding how different modules of the flight stack can be modified and can be uploaded on board and other related things. So I would like to request to discuss more about firmware and its working if possible.