PX4 Dev Call: October 30, 2019

October 30th, 2019

Agenda

  • Status update by component
  • Release v1.10
    • Time for another beta? should we cut an RC?
  • Join the discussion on the Pixhawk Hardware Standards Call
    • Currently discussing
      • Payload Standardization
      • BMS Standardization (Smart Battery)
      • Many other topics, including FMUv* and UAVCAN devices.
  • Introducing the Volunteer Team
    • Inbound Messages, Flight Testing Support, Assist Component Owners
  • 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

Documentation

Small usability fix to the parameters list. Booleans are now documented and you can see the default state. See ATT_ACC_COMP.

Flight Testing

Bad weather remains in TJ, fires and very strong winds, unsafe for the team to out to the field some days last week, and this week as well.

Weekly Report

System Architecture

@dagar

OS / NuttX

NuttX/nuttx with SDIO fixes
From last week’s conversation on filesystem read/write issues, this PR updates the NuttX submodule with the upstream fixes.

Comms

MAVLink update from bi-weekly meeting
Microservices was the main focus of the call

Meeting minutes for MAVLink call

Driver

@mcsauder looking into issue #13316

@dagar Added ICM20602

Commander

@JulianOes A corner was discovered in the failsafe state machine

Action: Send PR to release branch (once we figure out what’s going on)

VTOL

@sfuhrer This week we are flight testing the airspeed sensor PR.

Action: More testing by @sfuhrer

@igalloway NXP is working with FliteTest to produce a low-cost VTOL with PX4

Fixed Wing

:point_up: Same airspeed PR as VTOL with testing by @sfuhrer

Multicopter

Refactoring in master
Bug fixes for the release

Track down the PRs and issues

MAVROS / RTPS / ROS2

@TSC21 Currently working on the CI for px4_ros_com in order to add tests to the microRTPS bridge functionality

Avoidance

@jkflying fixes went into master

Release v1.10.0

Battery fixes and Nuttx fixes
Action: make sure those are in the release branch
Action: cut a beta5 once those fixes are in

make sure we check on this issue before release

@mcsauder & @dakejahl when we went from 1.9.2 to master we burned two motors (400Hz PWM)

Open section for the community

Action: @david_s5 sending a PR that enables two-wire ethernet on the K66


Question: @igalloway I have a general question at some point - relating to localization and how this should integrate with GPS positioning. How to transition from one to another localization system.
Answer: @jkflying Estimate offset between one and another, so you can get a smooth handover. You need both overlapping at some point.

Join the discussion on the Pixhawk Hardware Standards Call

Work Group invitations, BMS & Payload

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.

1 Like