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

Timestamps laserscan messages #47

Closed
rostest opened this issue May 4, 2022 · 1 comment · Fixed by #48
Closed

Timestamps laserscan messages #47

rostest opened this issue May 4, 2022 · 1 comment · Fixed by #48

Comments

@rostest
Copy link
Collaborator

rostest commented May 4, 2022

The timestamps in the header of pointcloud messages (i.e. msg.header.stamp of ros::sensor_msgs::PointCloud2 messages) are lidar ticks converted to ros-time using a software pll. The timestamp in the header of laserscan messages (msg.header.stamp of ros::sensor_msgs::LaserScan messages) ist the ros-time when receive the telegram. The timestamp of the laserscan messages should be identical to the timestamp of pointcloud messages.

rostest pushed a commit that referenced this issue May 4, 2022
Timestamp of pointcloud and laserscan messages identical and computed from lidar ticks by software-pll
@rostest
Copy link
Collaborator Author

rostest commented May 4, 2022

Release 2.6.3: Timestamp of pointcloud and laserscan messages identical and computed from lidar ticks by software-pll

@rostest rostest closed this as completed May 4, 2022
@rostest rostest linked a pull request May 4, 2022 that will close this issue
rostest added a commit that referenced this issue May 4, 2022
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.

1 participant