RFC 0014 - Events Interface

[bkueng]

MAVLink currently does not provide a mechanism to let one component inform
others about sporadic events or state changes with certain delivery. The most
prominent case is for an autopilot to inform a user via GCS about state changes
(e.g. switching into a failsafe mode). This has traditionally been solved by
sending string text messages that are then displayed directly.
However this has several shortcomings:

• The message could be lost, there is no retransmission
• Translation is not possible (or at least very impractical)
• Limited text length, no URLs
• Not suited for automated analysis, or consumption by other components
• Increased flash size requirements for an autopilot binary

The following document serves as a draft for a generic new events interface:
[updated link]: https://docs.google.com/document/d/1VLdnvjG6r6Cw-_FSo9lcG-Nlk7eGA7DaEHhe-3bP4-Q

Everyone is welcome to comment directly in the document. It serves as the main reference point.

@auturgy @dogmaphobic @DonLakeFlyer @hamishwillee

[hamishwillee]

@bkueng there are some open comments from David Sidrane. Did anyone else have any more feedback to add? What are next steps?

[junwoo091400]

@hamishwillee I gues this can be closed, since it was implemented in MAVLink?

[hamishwillee]

I'm not sure. My thinking would be "no", on the basis that:

• It is still WIP https://mavlink.io/en/services/events.html
• It depends on Component metadata, which is not fully implemented anywhere.
• Shouldn't RFCs be merged when they are complete, not closed?

[junwoo091400]

Shouldn't RFCs be merged when they are complete, not closed?

Oh true haha 😆

[hamishwillee]

FWIW it would be good to merge this, but its a bit like dominos. I want component metadata in first.