Sensors · Time-of-flight distance

VL53L1X ToF rangefinder

A 4 m laser rangefinder in a 5 mm package. Uses actual time-of-flight so it is not fooled by black or shiny targets the way IR reflectance sensors are.

$15 indicative ST Time-of-flight distance

The role it plays

Sensors split into proprioception — encoders, IMUs, joint torque, motor current — which tells the robot about itself, and exteroception — LiDAR, depth, force, GNSS — which tells it about the world. Build proprioception first. A robot that does not know where its own joints are cannot use a good world model anyway.

Typical use: Cliff detection, docking, gesture, table-edge sensing.

What the numbers actually mean

The headline figure is up to 4 m (dark), ~1.3 m in bright ambient (range), with 27° as the next most load-bearing number (field of view). At $15 in the sensors tier it sits cheap enough to prototype with and replace without regret, which is the correct way to learn a new subsystem.

GotchaIts field of view is a 27° cone — at 4 m that is a 2 m spot. It is a rangefinder, not a scanner.

How it compares

Same subsystem, closest alternatives. The primary spec column is usually the one that decides it.

PartPricePrimary specSecond spec
VL53L1X ToF rangefinderTime-of-flight distance $15 up to 4 m (dark), ~1.3 m in bright ambient 27°
AS5600 magnetic encoderAbsolute rotary encoder $3 12-bit (4096 counts/rev) I²C (also analog / PWM out)
AS5047P magnetic encoderAbsolute rotary encoder $10 14-bit (16384 counts/rev) SPI + ABI quadrature + UVW
CUI AMT102-VCapacitive incremental encoder $25 up to 2048 PPR (configurable) Quadrature A/B/Z
BNO085 9-DOF IMUIMU with onboard fusion $25 3-axis accel + gyro + magnetometer Quaternion / Euler / rotation vector, plus raw

Where it shows up

It is a component-level choice rather than a defining part of a named platform — pick it for the subsystem it serves, not to match a reference build.