20230816 Dev Meeting

General:

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

Notes

• #2027 {Sponsored by Intelliterra} Added MAV_CMD_DO_SET_EMERGENCY for manual emergency setting

  • Julian not opposed. Hamish thinks we need better guidance on how it would be used.

• Extending MISSION_ITEM_REACHED with more detailed status #2023

  • Julian - Add to mission_current two uint_16 for initial and final. These indicate progress and can mean time, distance, or turns or whatever. If both zero not used. The first divided by the second can be used as a percentage if both not zero. The meaning depends on the particular mission item and should be documented in each item.
  • AO hamish to update

• Mission feasibility message and command - discord and historical pr

  • JulianO This could be done as events in the same way as PX4 prearm checks (feasibility checks are run regularly and cached. If the feasibility changes then there is an update of all the issues). Reasoning is that this allows for standard and custom feasibility checks and also translation of those texts. This could possibly also be done as a message emitted on feasibility change that had both a standard and a custom enum value field - but then you'd have to re work out all the integration for meanings of fields, translations etc.
  • Comments on PR https://github.com/mavlink/MAVSDK/issues/2103#issuecomment-1680187221

---

Below not covered

• Move enums in description to real enums 1997
  • What do we think? Necessary? Is there a general rule?

Following - action would be for James to follow up with PeterB

• all.xml minus development.xml?

  • Last week proposed replacing add all_with_development.xml #1924 with "all - development.xml".
  • Now proposing generate WIP warnings on the use of WIP messages in C code #240 - get it in as "default off WIP test". That is useful for Beat. And once in is easier to flip this if we can show it is flawed.

• Fix Wireshark dissector and add snapshot tests #817

  • Can we add this to review?
  • AO James to ask Peter.

• XSD - can we get these merged?

  • mavschema.xsd - max, min, increment on field #811
  • mavschema.xsd: add superseded tag #809 #809
  • XSD Schema - there can be at most 7 params #814
  • #821 XSD: MAV_CMD missionOnly attribute
  • Add altitudeOnly attribute #824 (part of MAV_CMD_DO_GO_AROUND - isAltitude attribute discussion #1994

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

Attendees: Hamish, JulianO. JamesP unable to attend.