Compact Livox, configurable Ouster and 32-channel Hesai sensors used in robotic perception stacks.
Comparison 03 · Audit sample
Robot 3D LiDAR evidence table
Panoramic LiDAR specifications with reflectivity, return mode and configuration attached.
A single “range” number is misleading unless reflectivity, ambient light, channel and detection criterion match.
| Field | Livox MID-360 | Ouster OS1 | Hesai Technology XT32 |
|---|---|---|---|
| Range claimReflectivity and instrument-range distinctions remain visible. | 40 m @ 10%; 70 m @ 80%MTarget reflectivity; 100 klx ambient illumination.Source ↗ | 90 m at 10% reflectivity; 200 m maximumMReflectivity is stated for the 90 m figure; maximum-range condition differs.Source ↗ | 0.05–120 mMManufacturer product-table range; user manual additionally conditions capability by reflectivity and channel.Source ↗ |
| Point rateReturn mode and family configuration matter. | 200,000 points/sMFirst return.Source ↗ | 5.2 million points/sMMaximum published family configuration.Source ↗ | 640,000 points/sMSingle return; dual-return rate differs.Source ↗ |
| Field of viewHorizontal and vertical axes are not collapsed. | 360 × 59 °MHorizontal 360°; vertical −7° to +52°.Source ↗ | 45 °MHorizontal field is panoramic for the spinning sensor.Source ↗ | 360 × 31 °MHorizontal × vertical.Source ↗ |
| ChannelsNot every scanning architecture uses channels the same way. | UnknownNo adequate published value in the selected source set. | 128 channelsMFamily maximum; ordered SKU matters.Source ↗ | 32MNo extra condition in selected source.Source ↗ |
| PowerUnknown is shown when the selected citation does not support the field. | 6.5 WMManufacturer average.Source ↗ | UnknownNo adequate published value in the selected source set. | UnknownNo adequate published value in the selected source set. |
| SynchronizationProtocol support is only one layer of timing performance. | IEEE 1588-2008 PTPv2 / GPSMNo extra condition in selected source.Source ↗ | UnknownNo adequate published value in the selected source set. | GPS / PTPMThe user manual lists ≤1 μs PTP clock accuracy under its stated conditions.Source ↗ |
Values are transcribed from the linked sources and were checked on the date shown by each record. V = independently verified; M = manufacturer claimed; D = RCI derived; C = conflicting; U = unknown.
Interpretation rule
The condition belongs to the number.
RCI does not compute winners from this audit sample. The table’s purpose is to show what can be compared now, what requires a shared test, and which public fields are still missing.
Read the full method →