Skip to content

20210203 Dev Meeting

Jump to bottom Edit New page
Hamish Willee edited this page Feb 4, 2021 · 15 revisions

Agenda

General:

Notes

Agenda

  • UAVCAN/MAVLink integration via Component ID

    • Waiting on more discussion within respective development teams. Discuss again next meeting.

  • Component info Hosting of component definition files

    • Requirement is that devices are not bricked/unusable if manufacturer ceases operation. Either devices must be able to function without files, devices must host their own files, or these must be hosted somewhere that is considered reliable.
    • JamesP suggested on Github (in new mavlink sub repo). We consider this "reliable".
    • Lorenz suggested can we have manufacturer first, with github fallback? AO Hamish to ask Beat thoughts on that.
    • Will require some com structure - e.g. and all files should move here.
    • AO Hamish to create repo PR.
    • AO to ask about need for the XZ compression library. Note, Beat says everything is done for PX4 at build time, so this not something in the autopilot.

  • ack waypoints may violate no-fly zone #1566

    • The suggestion is cool but has a problematic edge case - upload of plan from a GCS?
    • Need testing and discussion with GCS to understand the impact.
    • DONE :AO HamishW to ask about testing/options

  • Github Action to create C mavlink lib repos for MAVLink 1 and Mavlink 2.

    • DONE AO JulianO to take care of (transferred from Lorenz)

  • Make static and inline prefixes optional #1563 - do we want to support

    • James to talk to PeterB re way forward here. Probably suggest that they write a Julia implementation.

  • If I define a message with NO field, the generated source file would have mistakes in compile. #1567

    • not a defect.
    • DONE AO HamishW to close

  • Adding external dialects (such as STorM32.xml or OpenHD.xml) - can we sign off?

    • Yes. This looks pretty good and is "as discussed". Agree might not be as welcoming as it could be. Let's get it in and modify if that proves to be a problem.
    • DONE AO HamishW - post this to issue.

  • Doc outdated: Camera Protocol #298 -

  • FTP protocol incompatibilities

    • PX4 and ArduPilot now appear aligned, but this is not testable as FTP UI removed while being updated.
    • DONE AO JulianO to align MAVSDK.

  • common.xml: Do not deprecate MAV_CMD_NAV_FENCE_RETURN_POINT. it is he… #1539

    • James. Please remove deprecation but update description on how/where it should be used.
    • DONE AO HamishW to take care of that.

  • Proposal for extending COMMAND_LONG to allow for arbitrary param types #1523 - can we progress this.

    • Generally we can't see this being done without significant break. We love the thinking through.
    • This should therefore become part of the MAVLink 3 "mix" along with other discussion items (like others, discussed here.)

  • Move call from Zoom to Jitsi

    • AO Hamish To ask Ramon

  • Routing helper function - can we move it along?

    • **DONE(( AO Hamish to add call to action on slack.

Not covered from Agenda:

  • Start cleanup of common.xml (the easy ones?)
    • Recreate standard by moving common so we get git history?

Attendees: HamishW, JamesP, Lorenz, JulianO, MattiasG

Add a custom footer
Add a custom sidebar
Clone this wiki locally