20200513 Dev Meeting
Hamish Willee edited this page May 13, 2020
·
3 revisions
General:
- Update from relevant previous calls
- Tagged: issues, PR.
- Current meeting time agreed by all to still be good compromise.
- Using Component Information to query autopilot support - JulianOes to update on status - changes to message, commands, don proposal.
- Using COMPONENT_INFORMATION to obtain vehicle metadata #1346
- Protocol-level discovery which mission items / commands are supported by an autopilot #1339
- Julian promised to progress this by next week. Requires reading Don's suggestion for changes to component message.
- HamishW will take over if Julian does not progress by next time.
-
DONE #1375 VFR_HUD: edit airspeed comment to also allow CAS if available instead of IAS
- AI HamishW - Update message to generalise. Silvan just wants to be "allowed" to send something other than IAS. This is what is already done.
-
DONE Added yaw to CMD_DO_SET_HOME #1364
- James says is OK by ardupilot. AI Hamish to Merge.
-
DONE #1377 TAKEOFF - clarify behaviour on VTOL
- Agreed that VTOL should obey this message, as it is considered a "generic takeoff message"
- Some concern that this should be rejected - vehicle should do the "safest thing" which is to take off in MC. Lorenz pointed out that on boot though it should be in MC mode, so if someone wants to then manually put it into FW mode that is their choice.
- AI Hamish: Merge and notify Silvan to put in protections to make sure on boot it is in MC mode.
- DONE CMD_NAV_VTOL_TAKEOFF: Clarify only for VTOL #1379 - VTOL_TAKEOFF should be ignored by non-vtol vehicles. AI hamish to fix up the message to say that.
-
DONE Add illuminator message #1272
- AI Hamish to close with useful message.
- AI Hamish: Follow up with Julian on Frames change.
Attendees: HamishW, JulianO, Lorenz, JamesP, SilvanF