20210303 Dev Meeting

Agenda

General:

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

Notes

• FENCE_STATUS - what do we need for the geofence "running" protocol?

  • Is used in ArduPlane but not really seen as essential/part of core protocol. Essentially geofence protocol defines what can be uploaded (form of a plan) and there is an assumption that the fence will act according to those instructions, but how it acts is defined by the flight stack.
  • AO hamish to update https://px4.slack.com/archives/C52DXKYLV/p1614729704024500?thread_ts=1614698238.024000&cid=C52DXKYLV

• Discussion: COMPONENT_INFORMATION extension #1588

  • General discussion around UAVCAN design
  • AO to defer to next meeting and get Beat along.

• Component Info

  • Quick overview by hamish of proposed change to protocol
  • Did not cover mavlink hosting of data.

• Support for 2 airspeed sensors

  • Design of message covered.
  • DONE AO hamish to post PR.

• Make static and inline prefixes optional #1563

  • AO update close message.

• Introduce image groups to allow for correlating images with surveys #1500

  • AO post comment about next steps/invite to meeting.

Not covered

• Doc outdated: Camera Protocol #298 - Carry over
• Start cleanup of common.xml (the easy ones?) - Recreate standard by moving common so we get git history?

Attendees: HamishW, JulianO, MertAskin, JamesP, Lorenz