20230510 Dev Meeting

General:

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

Notes

• common.xml: Add MAV_RESULT_COMMAND_LONG_ONLY and MAV_RESULT_COMMAND_INT_ONLY to MAV_RESULT #1982

  • Agreed there is no cost or risk to this, with some potential benefit.

• XSD Fun for all

  • 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
  • Range validation - XSD v1.1
    • Yes, worth pursuing

• Gimbal manager messages - remove WIP tagging - #1980

  • Yes, can be removed

• Standard modes:

  • RFC16: Standard Modes: Metadata support/overrides and dynamic modes #23
  • Changes to standard flight modes #1915 - Beat's PR
  • RFC0016-standard-moded - remove unnecessary base_mode info from messages #24
  • Merge it all. Still concerned it is hijack of simple concept, but can't argue against specific needs on case by case basis.

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

  • FYI is pending implementation by AndKe.

• 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

• Need a better way to call python generator - from Pymavlink?

• message_definitions: add all_with_development.xml #1924

  • Aim is to stop WIP being compiled to releases of tools by accident, making it defacto frozen.
  • Suggestion is to warn by default when a WIP command is built into a library, but allow this to be disabled via a flag.
  • This is still blocked.
  • JamesP seeking more suggestions.

• 1978 Wireshark mavlink_2_common.lua:9330: bad argument #1 to 'rshift' (number expected, got nil)

  • Hamish to cross post to pymavlink

Attendees: Hamish, JamesP, JulianO.