PX4 Dev Call: August 14, 2019

📞 Coordination Calls PX4 Autopilot Coordination
1

Here is the Agenda:

  • Quick pass through component maintainer boards
  • Continuation of 1.10 release discussion

More topics can be added based on the Devcall list on Github or by commenting here.

Click here: Join the Meeting

One tap mobile
+14086380968,946175205# US (San Jose)
+16468769923,946175205# US (New York)

Dial by your location
+1 408 638 0968 US (San Jose)
+1 646 876 9923 US (New York)
+1 669 900 6833 US (San Jose)
Meeting ID: 946 175 205
Find your local number: https://zoom.us/u/ad94Pgv9yQ

2

My notes, please correct or add as needed:

Drivers:

User experience (https://github.com/orgs/PX4/projects/14)

Commander / Safety (https://github.com/orgs/PX4/projects/13)

VTOL (https://github.com/orgs/PX4/projects/12)

  • Airspeed selection module is now merged and logging on VTOL and fixedwing but not used yet.
  • Future work will be non-airspeed mode and multiple airspeed sensors.
  • We need to get transition fixes into release (https://github.com/PX4/Firmware/pull/12630)
  • @sfuhrer: When you switch out of mission it will do a transition given the transition switch on RC which is not always intuitive. Thoughts?

Multicopter (https://github.com/orgs/PX4/projects/11):

  • Discussion whether to bring in 1kHz into release https://github.com/PX4/Firmware/pull/12145
    -> Advantage: shows to a user why 1.10 is better, otherwise there is no incentive for 1.10.
    -> Disadvantage: needs a bit more testing, will push the release out a bit.

Computer Vision ():

  • Integration issues with direction transforms (https://github.com/PX4/ecl/issues/631)
    -> Docs about how to connect via MAVROS would be nice.
    -> FastRTPS for this would be nice in the future. Ongoing work by @TSC21.

Other issues:

Release discussion:

Further testing discussion:

  • state of ntest (one binary vs. multiple binaries with runner)
    -> gtest for modules by @jkflying are easily separable because they inherit different test base class, so they don’t interfere with ntest.
    -> @dagar: we need clear way to display test result in PR/CI (e.g. xunit)

  • MAVSDK tests: @JulianOes needs to talk to @Stifael and go from there.

3

Who’s going to do this? I don’t have knowledge or bandwidth right now, so would be best if someone else did the update and I do a sanity check for “is it understandable”

4

Would be best if @dagar could do it since he came up with the new API and has transitioned over to it in many places recently.

5

Thanks, I added a docs issue and assigned to Daniel. Let’s see if he has time to look at.