20230426 Dev Meeting
Hamish Willee edited this page Apr 27, 2023
·
3 revisions
General:
- Update from relevant previous calls
- Tagged: issues, PR.
-
6pm new meeting time.
-
RFC16: Standard Modes: Metadata support/overrides and dynamic modes #23
- Argument for:
- Standard mode definitions very broad because they have to cover existing implementations.
- They are considered sufficient for an unknown GCS to be able to provide adequate support.
- This allows an autopilot to provide better information about the particular implementation (within the broad scope of the standard mode).
- This allows alternative implementations of standard modes to be provided at runtime (only one at a time).
- Also happens to allow custom modes to be supported at runtime, and to have metadata.
- Concerns that it makes a simple concept more complicated. This might discourage adoption, or misuse.
- No particular concerns with the implementation (so far)
- Agree worth taking to our communities to discuss - AO JamesP/Beat.
- Argument for:
-
Low Latency MAVLink Messages for VTOL
- They are no longer suggesting own message set but want help.
- AO to HamishW to suggest starter message set.
-
common - un-WIP gimbal messages #1973 - WIP on device
- Julian thinks we should unwip the manager messages based on:
- They are deployed
- initial look at GCS implementation indicates they are suitable
- The GCS implementation DavidSu. looks like it is heading in right direction, but is not sufficiently compatible yet. David and Julian continuing work.
- AO HamishW to add PR to re-wip the manager cases. But not necessarily merge until GCS stuff has progress.
- Julian thinks we should unwip the manager messages based on:
-
component metadata: add translation docs #498
- Merge
-
mavlink_msg_xxx_decode by mavgen_c does not handle extensions of message properly #684 - pymavlink bug fix
- AO JamesP to see if we can get review from PeterB
-
message_definitions: add all_with_development.xml #1924
- Aim is to stop WIP being compiled to releases of tools by accident, making it defacto frozen.
- Suggestion is to warn by default when a WIP command is built into a library, but allow this to be disabled via a flag.
- This is still blocked.
- JamesP seeking more suggestions.
-
- Can't set to use allxml by default as this includes development.xml, and we don't want to suggest that until ^^^ is fixed.
- No choice but to set common.
- AO JulianO to take first stab at docs.
- Should be good to go following reviews, but would like documentation first
-
Added "shortest way" as an option for yaw direction in MAV_CONDITION_YAW #1962
- FYI is pending implementation by AndKe.
Attendees: Hamish, JamesP, JulianO, BeatK, JonasV.