20240508 Dev Meeting

General:

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

Notes

• #2109 GPS_RTCM_DATA and associated ardupilot code needs to allow more than 4 fragments of RTCM data for multi-gnss on F9P
  • FYI, waiting on confirmation not a bug.
  • JamesP - easy to clog the link. Need to make sure tradeoffs are known/mitigated.
• #2110 gps: add status and resilience information
  • Broad support but want to make sure it is generic enough.
  • AO Thomas Frans to implement as much as possible of existing discussion.
• #2107 FUEL_STATUS message proposal
  • HamishW - general interest but no implementer
  • AO JamesP to raise with Tridge as there is a "need"
• #354 development.xml: RADIO_LINK statistics messages - FYI only.
  • JamesP owns. Discussion ongoing.

---

Remainder not really discussed.

• #2063 Add additional support for parachute
  • Just an FYI, still being clarified.
• #2098 Could we have some kind of sub-protocol to handle multi-GCS configurations in a graceful manner?
  • Needs concrete proposal - more like RFC model IMO
• RFC MAV_SYS status
  • AOI hamish to have another ook

JamesP expects to be possibly able to get movement on following in coming months:

• #544 Fix up enum generation
  • ? James passing to PeterB - we need a clear direction for next steps.
  • Legitimate problem, but we have put enough on PeterB this week.
• generate WIP warnings on the use of WIP messages in C code #240 - get it in as "default off WIP test". That is useful for Beat.
  • Fixed up but stalled again.
  • This is exactly what Tridge proposed and he wrote it, just not merged.
• XSD - can we get these merged?
  • mavschema.xsd - max, min, increment on field #811
  • mavschema.xsd: add superseded tag #809 #809
  • XSD Schema - there can be at most 7 params #814
  • #821 XSD: MAV_CMD missionOnly attribute
  • Add altitudeOnly attribute #824 (part of MAV_CMD_DO_GO_AROUND - isAltitude attribute discussion #1994

Attendees: Hamish, JulianO, JamesP (ish), Thomas Frans