20200930 Dev Meeting

Agenda

General:

Command to allow geofence action to be set per-fence - FENCE_ACTION - FYI maybe push back to ArduPilot and define GEOFENCE_ACTION. Do we need thrust control on return.

FYI

BATTERY_STATUS add faults, remove SMART_BATTERY_STATUS #1456 - merged as mode field after much discussion.
New instance xml markup. Good feature - was Don looped in?

Agenda

MAV_CMD_NAV_FENCE_RETURN_POINT - how is it supposed to work?
- MichaelO - predates rally points. Doesn't make much sense now but should not be removed because is used by ArduPilot Chinese users who will never update.
- Lorenz points out that deprecating it without removing at least provides clear direction of the desired alternative.
- DONE: AI HamishW Do deprecation.
Geofence Actions - should these be standardised so GCS can query/set them without having to know flight stack (currently would have to know the params used)
- James P - already is standard set but this is directly assigned to an ArduPilot param so no way to generically set it.
- Proposal is to create a command that can be uploaded in a fence definition, and that allows a GF action per fence. If not defined then fallback to system value.
- STARTED

Not discussed:

MAVlink Governance Policy (discussion doc)
- Generally looks good
- Lorenz main concern is that we need to broaden stakeholder to better involve industry partners, as proxy for end users. Example is gimbal vendors like Gremsy.
- Proposal to devote all next meeting to covering detail of this.
File-based protocols for params, missions, etc - Next steps Lorenz?

Attendees: ? HamishW, JamesP, JulianO, ClaudioM, Michael Oborne, Philip Rowse, JonasV.