20220720 Dev Meeting
Hamish Willee edited this page Jul 21, 2022
·
6 revisions
General:
- Update from relevant previous calls
- Tagged: issues, PR.
-
Yet another effort towards unified gimbal device messages
- two parts. One part looking for way to do without breaking existing setups.
- Proposal to allow separate RC control of gimbal bypassing gimbal manager. Seems OK to tell gimbal manager that RC control is regained/released so it can "release" its handled. But any kind of collaborative control like nudging needs control to come via manager. Julian to continue discussion with Ollie.
-
Adding additional remote ID message definitions #1865 - OpenID
-
- Theoretical - no mainline flight stack supports this many outputs right?
- Otherwise OK with names.
- AO ask for detail.
-
Add post-landed behavior setting for NAV_LAND command #1867
- Why is this needed - because sometimes you want to land rather than fly to "near landed" before releasing the gripper.
- Why not set the disarm behaviour as a mission specific setting?
- If done as a param becomes non-generic.
- Not sure it makes sense to specify this in this case.
- Why not use autocontinue off and use that as a trigger for not allowing disarming?
- AO JamesP to find out what ArduPilot does in this case.
- AO HamishW to add docs for autocontinue - https://github.com/mavlink/mavlink/pull/1868
Follow ups:
- AO Hamish - Reserve the MAVLink 1 range - Not done yet.
Attendees: Hamish, JulianO, JamesP, Ackshata, Thomas D