20240214 Dev Meeting
Hamish Willee edited this page Feb 14, 2024
·
7 revisions
General:
- Update from relevant previous calls
- Tagged: issues, PR.
-
#2078 COMPONENT_INFORMATION_BASIC - add manufacturer date
- AO to merge (HamishW)
-
#349 Allow individual fences to be enabled and disabled - AndyPiper
- I have issues with the use case. Specifically it is very narrow focused and does not address control over enabling specific airspaces.
- Would like to generally update the description to allow use in commands.
- AO discuss again.
-
#343 development.xml: RADIO_RC_CHANNELS message
- HamishW:
- flexibility makes things harder for the autopilot, while OllieW things it gives more options.
- no one else has strong opinions other than this fills a gap.
- JamesP: make sure last round of OllieW stuff goes in before we merge.
- Iterate as per OllieW way and merge.
- HamishW:
-
- SimonH to propose fix. Done in Mavgen C: Use strncpy instead of memcpy to pack char[n] fields #922
-
#2047 Add support for illuminators
- HamishW - AO to respond that we need test suite and logs. Proof of due diligence.
- Perhaps also an illuminator microservice doc?
-
#2063 Add additional support for parachute
- iterate.
-
#2079 common: add set-camera-lens command
- JamesP No industry standard way to handle this.
- HamishW: Two ways in MAVLink - treat as individual cameras or camera definition.
- Opposed to extending arbitrary parts of the basic API.
JamesP to follow up on these.
-
#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.
Already went in:
- #915 MavSchema: Allow 64-bit enum values to be specified - SimonH - can we get a review from PeterB
Did not look at these:
- #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?
Added after meeting:
-
#2012 Common - Opaque IDs for detecting plan changes
- FYI, this has been documented: https://mavlink.io/en/services/mission.html#detecting-missionplan-changes
Attendees: Hamish, JulianO, JamesP, Simon Hancock (a welcome addition :-)