Skip to content

20211110 Dev Meeting

Jump to bottom Edit New page
Hamish Willee edited this page Nov 17, 2021 · 14 revisions

Agenda

General:

Notes

  • add actuator test and configuration commands #1738

  • Component information: add actuators #1729

    • Hamish argues this is in line with current practice for components and is of utility for both PX4 and ArduPilot.
    • discussions around file formats and alternatives that are out of scope for this particular case. James/Lorenz to take offline.
    • JamesP OK for this to go in
    • Beat doing a few more minor detail changes - to ping hamish for merge.

  • dev: add new message for component capability #1724

    • Component info lost when we moved to using it as component metadata.
    • Broadly happy with this approach as it a low cost way of adding a heap of capabilities. While microservices protocol might do this, that is likely to take too long to agree.
    • AO Julian to add back component info lost when we moved to metatdata files. Rest of team to review in timely manner.

  • Flight modes - discussion as to whether fields in custom flight mode buffer can be used for standard modes.

    • Requirement is for consistent and simple way to set standard modes for testing and core flight modes. Must not break existing stuff.
    • JamesP and Lorenz to discuss offline and propose.

Pushed to next week

  • WIP tags in enums #1732 - Wip deprecation?
    • My feeling was that might be useful to do this while we haven't got enum nesting working properly (i.e. to allow us to mark everything as WIP for changed APIs).
    • What about dialect-specific use of WIP like OBSTACLE_DISTANCE_3D in ardupilot. Are they useful in this case?
    • Just did it https://github.com/ArduPilot/pymavlink/pull/592 - but WIP should still turn off
  • DISCUSS: MAV_FRAME_BODY_ to MAV_FRAME_MAV_ - better origin indicator than BODY
  • External dialects discussion continued - this is a problem with building pymavlink. The C library appears to build fine BUT that is lucky happenstance. The PR address both issues - makes building external dialects explicit (which while not accompanied by much testing is likely to be safer) and building pymavlink.
    • How do we proceed?
  • Enum IDX bug fixed but not reviewed - nag.
  • Better way to detect packet loss than sequence number (router issues)? Still good for detecting old messages.

Attendees: HamishW

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