From 3be6e56720686dec4b4252011fb82140ee65c32a Mon Sep 17 00:00:00 2001 From: Randy Mackay Date: Wed, 5 Mar 2025 20:30:38 +0900 Subject: [PATCH] Plane: autolanding fix to rangefinder param range --- plane/source/docs/rangefinder-autolanding.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plane/source/docs/rangefinder-autolanding.rst b/plane/source/docs/rangefinder-autolanding.rst index a985442670..c81f08403c 100644 --- a/plane/source/docs/rangefinder-autolanding.rst +++ b/plane/source/docs/rangefinder-autolanding.rst @@ -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 ` 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 ` 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 `) then you can safely choose quite small numbers for :ref:`LAND_FLARE_SEC` and :ref:`LAND_FLARE_ALT`, and flare closer to the ground than with the default values.