Skip to content
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

velodyne_pointcloud: dynamic reconfigure limits min_range to 0.9 meters #60

Closed
jack-oquin opened this issue Oct 14, 2015 · 5 comments
Closed

Comments

@jack-oquin
Copy link
Member

Some models may support shorter ranges, so configuration should allow smaller settings.

Maybe this is only a theoretical problem, but it prevents people from experimenting.

@jack-oquin
Copy link
Member Author

Apparently, the VLP-16 is limited to 0.9 meters, like most of the other models.

At some point there was an attempt to set min_range to 0.4 in the VLP-16 launch script, but due to bugs in that script and in dynamic reconfiguration it was not having any effect. With those bugs fixed, there are still no points returned from the device at less than about 0.9 meters range.

jack-oquin added a commit that referenced this issue Oct 14, 2015
No known models are currently known to return closer measurements.
@jack-oquin
Copy link
Member Author

The Windows VeloView program does show VLP-16 returns as short as 0.45 meters.

So, there must be some additional bug in this driver.

@jack-oquin jack-oquin reopened this Oct 14, 2015
jack-oquin added a commit that referenced this issue Oct 14, 2015
NOTE: There is still some other problem keeping that from working.
@jack-oquin
Copy link
Member Author

The VLP-16 manual on page 3 does mention a "range from 1m to 100m".

@piyushk
Copy link

piyushk commented Oct 14, 2015

@jack-oquin Thanks for finding that. I missed it in my original sweep.

I'll perform additional testing tomorrow to see if I can find a solution to this problem.

@jack-oquin
Copy link
Member Author

This issue is fixed. The remaining problem with close-range VLP-16 data deserves a separate issue, #61.

vrabaud pushed a commit to vrabaud/velodyne that referenced this issue May 9, 2016
No known models are currently known to return closer measurements.
vrabaud pushed a commit to vrabaud/velodyne that referenced this issue May 9, 2016
NOTE: There is still some other problem keeping that from working.
vrabaud pushed a commit to vrabaud/velodyne that referenced this issue May 9, 2016
No known models are currently known to return closer measurements.
vrabaud pushed a commit to vrabaud/velodyne that referenced this issue May 9, 2016
NOTE: There is still some other problem keeping that from working.
vrabaud pushed a commit to vrabaud/velodyne that referenced this issue May 9, 2016
No known models are currently known to return closer measurements.
vrabaud pushed a commit to vrabaud/velodyne that referenced this issue May 9, 2016
NOTE: There is still some other problem keeping that from working.
vrabaud pushed a commit to vrabaud/velodyne that referenced this issue May 9, 2016
No known models are currently known to return closer measurements.
vrabaud pushed a commit to vrabaud/velodyne that referenced this issue May 9, 2016
NOTE: There is still some other problem keeping that from working.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants