20221109 Dev Meeting

General:

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

Notes

• Component metadata - frames

  • Doesn't make sense to carry metadata in firmware for ardupilot because the required data is not firmware specific
  • The required UI is "more than just metadata" - on ArduPilot some frames require rebooting to enable hidden parameters as part of the firmware setup. That would require custom coding in QGC irrespetive of the metadata.
  • In summary, while desirable, it isn't possible to create a generic airframe setup UI for the current flight stacks interacting with MAVLink, let alone other "unknown stacks".

• For discussion: changes to standard flight modes #1915

  • Agreed advanced flag as hint to UI
  • Much discussion around having info about indented mode alongside current mode - use is not intuitive. Engineers present agree it is a pragmatic solution to problem.
  • AO Beat to update PR, hamis to update RFC.

• Lat lon field for sim_state should be int32_t #979

  • Not used by PX4.
  • Pros and cons on either solution. Final thinking was that least complicated change is to update the one in common.xml to have two new fiels.
  • AO HamishW to create PR - done in https://github.com/mavlink/mavlink/issues/979

FYI only

• Common should depend on standard and not visa versa #1905 - FYI merged, and also live in PX4.
• Camera Protocol v2 - Remove WIP tracking #1909 - FYI merged.

Did not discuss.

• component metadata dialect ranges - are there alternatives?
• Extend MAV_CMD_NAV_VTOL_TAKEOFF #1875
• Airspeed message: update #1900
• BATTERY_STATUS_V2
  • In development.xml
• General discussion on how to manage change better in wip and development.xml.
  • Last action was AO Hamish to see if https://github.com/Auterion/ras-a-testing-suite can be adjusted to perform some generic testing.

Attendees: Hamish, BeatK, JamesP, JulianO