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

incorrect 2d laser scan tf(both horizontal and vertical inversion) #221

Open
flymaxty opened this issue Sep 28, 2023 · 1 comment
Open
Assignees
Labels
bug Something isn't working

Comments

@flymaxty
Copy link

Describe the bug
Hi all, when I use ouster on ROS noetic with this package, I found that 2d laser scan has an incorrect tf.
I'm not sure if I miss something.

To Reproduce
Steps to reproduce the behavior (steps below are just an example):

  1. source ros environment
  2. compile the project workspace
  3. source the project workspace
  4. roslaunch ouster_ros driver.launch sensor_hostname:=192.168.33.7
  5. add /scan to rviz, and put it to white color.
  6. observe the issue ...

Screenshots
Screenshot from 2023-09-28 09-43-31

as you can see laser scan(white dots) is totally different from pointcloud, it seems both horizontal(left right) inversion and vertical(up-down) inversion.

Platform (please complete the following information):

  • Ouster Sensor? OS-0-32-U0
  • Ouster Firmware Version? V2.4.0
  • ROS version/distro? noetic
  • Operating System? Ubuntu 20.04
  • Machine Architecture? x64
  • git commit hash? latest
@flymaxty flymaxty added the bug Something isn't working label Sep 28, 2023
@Samahu Samahu self-assigned this Sep 28, 2023
@Samahu
Copy link
Contributor

Samahu commented Sep 28, 2023

I think this can be explained by the fact that the ROS1 driver version publishes PointCloud in in the "sensor frame" by default. However, the LaserScan message is published in "lidar frame". Currently, you can not change the frame of LaserScan message but you can change the reference frame for the PointCloud message. Not that even with this there is a bit of misalignment on that I spent some time to address (currently focusing on ROS2 PRs = {#203, #204} but will back port to ROS1 once finalized).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants