20191113 Dev Meeting

Agenda

General:

• Update from relevant previous calls
• Tagged: issues, PR.

• #1228 common.xml: add AIS message
  • Action: JamesP still hoping to do due diligence and confirm these are sane.
• #929 No way to transmit airspeed reference
  • JamesP: ArduPilot investigated. ArduPilot DO use NAV_CONTROLLER_OUTPUT. We will discuss options again when he is fully present in 2 weeks.
• #1234 Add messages for power regulation and temperature status reporting
  • JulianOes to review in coming weeks. James to test if has any constraints in terms of implementation.
• Common Flight Modes Microservices
  • Action on Lorenz to do first evolution of spec/requirements.
• JulianOes discuss "MAVLink connection semantics
• #1216 SET_POSITION_HOME: Add frame for local coordinates
• Microservices proposal.
  • Independent services can exist for fence, rally, missions. The fact they use the same workflow and sequences is an implementation detail that might change in future. This allows for us to say that if fence protocol is supported, then it is supported end to end. It also allows us to change the subsets of what supported means for each of them independently - e.g. Adding a new fence message should not require update of the mission protocol.
  • There is still a need to support a way of checking options validity. For example consider a system that supports the rally protocol but only supports multicopter. This system would reasonably not support a new type of rally point that is dedicated to FW - e.g. FW-Landing_Rally_Point. We could just reject the mission on upload, but better to have a way to work out that a particular feature set is not supported on startup. Ideas?

Notes

Call 1

AI:

See above!

Attendees

? HamishW, JulianOes, Jonas,