Skip to content

20210623 Dev Meeting

Jump to bottom Edit New page
Hamish Willee edited this page Jun 24, 2021 · 13 revisions

Agenda

General:

Notes

  • Next meeting JulianO and HamishW will be on holiday.

  • VTOL Safe Area - RomanB

    • Rally points for VTOLs - with additional information about save areas to land and appropriate exit/entry.
    • Love the concept - better to be able to define safe landing at multiple places rather than the "use mission landing" approach that only works for one destination.
    • Dev call recommends "Option2" new mission type.
      • HamishW - On re-reading I am not sure I agree. It's a rally type, and conceptually seems better to me to keep with other rally types. The rules can just as easily be handled with just a new rally command.
    • Dev call recommends getting more input from other VTOL vendors.
    • AO RomanB to create issue and link this - as area for discussion. Link in MichaelDb (@WickedShell). Share with team/James.
    • AO JamesP attempt to get feedback other VTOL vendors in ArduPilot community.

  • common: specify how to deactivate termination #1649

    • General agreement "termination is irreversible"
    • AO JulianO to see if use of using param1=0 for undoing termination in PX4 can be removed. Then we will update this message to confirm that non-1 values are ignored.

  • Fix up enum generation - reminder mk2

    • HamishW: Fixed up Pymavlink.
    • James: Wont this flow through to all cases.
    • HamishW: Yes. All cases work around the bug, so fixes need to be made. Best if these are made by someone with expertise.
    • AO: James to follow up.

  • HIGH LATENCY

    • General discussion about this PR. No specific conclusion. Will rejoin discussion if needed.

  • HYGROMETER message - measures temp and humidity. Intent is for heat control of airspeed sensor. The command part is via UAVCAN

    • Use case is reporting on temp of heated airspeed sensor. The temp control is already automated so not clear why we need to report this.
    • HamishW - OK with it as a sensor message only
    • AO James is talking to CUAV about this and will report back. (HW - added note about this to PR)

  • TIMESYNC

    • Dev call agreed does not make sense to extend old message as this would force APM do continue to use old hack.
    • We know the message with target sysid/compid will address the known issue, but not whether there are are better ways to do this/other things we should be doing.
    • AO JulianO - close old PR. Open PR for new message with the target address fields. Attempt to get advice from MKabir and others on whether it is best approach.

Did not discuss

Attendees: JulianOes, JamesP, Seb, HamishW, RomanBapst

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