-
Notifications
You must be signed in to change notification settings - Fork 49
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
If Lidar Data doesn't shows up and you've just installed it. #12
Comments
Hey, I am currently working on connecting XT16 LiDAR sensor to ROS2 within my development environment. Despite implementing the suggested fix, I am still unable to receive any data on RViz. Below are the details of my setup: Operating System: Ubuntu 22.04 For further clarity, I have attached a screenshot illustrating the current setup and issue. I would appreciate any guidance or suggestions you might have to resolve this matter. Thanks. |
It seems fine to me...Have you tried catch XT16 LIDAR's packet with wireshark? if not being catched,then try to check your IP addr or else. best debuging guide that i recommend is to debug hesai SDK itself to print more info.(using print()) |
Thanks to Hesai's professional help, I finally find a solution for this error. What most important thing is to turn off ANY firewall like UFW(Ubuntu) or Windows Firewall(Windows). You really need to ensure that there aren't any type of block wall behind u and lidar. Please double check! You need to completely turn off firewall first. Then if u do not have NVIDIA Graphics Cards ,u need to go to CMakeLists.txt and find line 158 158 find_package(CUDA ) And change the WHOLE LINE into 158 find_package(CUDA_FOUND ) Finally, colcon build as official docs says:
By the way, I didn't change anything including config/config.yaml and lidar works well. |
if there is "enable_packet_loss_tool: true" in your "config.yaml" file
it'll executed as debug mode so rviz doesn't work
So,make "enable_packet_loss_tool: false" in your "config.yaml" file
or Delete "enable_packet_loss_tool: true".
The text was updated successfully, but these errors were encountered: