-
Notifications
You must be signed in to change notification settings - Fork 563
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
Running rtab in ros2 humble #1255
Comments
Can you show the full log? I cannot reproduce the issue, both examples are working on my side. |
it's full logs. working in ros2 humble |
You may want to check if all these topics are published:
|
Publishing is progressing normally. Is there a topic name for rtab? I am receiving data from Intel RealSense and remapping topic names. |
If all those topics are published, you should not get the In this example, |
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: