ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Solved. The issue was that I was playing the bag file on the /scan topic. Definitely, the messages had old time stamps. So, converting the messages with the now() time stamps resolved the issue. You can see it in the message filter error message (that's how I figured it):

[slam_gmapping-1] [INFO] [1643650251.253186111] [slam_gmapping]: Message Filter dropping message: frame 'cloud' at time 1640201165.546 for reason 'Unknown

Solved. The issue was that I was playing the bag file on the /scan topic. Definitely, the messages had old time stamps. So, converting the messages with the now() time stamps resolved the issue. You can see it in the message filter error message (that's how I figured it):

[slam_gmapping-1] [INFO] [1643650251.253186111] [slam_gmapping]: Message Filter dropping message: frame 'cloud' at time 1640201165.546 for reason 'Unknown

1643650251 - January 2022 in Unix time 1640201165 - Dec 2021

Solved. The issue was that I was playing the bag file on the /scan topic. Definitely, the messages had old time stamps. So, converting the messages with the now() time stamps resolved the issue. You can see it in the message filter error message (that's how I figured it):

[slam_gmapping-1] [INFO] [1643650251.253186111] [slam_gmapping]: Message Filter dropping message: frame 'cloud' at time 1640201165.546 for reason 'Unknown

1643650251 - January 2022 in Unix time time; 1640201165 - Dec 2021

Solved. The issue was that I was playing the bag file on the /scan topic. Definitely, the messages had old time stamps. So, converting the messages with the now() time stamps resolved the issue. You can see it in the message filter error message (that's how I figured it):

[slam_gmapping-1] [INFO] [1643650251.253186111] [slam_gmapping]: Message Filter dropping message: frame 'cloud' at time 1640201165.546 for reason 'Unknown

1643650251 - January 2022 in Unix time; 1640201165 - Dec 2021

To answer my original question, the difference between the static transform and dynamic in this particular case. That's what happened. When publishing static tf transforms odom => base_link and base_link => cloud, the time stamps of the /scan messages were disregarded by the message filter. Whereas, when I tried to use dynamic odom => base_link transform, it did matter. So the issue came about. Not intuitive, but good to know.