Ussama Naal

We don't have this feature at the moment. We'll notify you once this has been added. @hantak3107

Hi @relffok , you are correct the `frame_id` for **LaserScan** message changes when the point_cloud_frame value changes. The `LaserScan` message is rather a new and an incomplete feature. I am...

Currently for the PCL point cloud message the frame selection only affects the xyz caluclated values. We don't apply any transformations to intensity, reflection values, etc that are included in...

If you are subscribing to the **PointCloud2** message through the `/ouster/points` topic then the fields `x, y, z` represent the projected Cartesian coordinates.

You can achieve this by making the sensor a child to another object through a fixed link that has the altitude transformation. This mainly a ROS setup that can be...

The question is more of a pure ros question which can find better answers at https://discourse.ros.org/

There should be some ROS packages that would assist with that, for example: http://wiki.ros.org/lidar_camera_calibration or https://github.com/ankitdhall/lidar_camera_calibration although I haven't tested the interoperability of these packages with Ouster sensors.

Definitely makes sense, @hodnajit with regard to the ros2 driver it implements the ros2 lifecycle managment. which gives you a bit of control over when the node performs configuration and...

I don't think I currently handle the case if the user passes a config with STANDBY to the `set_config` service :disappointed: . I will try to address this in a...

@jdomlac Thanks for contacting us, before I begin, I would have to admit that my answer won't be very complete and there is a bit of work that we may...