20220817 Dev Meeting

Agenda

General:

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

Agenda

Notes

• Open Drone ID - Can we remove all WIP on the existing set?

  • Yes, with caveat that OPEN_DRONE_ID_ARM_STATUS vs using MAV_STATE is discussed.
    • The OPEN_DRONE_ID_ARM_STATUS has a reason. This is considered important.
  • AO HamishW to create PR.
  • DONE - common: OpenDroneID messages no longer WIP #1882

• common: extend MISSION_CURRENT #1869

  • Extends mission current to allow this to provide all information possibly needed for mission state - total items, mission FSM state, whether the mission is suspended.
  • Julian updated name to remove "FSM" which isn't helpful.
  • This can be merged after final review - DONE

• Extend MAV_CMD_NAV_VTOL_TAKEOFF #1875

  • Need to confirm that this behavior does not break anything - i.e. ArduPilot assumptions are met.
  • James going to see advice on best person to help. Probably Michael Du Bruel
  • HamishW. INvited Michael here: https://github.com/mavlink/mavlink/pull/1875#issuecomment-1219002936 . PR needs more work.

• common.xml:TIMESYNC docs and extensions #1878

  • Testing some of the discussions that came up in the doc PR TIMESYNC (now paused).
  • Adds target system and component, and documentation on how this is actually used.
  • This does not work for updated systems against non-updated systems. The cost of updating systems to interwork in some way appears to be more than the cost of updating the systems.
  • AO HamishW to update issue and see if we can get further response: DONE: https://github.com/mavlink/mavlink/pull/1878#issuecomment-1219051078

• MISSION_CHECKSUM and MISSION_CHANGED

  • Serve very similar purpose. We should remove one and make sure we do implement the other.
  • Concern about cost of generating checksum : https://github.com/ArduPilot/ardupilot/pull/20834#issuecomment-1217508046
    • PX4 PR for this does it on the fly as mission comes in. Should be able to cope with any size mission that can normally be coped with.
    • ArduPilot is higher cost because mission update is done in stack and might have to be done "all at once" - e.g. if mission updated via FTP.
    • Cant progress this unless we know that ArduPilot can implement it.
  • AO Removal of MISSION_CHANGED agreed: https://github.com/mavlink/mavlink/pull/1879 - DONE
  • AO JamesP to ask PeterB to test cost of Checksum on ArduPilot.

These were not covered:

• Mission item - document values for autocontinue #1868 - Julian OK with this. How about you James. Note, autocontinue is not implemented on ArduPilot.

• minimal: try to make component ID less confusing - a good idea, OK ?

Attendees: Hamish, JulianO, JamesP, Thomas Debrunner