Skip to content

20221012 Dev Meeting

Jump to bottom Edit New page
Hamish Willee edited this page Oct 13, 2022 · 14 revisions

General:

Notes

  • MAVLink 2.1 a'la tridge

    • Sounds awesome. Doesn't conflict with other ideas around this.
    • ThomasDb agreed to review and see if he can find holes.
    • JamesP points out the intent was to prototype first. May be some issues to iron out.
    • Lots of other discussions about touch points with web technologies that do not impact the proposal.

  • Extend MAV_CMD_NAV_VTOL_TAKEOFF #1875

  • Winch extended support #1899

    • Hardware unclear - could be a winch with multiple controlable releases, in which case perhaps should be managed by a gripper message. Could be something else.
    • AO Auturgy to follow up with Randy to review.
    • HW - add request for clarification: https://github.com/mavlink/mavlink/pull/1899

  • Airspeed message: update #1900 - last minute comments?

    • Discussion around CAS or IAS being sent.
    • Discussion around whether the active/healthy flag information should be otherwise supplied.
    • Auturgy to think about it a little more and comment.

  • add vendor specs for cubepilot #1901

    • Not happy about this - it's lazy.
    • MAVLink can't stop autopilots accepting this stuff, so we need to be more rigorous about stopping it getting into dialects in the first place.

  • Mission_CHECKSUM - provide update on design as checksum can't work (cannot match if generated on GCS and flight stack in Ardupilot). Last issues is support for streaming the geofence/rally point part.

    • Updated plan 13/10/2022
      • unique ID for part of plan generated as mission/geofence/rally point is loaded. The ID is opaque to the GCS. This will effectively be a checksum, but not useable as one from GCS point of view.
      • UID is returned in the MISSION_ACK (extended with new field). This tells GCS that its mission (or other plan) was uploaded and what the ID is.
      • MISSION_CURRENT is extended with uid field and type field. It is emitted on part of plan changing, and streamed with the UID/type changing in cycle.
      • Less flash used. No additional message. GCS knows the current value.

  • MAV_CMD_BATTERY_RESET move to common #1897

    • Thomas "it works for ardupilot, would probably work for PX4 unchanged". "PX4 work on fuel systems has just started"
    • No need for it to move right now but no objection.
    • Hamish would rather wait and see. Closing because it can't be common unless there is a commitment to implement in PX4.

  • RFC 0018 - Improved Battery Status Reporting #19 - quick update

Attendees: Hamish, ThomasDb, JamesP, Yuri K

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