20240327 Dev Meeting

General:

Notes

#2098 Could we have some kind of sub-protocol to handle multi-GCS configurations in a graceful manner?
- Julian - have use case of only wanting one GCS to be able to send manual control messages. Not for security but for collaboration.
- Hamish. I prefer commands over messages. The autopilot should mediate
#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.
FYI James not here next meeting.

Updates

#2049 No way to get current ROI from vehicle - Agreed. Waiting on PR
#2092 common.xml: deprecate the _INT frames - Fixed up and merged.
#354 development.xml: RADIO_LINK statistics messages - FYI only.
- JamesP to own
#2091 DO_FENCE_ENABLE when sent as a command - merged following discussion
Versioning? #2037 Generate .deb file in CI
- Hard to see flight stacks taking the versioned version, which reduces the point.
- The version in the HEARTBEAT is a bit meaningless because no one checks it. Also because it is hard to see how useful it is when so many other things are incompatible. Primarily likely to be useful for big picture Pymavlink changes.
- Stalled
#2088 Common: add MAV_CMD_DO_LAND_REJOIN
- Broad acceptance from ArduPilot. PX4 think the use case is narrow, but "might do it this way if we needed to". So its OK but waiting on Pete to merge suggestions

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.

Attendees: Hamish, JulianO, JamesP