-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for old version of RS laser scanner. #93
Comments
Hi please send a pcap file saved by Wireshark and send to alex.guo@robosense.cn so I can check the data for you. Thanks. |
I have the same issue with rs-lidar-16. |
I am also planning to buy an used rs-lidar-16. Any news about this issue? |
Through combining three csv files into one angle.csv(just add the curves.csv and channelnum.csv's data to angle.csv ), the new sdk can read the config from angle.csv. And also you should add the angle_path in config.yaml. |
…pper-douwe Feat/skidpad mapper douwe
I bought three RS-LiDAR-32 with manufacutre date of July, 2018. They have been kept on the shelf for nearly four years, and now I found them and try to use them.
Firstly,
By using the old sdk ros_rslidar, I could get point clouds with correct geometry but without ring and timestamp info.
Then,
I attempted to use the new sdk rslidar_sdk, but unfortunately I got point clouds with geometry of flat circles, just like the issue #68.
Further,
I add the param of angle_path to the config.yaml. It did took some effect: flat circles became 3-dimension circles. Like this:
I would think the potential reason for this is that the lidar version is too old. And like the discussion in other issues, old version of lidars do not output device information via difop port.
The real problem is:
The setting of angle.csv can only make flat point clouds to stand up. I guess I still need the interface to config the curves.csv and ChannelNum.csv in the new sdk to recover corner and edge geometry
Please help!
The text was updated successfully, but these errors were encountered: