Files
PX4-Autopilot/docs/en/sensor/rangefinders.md
T
jiakun 52cf5eebe1 feat(tfmini): add TFMINI Plus variant and correct TFMINI FoV (#29575)
The 2.3 degree FoV published for the TFMINI/TFMINI-S dates back to
#24700 without a documented source and does not match the Benewake
datasheet, which specifies 2 degrees. Publish the datasheet value so
collision prevention and MAVLink consumers see an honest envelope.

Add the TFMINI Plus as variant 4. It speaks the same protocol but has
a 3.6 degree FoV and 0.1 m minimum range per the datasheet. Selecting
the TFMINI variant for a Plus made PX4 discard all readings below
0.4 m (signal_quality forced to 0), starving EKF2 of range aiding in
close-range use.

Update the PX4 docs so the model table, reported ranges and
out-of-range behaviour distinguish the two models.

Bench-verified on px4_fmu-v6x with a TFMINI Plus: variant 1 reports
h_fov 0.0349 rad and stamps quality 0 below 0.4 m; variant 4 reports
h_fov 0.0628 rad, keeps quality -1 from 0.11 to 0.30 m and stamps
quality 0 at 0.05 m.

Fixes #29460
Assisted-by: GLM:glm-5.3-flash

Signed-off-by: jiakun <53556221+ddwolf87@users.noreply.github.com>
2026-11-05 12:25:26 +11:00

20 KiB
Raw Blame History

Distance Sensors (Rangefinders)

Distance sensors provide distance measurement that can be used for terrain following, terrain holding (i.e. precision hovering for photography), improved landing behaviour (conditional range aid), warning of regulatory height limits, collision prevention, etc.

This section lists the distance sensors supported by PX4 (linked to more detailed documentation), and provides information about the generic configuration required for all rangefinders, testing, and simulation with Gazebo or Gazebo-Classic. More detailed setup and configuration information is provided in the topics linked below (and sidebar).

LIDAR-Lite v3LightWare SF11/C LidarARK Flow

Supported Rangefinders

::: tip This is a subset of the rangefinders that can be used with PX4. Modules: Distance Sensors lists PX4 drivers for other non-CAN rangefinders. There may also be other DroneCAN rangefinders than those listed here. :::

Rangefinder Technology Range (min – max) Connections NDAA Notes
Ainstein US-D1 Standard Radar Altimeter Microwave radar 0.5 m – 50 m UART ✔️ All-weather, works over water
ARK DIST SR ToF (850 nm IR) 8 cm to ~30 m DroneCAN, UART ✔️
ARK DIST MR ToF (IR) 8 cm to ~50 m DroneCAN, UART ✔️
Benewake TFmini Plus ToF (IR LED) 0.1 m – 12 m UART ~ PX4 minimum 0.1 m
Benewake TFmini-S ToF (IR laser) 0.1 m – 12 m UART ~ PX4 minimum 0.4 m
Garmin LIDAR-Lite v3 ToF (IR laser) up to 40 m I2C, PWM ~ PX4 caps range to 35 m or less
Holybro ST VL53L1X Lidar ToF (IR) up to ~4 m I2C ~
LeddarOne ToF (IR) 1 cm – 40 m UART ~
LightWare SF11/C ToF (IR laser) up to ~120 m UART, I2C ~
LightWare LW20/C ToF (IR laser) up to ~100 m I2C ~ Waterproof (IP67) + servo
LightWare SF45/B ToF (IR laser) ~50 m UART ~ Rotary lidar (collision prevention)
MaxBotix I2CXL-MaxSonar-EZ Ultrasonic I2C ~
RaccoonLab Cyphal & DroneCAN µRANGEFINDER ToF (IR) ~0.1 m – ~8 m DroneCAN, Cyphal ~
Sony AS-DT1 ToF up to 40 m UART ~ Multipoint distance sensor
LightWare SF02 (disc.) ToF (IR laser) ~50 m UART ~ Discontinued
LightWare SF10/A (disc.) ToF (IR laser) ~25 m UART, I2C ~ Discontinued
LightWare SF10/B (disc.) ToF (IR laser) ~50 m UART, I2C ~ Discontinued
LightWare SF10/C (disc.) ToF (IR laser) ~100 m UART, I2C ~ Discontinued
Lanbao PSK-CM8JL65-CC5 (disc.) ToF (IR) 0.17 m – 8 m UART ✖️ Discontinued
Smartmicro Drone Altimeter Microwave radar 1 m to 175 m DroneCAN ~
TeraRanger Evo 60m (disc.) ToF (IR) 0.5 m – 60 m I2C ~ Discontinued
TeraRanger Evo 600Hz (disc.) ToF (IR) 0.75 m – 8 m I2C ~ Discontinued
TeraRanger Evo 3m (disc.) ToF (IR) 0.1 m – 3 m I2C ~ Discontinued
TeraRanger One (disc.) ToF (IR) 0.2 m – 14 m I2C ~ Discontinued

These adaptors allows you to connect a non-CAN rangefinder via the CAN interface. Note that the range depends on the connected rangefinder

Adaptor Connections NDAA
Avionics Anonymous UAVCAN Laser Altimeter Interface DroneCAN ~
RaccoonLab Cyphal & DroneCAN Rangefinder Adapter DroneCAN, Cyphal ~

Note that some Optical Flow sensors also include a rangefinder, such as ARK Flow and ARK Flow MR.

ARK DIST SR & ARK DIST MR

ARK DIST SR and ARK DIST MR are open-source Time-of-Flight (ToF) rangefinder modules, which are capable of measuring distances from 8cm to 30m and from 8cm to 50m, respectively.

The sensors support DroneCAN, run PX4 DroneCAN Firmware, and are packed into a tiny form factor. They can be connected to a flight controller via its CAN1 port, allowing additional sensors to connected through the CAN2 port.

Holybro ST VL53L1X Lidar

The VL53L1X is a state-of-the-art, Time-of-Flight (ToF), laser-ranging sensor, enhancing the ST FlightSense™ product family. It is the fastest miniature ToF sensor on the market with accurate ranging up to 4 m and fast ranging frequency up to 50 Hz.

It comes with a JST GHR 4 pin connector that is compatible with the I2C port on Pixhawk 4, Pixhawk 5X, and other flight controllers that follow the Pixhawk Connector Standard.

Garmin LIDAR-Lite

The Garmin LIDAR-Lite v3 is a compact laser time-of-flight rangefinder with a range of up to 40 m (PX4 caps this to 35 m or less). It can be connected to either I2C or PWM ports.

MaxBotix I2CXL-MaxSonar-EZ

The MaxBotix I2CXL-MaxSonar-EZ range has a number of relatively short-ranged sonar based rangefinders that are suitable for assisted takeoff/landing and collision avoidance. These can be connected using an I2C port.

The rangefinders are enabled using the parameter SENS_EN_MB12XX.

Lightware LIDARs

Lightware SFxx Lidar provide a broad range of lightweight “laser altimeters” that are suitable for many drone applications.

PX4 supports: SF11/c and SF/LW20. PX4 can also be used with the following discontinued models: SF02, SF10/a, SF10/b, SF10/c.

Others may be supported via the RaccoonLab Cyphal and DroneCAN Rangefinder Adapter described below.

PX4 also supports the LightWare LiDAR SF45 Rotating Lidar for collision prevention applications.

Sony AS-DT1

Sony AS-DT1 is a multipoint distance sensor that connects to PX4 over a UART/serial port. PX4 configures the sensor baud rate and measurement output from the driver.

TeraRanger Rangefinders

Terabee TeraRanger sensors are small, lightweight rangefinders based on infrared Time-of-Flight (ToF) technology, with maximum ranges from 3 m to 60 m (depending on the model).

PX4 supports the following models connected via the I2C bus: TeraRanger Evo 60m, TeraRanger Evo 600Hz, TeraRanger Evo 3m and TeraRanger One.

Ainstein US-D1 Standard Radar Altimeter

The Ainstein US-D1 Standard Radar Altimeter is a compact microwave radar rangefinder with a range of 0.5 m to 50 m and a 100 Hz update rate. It can operate effectively in all weather conditions and over all terrain types (including water). It must be connected to a UART/serial bus.

LeddarOne

LeddarOne is small Lidar module with a narrow, yet diffuse beam that offers excellent overall detection range and performance, in a robust, reliable, cost-effective package. It has a sensing range from 1cm to 40m and needs to be connected to a UART/serial bus.

Benewake TFmini LiDAR

The Benewake TFmini LiDAR rangefinders (TFmini-S and TFmini Plus) have a range of 0.1–12 m and connect to a serial port (UART).

PSK-CM8JL65-CC5

The Lanbao PSK-CM8JL65-CC5 ToF Infrared Distance Measuring Sensor is a very small (38 mm x 18mm x 7mm, <10g) IR distance sensor with a 0.17m-8m range and millimeter resolution. It must be connected to a UART/serial bus.

Smartmicro Drone Altimeter

The Smartmicro Drone Altimeter is a DroneCAN radar-based altimeter with a sensing range of 1m to 175m. It is designed for use in GNSS-denied environments.

Avionics Anonymous UAVCAN Laser Altimeter Interface

The Avionics Anonymous UAVCAN Laser Altimeter Interface allows several common rangefinders (e.g. Lightware SF11/c, SF30/D, etc) to be connected to the CAN bus via DroneCAN, a more robust interface than I2C.

RaccoonLab Cyphal and DroneCAN Rangefinder Adapter

The RaccoonLab Cyphal and DroneCAN Rangefinder Adapter allows several common rangefinders to be connected to the CAN bus via Cyphal or DroneCAN, providing a more robust interface than I2C or UART. This adapter efficiently reads measurements via I2C or UART and publishes range data in meters, making it a versatile solution for UAVs, robotics, and technical documentation applications.

Supported rangefinders include:

  • LightWare LW20/C
  • TF-Luna
  • Garmin Lite V3
  • VL53L1CB

RaccoonLab Cyphal and DroneCAN µRANGEFINDER

RaccoonLab µRANGEFINDER is designed to measure distance and publish it via Cyphal/DroneCAN protocols. It can be used to estimate precision landing or object avoidance.

Features:

Configuration/Setup

Rangefinders are usually connected to either a serial (PWM) or I2C port (depending on the device driver), and are enabled on the port by setting a particular parameter.

The hardware and software setup that is specific to each distance sensor is covered in their individual topics.

The generic configuration that is common to all distance sensors, covering both the physical setup and usage, is given below.

Generic Configuration

The common rangefinder configuration is specified using EKF2_RNG_* parameters. These include (non exhaustively):

  • EKF2_RNG_POS_X, EKF2_RNG_POS_Y, EKF2_RNG_POS_Z - offset of the rangefinder from the vehicle centre of gravity in X, Y, Z directions.
  • EKF2_RNG_PITCH - A value of 0 degrees (default) corresponds to the range finder being exactly aligned with the vehicle vertical axis (i.e. straight down), while 90 degrees indicates that the range finder is pointing forward. Simple trigonometry is used to calculate the distance to ground if a non-zero pitch is used.
  • EKF2_RNG_DELAY - approximate delay of data reaching the estimator from the sensor.
  • EKF2_RNG_SFE - Range finder range dependent noise scaler.
  • EKF2_RNG_NOISE - Measurement noise for range finder fusion

Health Reporting

PX4 reports the rangefinder status to ground stations in the SYS_STATUS message, using the MAV_SYS_STATUS_SENSOR_LASER_POSITION bit (this bit is used for all distance sensor types, not just lasers):

  • onboard_control_sensors_present: set once any distance sensor has published data.
  • onboard_control_sensors_health: cleared if a required distance sensor is missing or stops providing valid data (no update for more than 1 second).

The required distance sensors are the first SYS_HAS_NUM_DIST sensors. For example, with SYS_HAS_NUM_DIST set to 2 and three sensors connected, only the first two affect the health bit. A required sensor that fails also blocks arming.

WARNING : SYS_HAS_NUM_DIST is 0 by default, which means no distance sensor is required. The health bit is then always reported as healthy, even if a rangefinder stops working. Set SYS_HAS_NUM_DIST if you want rangefinder failures to be reported.

You can check these bits in the SYS_STATUS message using the QGroundControl MAVLink Inspector.

Testing

The easiest way to test the rangefinder is to vary the range and compare to the values detected by PX4. The sections below show some approaches to getting the measured range.

The QGroundControl MAVLink Inspector lets you view messages sent from the vehicle, including DISTANCE_SENSOR information from the rangefinder. The main difference between the tools is that the Analyze tool can plot values in a graph.

::: info The messages that are sent depend on the vehicle configuration. You will only get DISTANCE_SENSOR messages if the connected vehicle has a rangefinder installed and is publishing sensor values. :::

To view the rangefinder output:

  1. Open the menu Q > Select Tool > Analyze Tools:

    Menu for QGC Analyze Tool

  2. Select the message DISTANCE_SENSOR, and then check the plot checkbox against current_distance. The tool will then plot the result: QGC Analyze DISTANCE_SENSOR value

You can also use the QGroundControl MAVLink Console to observe the distance_sensor uORB topic:

listener distance_sensor 5

::: info The QGroundControl MAVLink Console works when connected to Pixhawk or other NuttX targets, but not the Simulator. On the Simulator you can run the commands directly in the terminal. :::

For more information see: Development > Debugging/Logging > Sensor/Topic Debugging using the Listener Command.

Simulation

Gazebo Simulation

Lidar and sonar rangefinders can be used in the Gazebo simulator. To do this you must start the simulator using a vehicle model that includes the rangefinder.

Downward facing sensors that write to the DistanceSensor UORB topic can be used to test use cases such as landing and terrain following:

Front-facing sensors that write to ObstacleDistance can be used to test Collision Prevention:

Gazebo-Classic Simulation

Lidar and sonar rangefinders can be used in the Gazebo Classic simulator. To do this you must start the simulator using a vehicle model that includes the rangefinder.

The iris optical flow model includes a Lidar rangefinder:

make px4_sitl gazebo-classic_iris_opt_flow

The typhoon_h480 includes a sonar rangefinder:

make px4_sitl gazebo-classic_typhoon_h480

If you need to use a different vehicle you can include the model in its configuration file. You can see how in the respective Iris and Typhoon configuration files:

  • iris_opt_flow.sdf

      <include>
        <uri>model://lidar</uri>
        <pose>-0.12 0 0 0 3.1415 0</pose>
      </include>
      <joint name="lidar_joint" type="revolute">
        <child>lidar::link</child>
        <parent>iris::base_link</parent>
        <axis>
          <xyz>0 0 1</xyz>
          <limit>
            <upper>0</upper>
            <lower>0</lower>
          </limit>
        </axis>
      </joint>
    
  • typhoon_h480.sdf

      <include>
        <uri>model://sonar</uri>
      </include>
      <joint name="sonar_joint" type="revolute">
        <child>sonar_model::link</child>
        <parent>typhoon_h480::base_link</parent>
        <axis>
          <xyz>0 0 1</xyz>
          <limit>
            <upper>0</upper>
            <lower>0</lower>
          </limit>
        </axis>
      </joint>