20220105 Dev Meeting

Agenda

General:

• Update from relevant previous calls
• Tagged: issues, PR.

Notes

• Hamish away for 19th. Julian/James to make sure meeting either happens or is visibly cancelled.

• RFC 0016 - Mavlink Standard Modes - update to Proposal: Support for common flight modes #1750

  • James, waiting on ArduPilot feedback.
  • (James) It is important that the names and descriptions of standard modes are intuitive, or at least not counter-intuitive.
    • This is the case for the current description of FW POSITION_HOLD. What this does is hold the current track of the vehicle when sticks released: with that name it should loiter.
    • If we want to use one name for both MC and FW we need to change the name so that it is sensible for both cases
    • Perhaps better to keep this mode but have separate modes for FW. This allows explicit commanding in FW mode.
    • Update discussed in https://github.com/mavlink/rfcs/pull/17#issuecomment-1006204197

• What is https://github.com/mavlink/mavlink/tree/master/cmake for - can we delete it? https://github.com/mavlink/mavlink/pull/1760

  • AO Hamish to delete. We can always restore from history if needed.

• MAV_PROTOCOL_CAPABILITY_MISSION_FLOAT - deprecate #1768

  • This can be deprecated (PR merged) but bit cannot be removed.
  • Hamish - revisited. Discussion continues in PR

• Autotuning:

  • now allows axis to be specified.
  • AO Hamish to create bug reports in flight stacks - https://github.com/PX4/PX4-Autopilot/issues/18959 and https://github.com/ArduPilot/ardupilot/issues/19702

• PeterB - external dialects into internal? https://github.com/mavlink/mavlink/pull/1761

  • This would allow Pymavlink to include all.xml dialects (currently broken).
  • Feels inflexible but perhaps short term pragmatic; in particular not clear that the patch would not have worked.
  • General feeling was that we should accept this because it is useful to be able to be able to manage collisions (build all.xml), and the division is only reasonable in the context of the governance model, which has not been formally accepted.

• Extend WINCH_STATUS_FLAG and WINCH_ACTION #1766 - any objections

  • Some discussion. Need to see those changes and discuss with Randy, but aim is to update tomorrow (day after meeting).

Did not cover

• MAV_PROTOCOL_CAPABILITY_PARAM_FLOAT - redefine meaning

  • Did not discuss what this means

• PUNCTUAL WAYPOINTS - any point in a condition_wait_until?

• DISCUSS: MAV_FRAME_BODY_ to MAV_FRAME_MAV_ - better origin indicator than BODY

  • Progress on a Find an existing standard for frames and use that naming/agree convention body aligned
  • AO HamishW ask for thoughts on issue itself. DONE

Attendees: HamishW, JamesP, JulianO, Jake Dahl