20190320 Dev Meeting

Agenda

General:

• Update from 20190220 (relevant previous calls)
• Tagged: issues, PR. A few choice items:

CHECK Status

• @JamesP and @MichaelS (or Lorenz/Thomas) to engage with Local and body frames and add comments. Discuss next week.
• @WickedShell File format discussion - Attempt to re-engage in next two weeks. JamesP Forwarding of unknown messages in C library not supported #1092 - James to raise with Tridge for discussion.

• Upload mission - discuss with GCS vendors what they see as best way to handle lost Drone originating messages
• Added fields for RTL and LAND time estimates #995 - update with message discussed as WIP (Matthias/Alessandro)

• JulianO: Report back on possible System ID allocation approaches and GCS discovery mechanisms/publishing heartbeat when not connected.

• Lorenz/Hamish - What is happening with Rust team (Michal)

• MichaelDb: PR to update STATUSTEXT_LONG with fields to allow longer messages.

HamishW

• Doc Mission partial upload/download
• COMMAND_INT/MISSION_ITEM_INT definition danger spot - MatthiasG
• SET/GET message interval clarifications - persistence, what stream?
• Ways to resolve conflicts in requests from multiple sources - GCS, Developer APIs, etc. Both different telemetry rates and safety critical systems.

Notes

Call 1

• Discussion of message forwarding in C library - Tridge preferred implementation and reasoning at link. Suggested HamishW do the work - very brave!
• Added fields for RTL and LAND time estimates. Appears to have stalled. Action on Hamish to Ping. Hamish said he might push this through himself if no one else does.
• Mission upload robustness - No response on handling from Don, MichaelO or MichaelDB. Hamish to grab the Michaels at ArduPilot dev conference.
• Hamish update on Rust Team Status
  • They are working hard on this. They have a realistic understanding of what is required.
  • They want to know testing requirements - see Common Test Requirements Missing
    • Generally we can't ask more of them than is done by mavgen
    • Would love to see how their code handles the Pymavlink tests
• NOT DONE Status checks:
  • @JamesP and @MichaelS (or Lorenz/Thomas) to engage with Local and body frames and add comments. Discuss next week.
  • @WickedShell File format discussion - Attempt to re-engage in next two weeks.
  • JulianO: Report back on possible System ID allocation approaches and GCS discovery mechanisms/publishing heartbeat when not connected.
    • NOTE, Julian to ask Auterion team for advice, and at least rule out whether there is expertise that can help with this.
  • MichaelDb: PR to update STATUSTEXT_LONG with fields to allow longer messages.
  • None of Hamish discussion areas above discussed (e.g. COMMAND_INT/MISSION_ITEM_INT definition danger spot)

AI:

• DONE (pinged) Hamish: Added fields for RTL and LAND time estimates - Ping owners.
  • Might need to push again.
• Hamish: Grab the Michaels to discuss Mission Upload robustness
• Hamish: AI to share Common Test Requirements Missing discussion.

Attendees

HamishW, JamesP, JulianO, StoneB (silent), Tridge (ish!)