Skip to content

RFC 0014 - Events Interface #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+20 −0
Open

RFC 0014 - Events Interface #14

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions text/0014-events_interface.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
* Start date: 2019-04-05
* Contributors: Beat Küng <beat-kueng@gmx.net>

# Summary

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:
https://docs.google.com/document/d/18qdDgfML97lItom09MJhngYnFzAm1zFdmlCKG7TaBpg/edit