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

TIM551 points have bad coordinates. #166

Closed
piervito-salvo opened this issue May 10, 2023 · 1 comment · Fixed by #168
Closed

TIM551 points have bad coordinates. #166

piervito-salvo opened this issue May 10, 2023 · 1 comment · Fixed by #168

Comments

@piervito-salvo
Copy link

Hi,

We are using the ROS 1 driver on ROS Noetic with a TIM551 Lidar. We are supposed to get measurements from -135° to 135°; instead, when we look at the pointcloud on RVIZ, the points seem to be 360°.

It seems that the 271 points are "stretched" in order to cover the full 360° degrees instead of the the 270°. In the end, the effect is that straight walls are seen as curved lines.

We are using default launch file parameters

Why is this happening?

rostest added a commit that referenced this issue May 12, 2023
@rostest rostest linked a pull request May 12, 2023 that will close this issue
@rostest
Copy link
Collaborator

rostest commented May 12, 2023

Thanks for reporting! We corrected the angle settings and updated sick_scan_xd. Please checkout branch feature/angle_correction on https://github.com/SICKAG/sick_scan_xd/tree/feature/angle_correction and rebuild. The branch will soon be merged into the master (release 2.9.1).

aiplemaSICKAG added a commit that referenced this issue May 15, 2023
* Angle correction (min/max angle settings), fix TIM551 points have bad coordinates. #166
* TiM240 initialization (start measurement)
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

Successfully merging a pull request may close this issue.

2 participants