TF-Luna — 8 m Low Cost LiDAR Distance Sensor

The TF-Luna operates from 0.2m to 8m with 90% reflectivity in both indoor and outdoor conditions, and 0.2m to 2.5m with 10% reflectivity. Range varies based on target reflectivity and ambient light; the 8m maximum assumes a standard white board (90% reflective) tested indoors at 25°C. For lower-reflectivity targets (10%), maximum range drops to 2.5m.

The TF-Luna supports three interfaces: UART (default 115200 baud, adjustable), I²C (slave mode with 400kbps maximum transmission rate and default address 0x10), and I/O. The communication level is LVTTL (3.3V logic), and the I²C address range is 0x08–0x77, allowing multiple sensors on the same bus.

The TF-Luna is optimized for auxiliary focus (camera autofocus), elevator projection (cabin detection), intrusion detection, and level measurement (silo/tank monitoring). Its small size (<35mm length), low power (<0.35W), and high frame rate (up to 250Hz) make it ideal for compact systems like UAVs, AGVs, and IoT devices where space and power are constrained.

The TF-Luna delivers ±6cm accuracy at distances 0.2m–3m and ±2% accuracy from 3m–8m, with a distance resolution of 1cm. These specifications are based on indoor testing with a standard white board (90% reflectivity) at 25°C, representing best-case conditions for high-reflectivity targets.

Operating temperature ranges from -10°C to +60°C, with storage temperature from -20°C to +75°C. The sensor has no formal IP rating but uses ABS+PC housing. It tolerates ambient light up to 70Klux (approximately outdoor daylight equivalent) without range degradation, making it suitable for both indoor and outdoor deployment.

The TF-Luna requires a 3.7V–5.2V supply with average current ≤70mA and peak current of 150mA, consuming ≤0.35W on average. This low power budget enables integration into battery-powered systems including drones, mobile robots, and handheld devices without significant power management concerns.

The TF-Luna measures 35mm (L) × 21.25mm (W) × 12.5mm (H) and weighs less than 5g, making it one of the most compact single-point LiDAR modules. Its minimal footprint and weight make it ideal for space-constrained applications like UAV payload integration and embedded IoT systems.

The TF-Luna has a narrow 2° field of view and measures only single points, so it cannot create 2D or 3D maps—unsuitable for mapping or SLAM applications requiring spatial imaging. It also degrades significantly on low-reflectivity targets (<20%), limiting range to 2.5m; not recommended for dark surfaces, transparent materials, or long-distance outdoor applications requiring >8m range. Peak current spikes (150mA) may stress power-limited systems.

The TF-Luna is more compact (35×21.25×12.5mm vs. larger scanning lidar modules) and lower cost, with single-point measurement up to 8m at 90% reflectivity. However, it lacks the 2D scanning capability of devices like the Lightware SF45 and operates in narrower conditions (2° FOV vs. wider scanning fields). For range-only applications requiring small size and low power, TF-Luna competes on compactness; for mapping-capable sensors, it serves different use cases.

The TF-Luna integrates with Arduino (UART/I²C via serial shields), ROS (community drivers available for UART), Pixhawk autopilots (via rangefinder MAVLink protocol over UART), and industrial PLCs (via UART/I²C) through standard communication protocols. The LVTTL (3.3V) logic level is compatible with most microcontroller ecosystems; users may need level shifters for 5V systems. Default UART at 115200 baud and I²C slave at 0x10 are immediately usable in embedded and robotics stacks.

Use a USB-to-I2C adapter such as CH341 and BW_CheckWINCC to send the switch command. Some models also support the hardware method on PIN5. TFmini-S, TFmini Plus, and TF02-Pro commonly select I2C with PIN5 tied to GND; follow the model manual to remove that connection or send the matching command when returning to UART.

Check the I2C selection state on PIN5, the default address 0x10, and the Pixhawk parameters RNGFND1_TYPE=20 and RNGFND1_ADDR=0x10. Share a common ground, keep the I2C cable at or below 40 cm where possible, and verify power, pull-ups, and wiring order.

Yes. It is a confirmed firmware issue in v3.3.1: the register can read 0x0000 regardless of the actual frame rate. It is fixed in v3.5.1; update early-batch devices according to the model upgrade instructions.