RPLIDAR S2
The A1's outdoor-capable upgrade: 30 m range and 32k samples per second, so it resolves a person at distance instead of a blob.
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: Outdoor AMR, larger SLAM maps, people detection.
What the numbers actually mean
The headline figure is 0.05 – 30 m (range), with 10 Hz as the next most load-bearing number (scan rate). At $340 in the sensors tier it sits as a capital purchase. At this price you are buying documentation, repeatability and support as much as metal, and the integration cost is usually larger than the part.
How it compares
Same subsystem, closest alternatives. The primary spec column is usually the one that decides it.
| Part | Price | Primary spec | Second spec |
|---|---|---|---|
| RPLIDAR S22D LiDAR, long range | $340 | 0.05 – 30 m | 10 Hz |
| 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.