Industrial-grade 2D LiDAR sensors for AGV, AMR and conveyor lines now span 0.1 m to 40 m at 1 to 10,000 Hz frame rates with sub-2 W power budgets, and 3D units have crossed 10 million points per second on 128-channel silicon, defining the operating envelope most line builders are standardising on in 2026 [S1].
Three vendor clusters control that envelope: Chinese dToF and MEMS specialists (Hesai, RoboSense, Benewake), North-American digital LiDAR houses (Ouster, Velodyne), and the European 2D industrial base (SICK, Hokuyo, LEUZE), with a 14.8% CAGR running off a USD 3.4B 2026 anchor [S9][S6].
Vendor clusters and where each one actually wins on a spec sheet
The Chinese volume tier leads automotive shipments on 905 nm MEMS, with Hesai and RoboSense running a manufacturing scale that pressures unit pricing downward through 2026 [S6]. Benewake's TF-series single-point and array modules span 1.35 g to 86 g, anchoring the short-to-medium range industrial slot, while the Ouster OS1 mid-range sensor hits 90 m at 10% reflectivity, 250 m maximum, 0.0 m minimum range, and 10.4 million points per second across 128 vertical channels with a digital architecture that fuses color in silicon rather than post-processing [S1].
The European-2D industrial base, SICK, LEUZE, Hokuyo, plus China's Tianjin G-TEK Sensor Technology, continues to define AGV and conveyor scanner design, while RIEGL and Ouster hold the long-range mapping and mining slots at 50 to 1000 m on 905/1550 nm with both mechanical and flash architectures [S6]. Solid-state wide-FOV units (Richbeam HaloBeam120, HaloBeam240) are explicitly framed as automotive-grade but still have to prove outdoor reliability against spinning mechanical units [S1].
Selection criteria: the five numbers that move POs in 2026
Five numbers drive the spec sheet: range, frame rate, point cloud density, FOV, and power consumption, and vendor data shows they trade off predictably along the product curves [S1]. A Benewake TF-Luna at 0.2 to 8 m, 1 to 250 Hz, 0.35 W, and under 5 g is the typical short-range, low-power pick; the TF03 at 0.1 to 180 m, 1 to 9,800 Hz, IP67, and 86 g is the long-range industrial workhorse; the TFA300 reaches 0.1 to 290 m at 1 to 10,000 Hz for 0.45 W in a 10.5 g package, the densest power-to-weight ratio in that lineup [S1].
For 3D, the OS1 spec sheet puts 90 m at 10% reflectivity as the headline figure versus 250 m absolute max and 10.4 M points per second, the working combination most automation buyers compare against [S1]. Interface choice matters as much as optics: UART, I²C, and I/O dominate short-range boards, while CAN and RS-485 show up the moment the sensor mounts on a moving AGV or mobile robot (TFmini-i, TF02-i, TFA300 all use CAN/RS-485 specifically for vehicle-bus integration) [S1]. Protection class separates enclosure-less modules (TF-Luna, TFA170-L, TF-NOVA) from IP65 (TFmini-S, TF02-Pro) and IP67 (TF03, TF350) units, and that is usually the first line item buyers filter on [S1].
For the maker tier, the Slamtec RPLIDAR A1M8, LDRobot LD19, and XG lidar P100 form the rotating 2D baseline, with baud rates split between 115200 (legacy 5 V Arduino) and 230400 (ESP32-S3 / Teensy 4.1 SLAM), while the VL53L0X and TF-Luna hold the single-point / multi-proximity I²C slots at the bottom of the price stack [S2][S3]. Selection guidance from the maker side emphasises working range, blind zone, interface (UART vs I²C), and ambient light tolerance, with the RPLIDAR C1M1 hitting a 5 cm blind zone versus the A1M8's 15 cm, and TF-Luna detecting from 20 cm out [S2].
Near-blind zone: the underrated AGV failure mode

Near-blind zone, also called minimum detection range, is the shortest distance at which a LiDAR can reliably detect obstacles, and it directly drives AGV collision rates in dense warehousing and human-robot coexistence [S5]. Within the near-blind zone, the sensor either returns no signal or returns point cloud so sparse that algorithms cannot identify obstacles, and the gap between datasheet nominal and real reliable detection is large enough to crash an AGV into a shelf at 1 m/s approach speed [S5].
Warehouse hazards sit exactly in this zone: shelf legs of 5 to 8 cm, floor cables 10 to 20 cm tall, and pallet bottom crossbeams below 20 cm, all within the gap where a 10 cm or 20 cm near-blind zone leaves less than 0.1 s between detection and impact after braking delay [S5]. Mechanical LiDAR (Hesai XT32) loses near-distance returns because the detector's reception window is exceeded by angular deviation, while solid-state units (Livox MID-360, M360) saturate the APD array at close range and require algorithmic compensation to recover a usable point cloud [S5]. Three further failure modes compound the issue: black shelves, transparent film, and reflective metal surfaces increase actual minimum detection distance beyond the nominal spec, point cloud density decays sharply at the blind-zone boundary, and motion blur smears near-distance returns when the AGV is moving [S5].
Comparison matrix: 2D scanners, single-point, and 3D units on the same axes
Lining up the main 2026 options on four decision criteria (range, sample rate, interface, and price band) lets a buyer extract a structured comparison without re-reading every datasheet. Single-point ToF modules (Benewake TF-Luna, VL53L0X) hold the 0.2 to 8 m / 8 m slot at the bottom of the price band, with I²C / UART and 250 Hz to 1 kHz effective rates, while 360° ToF units (youyeetoo FHL-LD19, WayPonDEV FHL-LD19) push 12 m at UART with sample rates up to 21,600 samples per second on the WayPonDEV FHL-LD19 Plus for survey drones [S2][S8].
Industrial 2D LiDAR dominates the AGV slot: the Benewake TF02-Pro runs 0.1 to 40 m at 1 to 1,000 Hz, 1 W, IP65 in a compact package, and the TF03 stretches to 0.1 to 180 m at 1 to 9,800 Hz, IP67, 86 g [S1][S2]. For 3D perception, Ouster's OS1 mid-range digital LiDAR hits 90 m at 10% reflectivity, 0.0 m minimum range, and 10.4 M points per second across 128 vertical channels with native color fusion in silicon [S1]. Among newer automotive-grade options, the Richbeam LakiBeam 2D scanner is positioned for AGV and traffic monitoring with a claimed 40% size reduction against its predecessor, while the HaloBeam120/240 cover 120° and 240-line FOV for blind-spot and autonomous logistics roles [S1].
Limitations, integration cost, and the gaps vendors do not print on the front page

Effective angular resolution falls as scan rate climbs, so a 9.8 kHz TF03 scan is not the same point cloud density as a 100 Hz scan, and spec sheets do not always make that explicit [S1]. Triangulation-based 360° units (Slamtec RPLIDAR A1M8) are less expensive than ToF but lose accuracy at longer ranges and on dark surfaces, while many cheap LiDAR modules struggle under direct sunlight, so ambient light tolerance is a filter, not an afterthought [S2].
On the maker side, the architectural bottleneck is memory: an ATmega328P (Arduino Uno) with 2 KB SRAM cannot buffer a 360° sweep of 400 to 800 points at 9 bytes per point, and the controller will either throw a memory overflow or silently overwrite its own stack, so a 32-bit Teensy 4.1 (ARM Cortex-M7 at 600 MHz) or ESP32-S3 is the practical baseline for any 2D LiDAR scanner Arduino project in 2026 [S3].
Sourcing signals and trackable next nodes
Two signals are worth tracking through the rest of 2026: whether Chinese MEMS pricing pressure continues to push automotive-tier 905 nm unit costs below the prior generation's industrial-2D baseline, and whether solid-state wide-FOV suppliers (Richbeam HaloBeam120/240) publish long-term outdoor reliability data comparable to mechanical incumbents [S1][S6]. For AGV integrators, the next decision point is a reliable-detection test against warehouse hazards, not a re-read of nominal minimum range, because the gap between datasheet and deployment is where the collisions actually happen [S5]. Buyers evaluating 2026 3D digital-twin pipelines should also factor in the labeled-data software stack that now ships bundled with many 2D and 3D units, since the LiDAR software layer has moved from viewer plus classifier to full data pipeline [S9].
The underlying component specifications are covered under capacitive sensor, displacement sensor, and flow sensor.
Background reading: Control Cable Sizing and Selection: 2026 Spec Map for Industrial Engineers.