[Solved] Rosbotxl navigation problem

I am following the navigation tutorial from rosbotxl github. I donwload the repository in boht places (the rosbotxl and my computer). Both elements are in the same network (i can ping from both). When I run ./sync_with_rosbot.sh <ROSbot_ip> I got the following:

sending incremental file list
.env
.gitignore
LICENSE
README.md
compose.pc.yaml
compose.rosbot.yaml
compose.sim.gazebo.yaml
sync_with_rosbot.sh
.git/HEAD
.git/config
.git/description
.git/index
.git/packed-refs
.git/hooks/applypatch-msg.sample
.git/hooks/commit-msg.sample
.git/hooks/fsmonitor-watchman.sample
.git/hooks/post-update.sample
.git/hooks/pre-applypatch.sample
.git/hooks/pre-commit.sample
.git/hooks/pre-merge-commit.sample
.git/hooks/pre-push.sample
.git/hooks/pre-rebase.sample
.git/hooks/pre-receive.sample
.git/hooks/prepare-commit-msg.sample
.git/hooks/push-to-checkout.sample
.git/hooks/update.sample
.git/info/exclude
.git/logs/HEAD
.git/logs/refs/heads/main
.git/logs/refs/remotes/origin/HEAD
.git/objects/pack/pack-2f3c479ea064350d7723f547b4b7bddca6dbb3d6.idx
.git/objects/pack/pack-2f3c479ea064350d7723f547b4b7bddca6dbb3d6.pack
.git/refs/heads/main
.git/refs/remotes/origin/HEAD
config/amcl_params.yaml
config/amcl_params_mecanum.yaml
config/nav2_params.yaml
config/nav2_params_mecanum.yaml
config/nav2_params_pure_pursuit.yaml
config/navigate_w_recovery.xml
config/rosbot.rviz

sent 4.165 bytes received 2.015 bytes 12.360,00 bytes/sec
total size is 123.983 speedup is 20,06
Setting up watches. Beware: since -r was given, this may take a while!
Watches established.

Then I lunch both compose, in the robot and in my computer(ubuntu 22.04), all dockers up correctly but the RVIZ does not show anything and when I run: ros2 topic list in the computer console It also does not show any topic related with the rosbotxl. When I run the same command in the rosbotxl appears all the topics
Is there any requirements related with the network to run the tutorial or I missing something?

Hi @avillaj88,

I guess it’s caused by the network configuration defined in the net.env file, and the culprit is the ROS_DOMAIN_ID=123 line. If you change it to 0 and restart containers you should be able to see ROSbot topics from your computer (I change repo for default 0 value).
However, I don’t understand why RViz didn’t work, unless you didn’t run it via compose.pc.yaml but from a terminal.
Let me know if it solved the problem If not you can also try setting up RMW_IMPLEMENTATION the same on both device (try rmw_cyclonedds_cpp or rmw_fastrtps_cpp)

Regards and I wish you success,
Rafał Górecki

This topic was automatically closed after 4 days. New replies are no longer allowed.

Continuation: