You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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):
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
The text was updated successfully, but these errors were encountered:
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).
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):
Screenshots
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):
The text was updated successfully, but these errors were encountered: