Skip to content

Commit

Permalink
Plane: autolanding fix to rangefinder param range
Browse files Browse the repository at this point in the history
  • Loading branch information
rmackay9 authored and Hwurzburg committed Mar 5, 2025
1 parent 94bcc28 commit bf7cbfd
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion plane/source/docs/rangefinder-autolanding.rst
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ Also note that if you have a longer range rangefinder then it is a very
good idea to set the minimum range of the rangerfinder well above zero.
For example, the PulsedLight Lidar has a typical range of over 40
meters, and when it gets false readings it tends to read ranges of less
than 1 meter. And setting :ref:`RNGFND1_MIN <RNGFND1_MIN>` to 150 , if its the first system rangefinder, will discard any rangefinder readings below 1.5 meters, and will
than 1 meter. And setting :ref:`RNGFND1_MIN <RNGFND1_MIN>` to 1.5 , if its the first system rangefinder, will discard any rangefinder readings below 1.5 meters, and will
greatly improve the robustness of the Lidar for landing.

If the autopilot has a good rangefinder (:ref:`such as LIDAR <common-rangefinder-lidarlite>`) then you can safely choose quite small numbers for :ref:`LAND_FLARE_SEC<LAND_FLARE_SEC>` and :ref:`LAND_FLARE_ALT<LAND_FLARE_ALT>`, and flare closer to the ground than with the default values.
Expand Down

0 comments on commit bf7cbfd

Please sign in to comment.