-
Notifications
You must be signed in to change notification settings - Fork 643
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
I can't run two lidar at the same time #532
Comments
If both lidar are on the same network, you must use the web interface to configure different IP address and ports for each lidar. |
I got different IP my lidar is hdl64e so it can't use web interface and only can change IP not for port |
Even if the devices have different IP addresses, if they are both broadcasting to the same port, you will receive the data from both lidars on that one port. You must either separate them into different physical networks or change the port. On HDL-64Es, I believe this must be done using the serial (RS232) interface. However, I don't believe this is the cause of your problem. Try running two separate launch files instead of one launch file and see if you get the same error. |
Please complete the following information:
I got different IP different RJ45
lidar1 IP:172.20.102.31 port:2368 destination:172.20.102.102
lidar2 IP:172.20.2.32 port:2368 destination:172.20.2.101
I can run run lidar each other, but can't at the same time.
it awlays output
[ WARN] [1695786609.867868744]: Velodyne poll() timeout
[ERROR] [1695786609.867924776]: DriverNodelet::devicePoll - Failed to poll device.
what's problem ?
this is my rosnode list
/rosout
/velodyne_1/velodyne_1_nodelet_manager
/velodyne_1/velodyne_1_nodelet_manager_driver
/velodyne_1/velodyne_1_nodelet_manager_laserscan
/velodyne_1/velodyne_1_nodelet_manager_transform
/velodyne_2/velodyne_2_nodelet_manager
/velodyne_2/velodyne_2_nodelet_manager_driver
/velodyne_2/velodyne_2_nodelet_manager_laserscan
/velodyne_2/velodyne_2_nodelet_manager_transform
this my launch file
The text was updated successfully, but these errors were encountered: