Ussama Naal

> Another question regarding the azimuth window I had while experimenting these last days, is that I want to use the Multipurpose I/O for triggering another sensors, preferably I would...

The sensor only generates acceleration and angular velocity, and the driver is publishing these raw values as is. We would need to do further processing to produce orientation values. I'll...

The way I understood the issue is that it only happens when the sensor is connected to a PTP clock and the clock is making some adjustments? Right? I don't...

> * if I do a full 360° swipe `ts = std::chrono::nanoseconds(timestamp[v] - timestamp[0])` > * and if I do 90° to 180° > `ts = std::chrono::nanoseconds(timestamp[v] - timestamp[256]) //but...

Was the `my.bag` file recorded using ouster_ros driver (ros1) or was it recorded using a different driver? What happens if you use `rosbag info` on the file?

I think the tool you referenced uses ROS1 when performing the conversion. You would need to use ros1 bag utilities to replay the files (i.e you would need to use...

Unfortunately, I need to look in depth into this and I am busy building the ros2 driver. So it will be at least another week before I can look into...

Hi @jeychandar, you can utilize any of the two utility scripts supplied in this [PR](https://github.com/ouster-lidar/ouster-ros-extras/pull/2) to convert between our ROS1/ROS2 bag file formats (they are not production ready yet but...

I forgot to link the PR my original post :facepalm: .. appolgies. Here it is https://github.com/ouster-lidar/ouster-ros-extras/pull/2

@ShepelIlya We do have a polling-client and a high volume of packets (640 per seconds for lidar packets alone). It is totally okay to use `ros::Timer` in fact that's the...