CAPABILITY-GATED · NOT SENSOR-LOCKED
Use the hardware that fits your build.
Sensor profiles will expose only the features the connected hardware can actually support. A low-cost 2D LiDAR will not be presented as a 3D surface scanner.
| Planned source | Connection | Data | Feature level |
|---|---|---|---|
| RPLIDAR C1 / compatible 2D | USB serial to Pi or desktop connector | Angle, range, quality, scan rate | 2D raw scan, profiles, obstacle/edge measurements |
| SLAMTEC families | USB/UART/Ethernet by model | Model-specific 2D or mapped data | Capability-negotiated |
| Unitree 4D LiDAR | Ethernet + IMU data | 3D point clouds and motion inputs | Advanced capture, fusion and surface generation |
| Generic 3D LiDAR | Connector adapter | Validated point-cloud frames | Enabled after driver and calibration approval |
| Unicore dual-heading RTK/GNSS | UART/USB/Ethernet by board | Position, heading, fix state and corrections | Tool georeference and pose fusion |
| IMU / sonic / camera | Pi GPIO, USB or network | Pitch, roll, distance and visual context | Machine-profile dependent |
Final hardware support depends on driver validation, calibration, timestamp quality, safe servo mapping and physical bench testing. Product names describe planned compatibility targets, not manufacturer endorsement.