20230315 Dev Meeting

General:

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

Agenda

• Add control handoff messages for multiple GCS #1954

  • Agree strongly with the use case
  • The ownership message won't work as is - no one will implement round-robin notification when broadcast will work.
  • Setting priority in the requestor won't work "psychologically"; users will just set max.
  • The operating pilot always needs to be able to take control in a way that can't be superseded
  • Having the payload thing manage handover with different GCS is good - i.e. GCS do not need to be on same system.
  • Where possible use MAV_CMDs - that way you get an ACK of success.

• How indicate/define minimal sets: https://github.com/mavlink/mavlink/pull/1958 - desirables? Profiles?

  • This case doesn't actually make - why force face inwards and not face forward?
  • What we really need is better profiles support. HamishW to propose.
  • Dialects should be able to override messages in common.xml though - probably best short term process.

• Added "shortest way" as an option for yaw direction in MAV_CONDITION_YAW #1962

  • This makes sense, but we need an implementation before we merge. Also understanding of where this is being done, and other things that might break

• Indicate preference for COMMAND_INT #1955 and Positional NAV command - test wording of scaling recommendation #1956

  • The general point here is that we need better ways to indicate where an how things are a) relevant, b) standard. For example, consider MAV_CMD_XXXX. Users need to be able to tell
    • whether it can be used in missions, commands or both?
    • What vehicles can it be used on and what behaviours make sense for those
    • Whether it is standard for that vehicle type in missions and/or commands.
  • Perhaps instrumentation is the answer here, or some form of profile?

• New landing target messages TARGET_ABSOLUTE/RELATIVE #1943

  • AO - merge and get it it in. Ping @rishabsingh3003

• mavlink_msg_xxx_decode by mavgen_c does not handle extensions of message properly #684 - pymavlink bug fix

  • AO JamesP to see if we can get review from PeterB.

• message_definitions: add all_with_development.xml #1924

  • AO: JamesP to talk to PeterB to get movement on https://github.com/ArduPilot/pymavlink/pull/240

• COMPONENT METADATA: translation - AO JamesP to outline concerns and reasonable steps Beat or others might take to address them.

Attendees: Hamish, Konrad, JamesP