Hello, I am using the lidar_replay sample to get individual bin files for each lidar frame. I noticed that the values for intensity have a range from 0 to 2000s depending on the drive. However, in the documentation for dwLidarPointXYZI it states that the range should be within 0 to 1. Is there a reason for this difference?
I also observe this behavior in the lidar file included with the sample: “/samples/sensors/lidar/lidar_os2128_v5.bin”.
Please provide the following info (check/uncheck the boxes after creating this topic): Software Version
DRIVE OS Linux 5.2.6
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other
The command below saves individual frames as bin files to the output-dir. “/samples/sensors/lidar/lidar_os2128_v5.bin” is the default for --param=file=/samples/sensors/lidar/lidar_os2128_v5.bin
This is a bug of not scaling intensity to [0, 0] in the decoder in DriveWorks 3.5 release.
As far as I know, Ouster will publicly release for their new plugin (based on DriveWorks 3.5 and 4.0) that covers all models with the latest FW within the next days.
We would suggest you contact Ouster, and make sure they can inform you once available.
Thanks.