20201111 Dev Meeting

Agenda

General:

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

Notes

• Move MAV_CMD_DO_AUTOTUNE_ENABLE to common #1525 - No reason not to do this, but I would like to understand the current message flow.
  • AO Hamish to merge. MichaelO to try find out how ArduPilot knows that autotune is finished.
• generator: mavlink_channel_t with correct length #473
  • AO James to get Tridge to evaluate this (not a job for PeterB)
• Proposal for extending COMMAND_LONG to allow for arbitrary param types #1523 Ollie idea for tagging intended data type.
  • Very interesting! Idea needs more thought. Julian is going to try do that thought over coming weeks. Response to Ollie added here.
• add pseudo oblique function to 206 CAM_TRIGG_DIST - 1508
  • DONE AO Hamish to let Igor know we are happy with this, but need confirmation that implementation is approved or in flight stack before we will merge.
• common: Add 'Inclusion Group' to fence for 'OR' fences #1510
  • James pointed out that this is likely to fill need in future to ease aviation authorities specifying safe flight zones, and interworking them with user flight zones. The approach works well with Introduce image groups to allow for correlating images with surveys #1500
  • Hamish not as certain - aren't authorities more likely to be interested in exclusion zones, which do not need this?
  • AO Hamish, update issue and get Lorenz to review (have asked).
• NAV_CONTROLLER_OUTPUT: add airspeed setpoint field
  • If we add this setpoint, do we also need altitude setpoint
  • Would we be better with a separate message, and if so, what would be in it.
  • FYI only we need to be more consistent in how we refer to setpoint field names. The same concept is referred to as desired, setpoint, target, and other variations. Generally target is probably recommended as "most neutral".
  • What is the intent for this - ie how will it be used.
  • AO Ask Silvan to attend meeting and answer with his thoughts on the above.

Not discussed:

• common: add MAV_CMD to process custom actions on a waypoint #1516
• MAVlink Governance Policy (discussion doc) NOTES from last time
  • Lorenz has being trying to act more in spirit of the doc - tagging James, encouraging more complete solutions etc.
  • Action on Lorenz to clarify wording around generator tooling and industry engagement.
  • General agreement on concept of "experimental" xml (or xml folder) for co-development of proposed standards. Ideally granular so can be picked up by dialects and standard.xml when needed.
  • Action to evaluate current use of WIP in prep for moving to this.
    • AO Julian to verify what WIP is supported in MAVSDK and PX4.
    • AO JamesP to confirm no impact of WIP removal on ArduPilot.
  • Aim is to move forward with intent of governance.
• File-based protocols for params, missions, etc - Next steps Lorenz?
• Specific case - COMMAND_ACK extension fields WIP: https://mavlink.io/en/messages/common.html#COMMAND_ACK

Attendees: HamishW, JamesP, JulianO, Michael Oborne, Philip Rowse. Apologies from Lorenz.