You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently trying to map 3D images using rtabmap, but the demo file does not work.
The following log appears: How can I solve this?
ros2 launch rtabmap_example realsense_d435i_stereo.launch.py
ros2 launch rtabmap_examples realsense_d435i_color.launch.py
Both have the same problem.
[rtabmap_viz-4] [WARN] [1734099294.581896098] [rtabmap_viz]: rtabmap_viz: Did not receive data since 5 seconds! Make sure the input topics are published ("$ ros2 topic hz my_topic") and the timestamps in their header are set. If topics are coming from different computers, make sure the clocks of the computers are synchronized ("ntpdate"). Ajusting topic_queue_size (10) and sync_queue_size (10) can also help for better synchronization if framerates and/or delays are different. Parameter "approx_sync" is false, which means that input topics should have all the exact timestamp for the callback to be called.
[rtabmap_viz-4] rtabmap_viz subscribed to (exact sync):
[rtabmap_viz-4] /odom
[rtabmap_viz-4] /camera/infra1/image_rect_raw
[rtabmap_viz-4] /camera/infra2/image_rect_raw
[rtabmap_viz-4] /camera/infra1/camera_info
[rtabmap_viz-4] /camera/infra2/camera_info
[rtabmap_viz-4] /odom_info
The text was updated successfully, but these errors were encountered:
I am currently trying to map 3D images using rtabmap, but the demo file does not work.
The following log appears: How can I solve this?
ros2 launch rtabmap_example realsense_d435i_stereo.launch.py
ros2 launch rtabmap_examples realsense_d435i_color.launch.py
Both have the same problem.
[rtabmap_viz-4] [WARN] [1734099294.581896098] [rtabmap_viz]: rtabmap_viz: Did not receive data since 5 seconds! Make sure the input topics are published ("$ ros2 topic hz my_topic") and the timestamps in their header are set. If topics are coming from different computers, make sure the clocks of the computers are synchronized ("ntpdate"). Ajusting topic_queue_size (10) and sync_queue_size (10) can also help for better synchronization if framerates and/or delays are different. Parameter "approx_sync" is false, which means that input topics should have all the exact timestamp for the callback to be called.
[rtabmap_viz-4] rtabmap_viz subscribed to (exact sync):
[rtabmap_viz-4] /odom
[rtabmap_viz-4] /camera/infra1/image_rect_raw
[rtabmap_viz-4] /camera/infra2/image_rect_raw
[rtabmap_viz-4] /camera/infra1/camera_info
[rtabmap_viz-4] /camera/infra2/camera_info
[rtabmap_viz-4] /odom_info
The text was updated successfully, but these errors were encountered: