20220803 Dev Meeting

Agenda

General:

Mission item - document values for autocontinue #1868
- in agreement on behaviour of set current and autocontinue - just confusing ourselves.
- concerns about jumps - AO hamish to document:
  - what 0 jumps means
    - Done in https://github.com/mavlink/mavlink/pull/1871
  - note that there are no inherent maximum number of jumps or number of jump items, but there may be autopilot limits.
- concern about no way to programmatically reset a mission except to upload a new one
  - DONE MAV_CMD_DO_SET_MISSION_CURRENT - allow mission resetting #1870 AO Hamish to update MAV_CMD_DO_SET_MISSION_CURRENT proposing reset mission and autocontinue options (or other option if on further thought this isn't good).
- Concern about how systems know the mission state - e.g. when mission is complete, how can a system know the reason it is loitering.
  - AO Julian to propose MISSION_CURRENT update to add number of items, and mission state: running, paused, finished. Not started = paused I presume.
    - IN progress in common: extend MISSION_CURRENT #1869
TIMESYNC
- Sync is required mostly for components so ArduPilot approach including system id in timestamp does not fix this.
- There may be other approaches being used - SYSTEM_TIME, PING.
- AO: HamishW finish these V1 docs and find out what people are doing. IF needed, create V2 using mavlink approach.
Yet another effort towards unified gimbal device messages
- Julian will progress.
Adding additional remote ID message definitions #1865 - OpenID

These are waiting on feedback:

Follow ups:

Attendees: Hamish, JulianO, JamesP,