LidarDriver yields point-cloud frames from a spinning, solid-state or single-line ranging device.
The interface
Capabilities
Frames
EachLidarFrame holds timestamp_ns, sequence, optional metadata, and points, a tuple of LidarPoint in the sensor body frame: +x forward, +y left, +z up, in metres.
Single-line and spinning sensors
The driver layer does not distinguish single-beam rangefinders from 3D LiDARs. A 1D rangefinder yields frames withpoints_per_frame=1.
Opening the driver from your plugin
Your plugin callsdiscover(), open() and consumes frame_iterator itself, then publishes what it derives (nearest obstacle, a downsampled scan) with ctx.telemetry.extend or ctx.events.publish. The pattern is on Driver layer. Most LiDARs need hardware.uart or hardware.usb.
Next steps
Driver layer
The shared contract and the manifest table.
Hardware testing
Replay recorded data when no sensor is on the bench.
GPS driver
The next driver kind.