Skip to content

20220119 Dev Meeting

Julian Oes edited this page Jan 19, 2022 · 5 revisions

Agenda

General:

Notes (by Julian, incomplete, best effort)

  • Update on common flight modes? https://github.com/mavlink/rfcs/pull/17

    • James: Cruise sugggestion is ok, position mode/position hold doesn't make sense for fixedwing.
    • Lorenz: Agrees, position hold for multicopter, cruise for things that move forward. What about loiter.
    • James: Loiter in fixedwing is orbit, Loiter in multicopter holds position, differently from position hold mode.
    • Julian: but loiter is an important mode for fixedwing
    • James: circle mode is an emergency mode without GPS (constant bank)
    • James: we could call it orbit
    • James: mode reporting, in heartbeat makes him nervous.
    • Julian: should be a separate message
    • Lorenz: should set a bit in the custom mode to signal common modes are sent/supported. Custom modes still exist
    • Julian: what about custom modes are still carried, supported for a bit
    • Lorenz: all modes can now also be transmitted with the string value. Subset (common) is for the broader industry that's explicitly listed. Can be used, does not have to.
  • Thomas Stastny question:

    • Can we use NAN instead of 0 for unknown values in https://mavlink.io/en/messages/common.html#FOLLOW_TARGET? How do we deal with this in general?
    • ArduPilot does not use the message.
    • PX4 does. Handling of NAN not clear.
    • MAVSDK actually uses NAN.
    • How do we deal with this in general?
      • We could break the message but that would be incompatible.
      • We could make a new one but that adds craft.
      • We would need some sort of versioning
    • We could also use a GLOBAL_POSITION_INT.
    • Takeaway: we might consider changing it because it is likely not used and won't cause bad effects.
  • Component information

Attendees: LorenzM, JamesP, JulianO, ThomasS, Manash, Alfred

Clone this wiki locally