Skip to content

4.8:32255/32614/ MAVLink leak detection #7593

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
ES-Alexander wants to merge 1 commit into
base: master
Choose a base branch
from
+2 −0
Open

4.8:32255/32614/ MAVLink leak detection #7593

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
2 changes: 2 additions & 0 deletions sub/source/docs/internal-leak-failsafe.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,8 @@ Whether the active level of an analog sensor or the logic level from a digital s

.. note:: Digital leak detectors should be connected to digital input pins. Some flight controllers support that on :ref:`servo channel ports <main-aux-out>`, in which case the relevant channel(s) must be configured as :ref:`common-gpios`.

.. note:: Leak detections can also be triggered from a MAVLink subsystem (matching the autopilot's MAVLink system ID), via the extended form of `SYS_STATUS <https://mavlink.io/en/messages/common.html#SYS_STATUS>`__ messages. This can be useful for "remote" leak detection (e.g. in a separate enclosure to the autopilot), where it may be impractical to run a leak sensor probe to, or if the autopilot does not have enough GPIO pins available for the desired number of probes.

What will happen
================
When the failsafe occurs, the action taken is determined by the value of :ref:`FS_LEAK_ENABLE<FS_LEAK_ENABLE>`:
Expand Down
Loading