20200108 Dev Meeting
Hamish Willee edited this page Jan 9, 2020
·
4 revisions
General:
- Update from relevant previous calls
- Tagged: issues, PR.
-
Proposal: Deprecate all non MISSION_*_INT usage with a breaking change #1285
- JamesP not sure of the value. Hamish to re-read and comment.
-
HamishW: RSSI defn
-
rssi
fields are in device-dependent units/scale which makes hard for GSC to present. - For GCS to usefully display needs to either be predictable, or message needs to provide the scale used. Former puts burden on sender to parse into desired format. Latter, buts burden on GCS to do conversions.
- Dev team not sure that we can improve this without more expertise.
- Requested Don act as stakeholder.
-
-
MAVLinkFTP: Require support of compressed (text) files #1275
- Julian suggested can use .gz format for compressed files.
- HamishW prompted for next steps, which should probably be prototype in QGC.
-
Gimbal interface progress discussions
- Has been submitted to Gremsy for discussion.
- JamesP: Don't deprecate old messages (worried about old messages being deleted early). HamishW suggested what we actually need is not deprecate tag but superseded or obsolete - essentially a tag to indicate the upgrade path without indicating imminent removal.
- JulianO hopes to merge new messages as WIP in coming weeks. Will also do initial protocol docs.
-
#1264 More support for ICE monitoring
- HamishW raised that this is ardupilot message set that may be needed for common.
- Result is that this issue has been closed for now. The messages are being iterated in ArduPilot. If there is interest in having them in common again we will discuss with new stakeholder.
-
- Very brief discussion. James indicated that perhaps a component information file listing and prototcol bit would be sufficient from his side.
- I pointed out that we're talking versions not features. So for protocol bits to be used, people would need to be willing for us to have a protocol bit like "mission_protocol_version_3_supported". That is quite different than how protocol capabilities are done now.
-
Events interface progress
- Still considered desirable but next step (prototyping) keeps getting pushed back.
- Hamish to chase with Beart to get status.
-
Common Flight Modes Microservices
- This has been waiting on Lorenz to do first evolution of spec/requirements.
- James would like to progress this (and other) large open architectural questions.
Discussions not covered:
- Add a constant to MAV_AUTOPILOT for a COEX Pelican charging station #1146
- JulianOes discuss "MAVLink connection semantics
- #1216 SET_POSITION_HOME: Add frame for local coordinates
-
#929 No way to transmit airspeed reference
- Propose to close - see comment.
-
#1234 Add messages for power regulation and temperature status reporting
- FYI, Edwin no longer working on this. Waiting on team member to pick up.
See above!
- HamishW, JulianOes, JonasV, JamesP