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

Occasional distorted scans #17

Open
tim-fan opened this issue Jul 16, 2020 · 0 comments
Open

Occasional distorted scans #17

tim-fan opened this issue Jul 16, 2020 · 0 comments

Comments

@tim-fan
Copy link

tim-fan commented Jul 16, 2020

I have noticed some instances where a single scan from this driver will be distorted. See images below for example:

A 'good' scan from the driver:
r2000ScanNormal

A distorted scan, taken in the same area:
r2000ScanDistorted

I've noticed that the number of points in the distorted scan is fewer than in the good scan - I'm guessing an incomplete/partial scan has been received, which is then 'stretched' to make a full 360 degree scan. See this line, where angle_increment is set on the assumption that the full scan was received:
scanmsg.angle_increment = 2*M_PI/float(scandata.distance_data.size());
https://github.com/dillenberger/pepperl_fuchs/blob/master/pepperl_fuchs_r2000/src/rosnode/r2000_node.cpp#L127

Note this was observed a couple years ago, so I cannot provide much detail on what I was running when I observed it, except it was on a laptop running kinetic. I decided to log this issue when I saw another user apparently experiencing the same issue on answers.ros:
https://answers.ros.org/question/316652/data-error-with-pepperl-fuchs-r2000-with-ros-kinetic/#

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

1 participant