-
Notifications
You must be signed in to change notification settings - Fork 204
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
Simple tf causes "Message removed because it is too old" #43
Comments
Hi,satoshimiya, |
@satoshimiya, I had the same issue with the Livox and was wondering the same thing; Unlike while rosbag files which can publish the simulation clock using the @Livox-SDK, if I do not have any other sensors along with the Livox (not even a GPS sensor), how can I synchronize Livox messages with the current ROS time? I used a hacky work around to resolve the issue. I created a node that subscribes to |
@RakVish1342 is it working for your method? I face the same problem. Does Livox can not show pointclouds in RViz with a static_tf_publisher or it can not work in our codes too? |
@gongyue666, I do not use the livox lidar any more. However, the technique that I had mentioned in the workaround should resolve your rviz visualization issue. In my workaround I write a subsrciber that subscribes to the |
@RakVish1342 Thx very much~ |
Hi,
I have added very simple static tf publisher in "livox_lidar_rviz.launch" but PointCloud2(/livox/lidar) is not published with the error saying "Message removed because it is too old".
This is the 1-line code I added to the launch file.
<node pkg="tf" type="static_transform_publisher" name="cab_livox_tf" args="1 0 1 0 0.785398 0 cab_frame livox_frame 100"/>
The PointCloud2 was displayed without this single line. Only this single line is causing error somehow.
I have checked tf tree but it looks fine. As this is not rosbag, typical answer to this error such as "set /use_simu_time true" does not work.
It would be highly appreciated if someone can provide a solution to this issue.
The text was updated successfully, but these errors were encountered: