20230607 Dev Meeting

General:

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

Notes

• MAV_CMD_DO_GO_AROUND - isAltitude attribute discussion #1994

  • JamesP: If these aren't being used, do we need them at all.
  • HamishW: Yes. I need something to identify different types for tagging.
  • Decision. Minimise churn. Add altitudeOnly. These only apply to param5, 6, 7. Can revisit if needed.

• Add MAV_RESULT_COMMAND_UNSUPPORTED_MAV_FRAME #2001

  • Yes. Good idea. Merge.

• Clarify DO_REPOSITION vs NAV_WAYPOINT #2002

  • Yes, makes sense. Merge.

• Do we need a specific way to indicate failsafe triggered?

  • No. This can be monitored using MAV_STATE in the HEARTBEAT. Failsafe states are indicated by MAV_STATE_CRITICAL and MAV_STATE_EMERGENCY, and possibly FLIGHT_TERMINATION. Most systems also send events and/or STATUSTEXT.
  • AO Hamish to add (failsafe) to docs
  • AO Julian to add to list to implement emitting emergency on PX4.

• Add Payload and Autonomy Microservice Support from Marine Dialect #1998

  • As a dialect it can be added, but will need ranges, less generic name than marine, and clear docs to indicate that it is a dialect
  • To get into the standard we need much further discussion.
  • AO invite them to addend next meeting and discuss.

• Command int long fixes #1992 - docs updated but lots of follow on.

  • #1996 MAV_CMD_VIDEO_START_CAPTURE et al change param5/6 to 0 default - merge
  • #1995 MAV_CMD_FIXED_MAG_CAL_YAW - help clarify frame and location - merge.
  • #1993 MAV_CMD_PAYLOAD_PREPARE_DEPLOY - remove note about MISSION_ITEM - merge

• 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

• Replace validator with xmlschema (XSD1.1 compliant) #816

  • Note, not done.

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

  • AO James to get Peter to look

• 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 - get answer?

• message_definitions: add all_with_development.xml #1924

  • JamesP seeking more suggestions.

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

  • Some progress FYI - Roku (Dan Rose) fixed that bug but is looking at other problems with output.

Attendees: Hamish, JamesP, JulianO