20240424 Dev Meeting

General:

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

Notes

• #2102 common: extend EFI_STATUS with a 'fuel_remaining' field
  • This is a 1:1 map to UAVCAN and it reflects EFI system not fuel tank
  • Battery does wrong thing too, but 2 wrongs don't make a right.
  • Right thing to do is have a general fuel capacity message.
  • AO hamish to propose.
• #2063 Add additional support for parachute
  • Just an FYI, still being clarified.
• #2099 common.xml: deprecate MAV_CMD_SET_PARAMETER
  • Yes, we'll deprecate - very old message with no implementers. But willing to reopen this if needed.
  • AO Hamish to fix up the deprecation date to now and merge
• #2104 Sending thrust and torque commands with MAVLink
  • Tech support - close and suggest they create a PR in PX4
• #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
• #2100 [WIP] common.xml: add new frame MAV_FRAME_GLOBAL_VEHICLERELATIVE_ALT
  • We like it but unless there are implementers, should be closed.
  • AO JamesP to close (DONE)
• #354 development.xml: RADIO_LINK statistics messages - FYI only.
  • JamesP owns. Discussion ongoing.
• Versioning? #2037 Generate .deb file in CI
  • Agreed we can have an auto triggered tag release with some kind of date timestamp.
  • Tag to be added by workflow on time.
  • No semantic meaning other than date assigned to the release. It's basically something to satisfy the .deb requirements.

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

Not addressed/did not look at these:

• Should we make requirement in future for tests a MAVSDK client and server side plugin? (fell out of #2047 Add support for illuminators)
• #2079 common: add set-camera-lens command - see #530 Camera source docs
  • HW update - think can do by allowing source to be set on stream, and published.
  • Need more engagement from Randy on this.
• #894 mavschema - 1E2 for scaled unitless values
• #2062 Proposed addition/clarification of units for EPH, EPV, Azimuth
  • Hamish to create a PR against XSD for scaling. We'll see how it goes. Done in https://github.com/ArduPilot/pymavlink/pull/894.
  • James follow up on the other scaling PR against XSD.
• #2055 development: add setter/getters for torque and thrust setpoints
  • Chase up Silvan and Leonard again?
• 1946 Convrnience function(s?) blindly copy 16bytes, - even when less are provided... resulting in somehow corrupt packets.
  • SimonH to propose fix. Done in Mavgen C: Use strncpy instead of memcpy to pack char[n] fields #922
• mavlink_msg_xxx_decode by mavgen_c does not handle extensions of message properly #684 - pymavlink bug fix\
• Jump commands - can only be used in missions #1871

Waiting on others:

• #2029 common.xml: MISSION_CURRENT progress notification

  • Waiting on Nick to address questions/take up again. But won't be mission specific

• #2048 Re-use param index 3 for Fence Action

  • FYI paused/closed for now

• #2049 No way to get current ROI from vehicle

  • Paused until Nick regains time.

• MAVLink 2.1 a'la tridge

• Add Payload and Autonomy Microservice Support from Marine Dialect #1998

  • As a dialect it can be added, but will need ranges, less generic name than marine, and clear docs to indicate that it is a dialect
  • Seb didn't turn up to discuss. But we quite like aspects of the proposal.
  • AO Hamish to ping. - Done https://github.com/mavlink/mavlink/pull/1998#issuecomment-1601907570

Attendees: Hamish, JulianO, JamesP