Skip to content

20210915 Dev Meeting

Jump to bottom Edit New page
Hamish Willee edited this page Sep 22, 2021 · 9 revisions

Agenda

General:

Notes

  • Common.xml - WIP message review #1669

    • Good progress. Main push done for now - no need to pursue immediately.

  • Version control - cadence, process, notification

    • AO Hamish to create issue with initial proposal.

  • Pl add VIDFPS and VIDFOV to Common Camera Parameters #130 - do we need separate common messages for camera and video? Matej/Julian

    • There are lots of camera implementations. Currently none of them have needed separate values for these kinds of settings for video and camera, so there has been no issue so far.
    • There are cases where separate values would be useful.
    • This would makes it easier for the camera implementer if needed
    • This would be more complicated potentially for the GCS.
    • The "summary" of discussion is that we don't want to add the specific video/still variants to the common set right now.
      • We're there would not be unintended consequences of this - for example that there might need to be even more variants for different modes.
      • Evidence is that what we have now works for a lot of camera.
      • There is nothing to stop you having separate parameters for video/still. This discussion is just whether those are marked common.
      • we would revisit this if someone had a camera and use case where they needed separate values, and was willing to prototype end to end. But we don't want to change this as an abstract exercise.
    • EDITED: HamishW. Not quite ready to give up on this. In discussion.
    • Add https://github.com/mavlink/mavlink/issues/1306#issuecomment-920546037

  • Mission item grouping commands and messages #1687 - Matej / James discuss concerns

  • MAV_CMD_MISSION_START for discussion "can we be more explicit about behaviour"

  • Integrated Camera/Gimbal Systems Documentation #1678 and #1306

    • Julian - ongoing. Nothing to report yet.

  • common: add motor_info message #1695

    • James to add additional feedback.
    • Hamish noted that pushing motor stuff to development.xml while this impacts common due to ESC stuff might be "irritating". James to confirm whether the motor stuff needs to go to dev.

  • common.xml: Set/get local position in FRD, FRU frames #1685 - Hamish

    • Can we progress the RFC.
      • Not clear if this process is "alive". Defer to Lorenz
    • General agreement that rewording common.xml to match the RFC terminology seems OK. AO Hamish to try it.

Not covered

Attendees: JamesP, Seb, HamishW, Julian, Matej, JonasH, AntinasB

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