20210414 Dev Meeting

Agenda

General:

Add a constant to MAV_AUTOPILOT for a COEX Pelican charging station #1146 - been around forever.
- Right MAVLink way is to use a MAV_TYPE, for which MAV_TYPE_CHARGING_STATION exists. The reason for approach was problems with QGC, but the solution is to fix QGC.
- Done Action HamishW to close issue and notify.
Common.xml: AIRSPEED message #1602
- It is worth adding a more up to date message than SCALED_PRESSURE and friends
- Make it airspeed (rather than raw) and include information to allow accuracy/error to be calculated. We decided to allow systems to do this in one of two ways - via enum indicating the "type" of sensor, and via an error value in m/s.
- DONE AO HamishW to update message and give people chance to comment.
Add 'invalid' attribute to messages for invalid, unknown, to be not used, etc, fields #1614
- FYI only. Generally seen as a very good thing.
- Lorenz emphasizes need for care in review of PR. Hamish says will get Julian to do final review when detail resolved.
Doc outdated: Camera Protocol #298
- Julian - this impacts MAVSDK. We'd like to do this right way.
- AO Julian to take away and assess whether it is worth using as test case for prototyping microservices implementation.
Command to allow geofence action to be set per-fence #1482
- No longer blocked.
- DONE AO HamishW - move into development.xml

Attendees: HamishW, Lorenz, JulianO, JamesP,