20240522 Dev Meeting

General:

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

Agenda

• #2116 ADSB_VEHICLE.squawk octal code is sent as if decimal
  • James to chase TomP. But code looks like this is correct.
• #2111 Set camera ids on messages that might have flight-stack attached cameras
  • Julian0. Needed on setmode command because current implementations usually require you switch to correct mode before switching to capture in that mode.
  • HamishW: That seems a lot for users and implementers to infer. AO update docs to provide clear instructions.
• #2115 Tagged releases?
  • JulianO not planning this in the short term.
  • AO HamishW Confirm does not have to be semantic.
  • NOTE:
    • We could do a semantic patch release if we wanted instead?
    • 2.3.n instead of a date stamp? Essentially a promise of a cosmetic update without binary breaks
    • I prefer not to because in theory we'd be implying no new additions on each update.
• #2107 FUEL_STATUS message proposal
  • JamesP: Remove battery as type of fuel
  • AO James - get feedback from Tridge
• #2110 gps: add status and integrity information
  • AO James - get feedback from Tridge
• #2063 Add additional support for parachute
  • Discussion "have we had feedback from manufacturers". Appears @potaito has done so.
  • Get follow up review from @potaito.
• #885 Add multiplier value for GPS_STATUS.satellite_azimuth where 255 means 360deg
  • AO James to chase up Peter's opinion.

Updates?

• #354 development.xml: RADIO_LINK statistics messages - FYI only.
  • JamesP owns.
• #2098 Could we have some kind of sub-protocol to handle multi-GCS configurations in a graceful manner?
  • David on this.

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