20210818 Dev Meeting

Agenda

General:

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

Notes

• Update docs to note that C# supports mavlink 2 (James)

  • AO hamish to do: Done: https://github.com/mavlink/mavlink-devguide/pull/377

• move HYGROMETER_SENSOR from development.xml to common.xml #1672 - what else do we need?

  • Looks OK but there are some minor typos and we need removal of the WIP
  • HamishW to comment (was going to merge but this injects a CI error).

• Add additional axis to Manual control, support additional buttons. #1674

  • This is a simple extension of the current approach but might not be sufficiently future proof. i.e. at the moment the message is sent direct to the flight controller which then needs to map the buttons to functions. It might be that a better design is that functions are assigned in GCS and that is what gets sent to the flight stack - more efficient on the channel.
  • James taking action to discuss with William and Jakub
  • Hamish to summarise discussion on issue - done: https://github.com/mavlink/mavlink/pull/1674#issuecomment-901478811

• all.xml follow up from Jae - if present

  • Jae misunderstood the purpose of all.xml. He thought it was for use by GCS: that is desirable, but the main purpose is to make it easier to prevent id collisions across dialects.
  • AO hamish to document this - Done in https://github.com/mavlink/mavlink/pull/1676
  • Jae wants to understand best way to migrate dialect into all.xml with clashes, in particular for message that needs to be in the mavlink 1 range. James to send Jae an unused ardupilot range id for that message. Jae to move the rest and create a PR for the dialect.

• represent BASE_MODE field in messages SET_MODE and MAV_CMD_DO_SET_MODE #1673 - what could this break?

  • Assertion that this will not be a problem is not sufficient. Needs testing.
  • AO hamish to respond.

• Common.xml - WIP message review #1669

  • Odroid need to stay where they are for now.
  • Removed Command_ack WIP text.
  • Merge the no-brainers.
  • Wait on Julian for confirmation of gimbal etc.

• common: allow negative temperatures for ESC_INFO message #1663

  • General direction was to split this into ESC and motor messages. ESC message to remove motor specific stuff and merge as WIP.
  • AO Claudio

Not discussed.

• MAV_CMD_PAYLOAD_CONTROL_DEPLOY, MAV_CMD_PAYLOAD_PREPARE_DEPLOY, MAV_CMD_NAV_PAYLOAD_PLACE confirm whether https://github.com/mavlink/mavlink/pull/1648 can go in.

Attendees: JamesP, Seb, HamishW, ClaudioM, JaeLim