-
Notifications
You must be signed in to change notification settings - Fork 639
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 multiple velodynes (improved) #39
Conversation
I forgot to mention: compared to @ddillenberger implementation, we added a parameter for the udp port to read from. |
This has been running with success on our system for quite some time already. |
Good to know, Brice. Sorry I have been so slow to work on this driver. I am not actively using it myself these days. Would you be interested in being a co-maintainer? |
OK. But I'm not using it much either. I have access to a few Pucks and a 64. |
Is your calibration method proprietary, or would you be interested in sharing it? |
it's proprietary. The good news is that for the Pucks, it we don't need a calibration file. |
@jack-oquin OK I'll volunteer to be a maintainer |
I appreciate your help. |
support for multiple velodynes
This is an improvement on @ddillenberger implementation of the multi velodyne support. From what I understand from his design, and from what I experienced today on my setup (4 16-beam velodynes), @ddillenberger code allows to read data from one and only one laser at the same time.
With this pull request, we add support for reading data simultaneously from several lidars at the same time. Each lidar must be configured with a separate IP address and to broadcast on a separate port.
With this code, we were able to read from 4 velodyne at the same time.
Credits also go to @ddillenberger and @ahendrix for this pull request.