20191002 Dev Meeting
Hamish Willee edited this page Oct 3, 2019
·
3 revisions
General:
- Update from relevant previous calls
- Tagged: issues, PR.
-
MERGED #1239 Update OpenDroneId messages to match version 0.8 of the specification
- AO HamishW agree to merge as WIP but requests additional information be added on expected usage patterns before WIP removed
- Lorenz discussed concerns around authentication being defined end to end, that for practical use range requirement is needed, asked about whether Wifi/Bluetooth can still be used for other purposes while acting as transponder.
- Lorenz/Gabriel/Soren to connect via email.
-
MERGED #1243 MAV_CMD_COMPONENT_ARM_DISARM: Clarify forced arm/disarm
- Confirmed interpretation of requirement and Merged.
- Stefano Alberico outlined new chip for end/end encryption to see where might fit into ecosystem.
- Not particularly a MAVLink discussion (other than being an option for users who need encrypted comms on MAVLink 2)
- Lorenz provided product-positioning guidance; in particular that setup and pairing need to be seamless for end user.
- MAVLink 3 Discussion
- Hamish presented pre-draft of discussion doc. Comments welcome.
Not discussed:
-
Common Flight Modes Microservices
- Action on Lorenz to do first evolution of spec/requirements.
-
#1228 common.xml: add AIS message
- Action: JamesP to do due diligence and confirm these are sane.
- JulianOes Absent did not discuss "MAVLink connection semantics
-
#929 No way to transmit airspeed reference
- JamesP: ArduPilot does not use
NAV_CONTROLLER_OUTPUT
, so will need to investigate how it sends this information in order to surface possible options.
- JamesP: ArduPilot does not use
- #1216 SET_POSITION_HOME: Add frame for local coordinates
- JulianO to discuss microservices proposal.
- #1234 Add messages for power regulation and temperature status reporting
- #1206 ArduPilot downstream changes
See above!
HamishW, JamesP, Søren Friis, LorenzM, Stefano Alberico, JulianOes
JamesP unable to attend