20200205 Dev Meeting
Hamish Willee edited this page Feb 6, 2020
·
6 revisions
General:
- Update from relevant previous calls
- Tagged: issues, PR.
-
Proposal to start using meeting to discuss big-picture problems through to completion if at all possible. First discussions to be on Common Flight Modes, Microservices.
-
JulianOes: New gimbal messages #1174
- Should we have dedicated messages for gimbal even though the info can be accumulated from elsewhere. General feeling was that with newer gimbals time synchronization will be a real issue, and that we can enable a better experience (and extend if needed) by allowing this.
- Result captured in this comment.
-
common.xml: add chunks for statustext #1295
- Better way to do status updates than STATUSTEXT_LONG.
- Merged this and deleted
STATUSTEXT_LONG: Remove STATUSTEXT_LONG (unused)
-
common: Set mission yaw mode command #1297
- Agreed this is good idea.
- Discussion whether should be persistent or last only for duration of mission, or whatever. Agruments:
- If persistent then can easily be implemented by direct translation to parameter
- Mission commands reasonably should persist during mission. Ideally should be "cancellable".
- General agreement to spec with a persistent flag in the second parameter (only mode supported).
- IN PROGRESS - AI HamishW to make it happen.
-
Proposal: Support for optional values in MISSION_ITEM_INT.
- Agreed we should do this.
- AI HamishW to make it happen - Progressing
-
Proposal: Deprecate all non MISSION_*_INT usage with a breaking change - James, you actively opposed or just not all that interested?
- Agreed we should do this.
- AI HamishW to make it happen
-
Common Flight Modes Discussion
- Having common flight modes removes quite a lot of flight stack specific behaviour. In particular it will make it easier for MAVSDK to be compatible with ArduPilot and other flight stacks, by removing quite a lot of parameter-defined behaviour.
- Discussion of "what is common set".
- Lorenz takes view we should all work to define and agree truly common definition and then implement it. API to support non standard variants, and we can in future make these definitions standard too.
- JamesP "let's start with small set" and work from there to prove principle.
-
Attendees: JulianO, HamishW, JonasV, LorenzM, JamesP