turtlebot4: cannot start sync slam on a remote pc

Please provide the following information:

  • OS: Ubuntu 20.04.05 LTS
  • ROS Distro: Galactic
  • Built from source or installed: installed according to the official documentation
  • Package version: ros-galactic-turtlebot4-navigation (0.1.2-1focal.20220922.210710)

Expected behaviour A map should be created and updated in rviz2

Actual behaviour According to the turtlebot4 user manual I try to start slam_sync.launch.py on a remote pc, but I get the following error repeatedly:

[sync_slam_toolbox_node-1] [INFO] [1665068583.432561558] [slam_toolbox]: Message Filter dropping message: frame 'rplidar_link' at time 1665068582.845 for reason 'discarding message because the queue is full'

When executing view_robot.launch.py, in another terminal, the following errors are shown, repeatedly:

[rviz2-1] [INFO] [1665068580.660212631] [rviz2]: Message Filter dropping message: frame 'rplidar_link' at time 1665068576,397 for reason 'discarding message because the queue is full'
[rviz2-1] Warning: Invalid frame ID "wheel_drop_left" passed to canTransform argument source_frame - frame does not exist
[rviz2-1]          at line 156 in /tmp/binarydeb/ros-galactic-tf2-0.17.4/src/buffer_core.cpp
[rviz2-1] Warning: Invalid frame ID "wheel_drop_right" passed to canTransform argument source_frame - frame does not exist
[rviz2-1]          at line 156 in /tmp/binarydeb/ros-galactic-tf2-0.17.4/src/buffer_core.cpp
[rviz2-1] Warning: Invalid frame ID "wheel_drop_left" passed to canTransform argument source_frame - frame does not exist
[rviz2-1]          at line 156 in /tmp/binarydeb/ros-galactic-tf2-0.17.4/src/buffer_core.cpp
[rviz2-1] Warning: Invalid frame ID "wheel_drop_right" passed to canTransform argument source_frame - frame does not exist
[rviz2-1]          at line 156 in /tmp/binarydeb/ros-galactic-tf2-0.17.4/src/buffer_core.cpp
[rviz2-1] [INFO] [1665068581.171618589] [rviz2]: Message Filter dropping message: frame 'rplidar_link' at time 1665068576,532 for reason 'discarding message because the queue is full'
[rviz2-1] Warning: Invalid frame ID "wheel_drop_left" passed to canTransform argument source_frame - frame does not exist
[rviz2-1]          at line 156 in /tmp/binarydeb/ros-galactic-tf2-0.17.4/src/buffer_core.cpp
[rviz2-1] Warning: Invalid frame ID "wheel_drop_right" passed to canTransform argument source_frame - frame does not exist
[rviz2-1]          at line 156 in /tmp/binarydeb/ros-galactic-tf2-0.17.4/src/buffer_core.cpp
[rviz2-1] Warning: Invalid frame ID "wheel_drop_left" passed to canTransform argument source_frame - frame does not exist
[rviz2-1]          at line 156 in /tmp/binarydeb/ros-galactic-tf2-0.17.4/src/buffer_core.cpp
[rviz2-1] Warning: Invalid frame ID "wheel_drop_right" passed to canTransform argument source_frame - frame does not exist
[rviz2-1]          at line 156 in /tmp/binarydeb/ros-galactic-tf2-0.17.4/src/buffer_core.cpp
[rviz2-1] [INFO] [1665068581.612268664] [rviz2]: Message Filter dropping message: frame 'rplidar_link' at time 1665068577,060 for reason 'discarding message because the queue is full'

Starting sync SLAM on the Raspberry directly is creating the map as expected, with no errors.

To Reproduce Provide the steps to reproduce:

  1. On the remote PC run
ros2 launch turtlebot4_navigation slam_sync.launch.py
  1. On the remote PC, in another terminal, run
ros2 launch turtlebot4_viz view_robot.launch.py
  1. see the error

Other notes

  • When rviz2 is started i can see a static map, which will never get updated. In the TF-tree map and odom is in state Transform OK the rest shows No transform from ...
  • On the remote PC i can echo lidar data, running ros2 topic echo /scan
  • Both, the Raspberry and the remote PC, are connected to the same router via 5GHz-WLAN.
  • Time is in sync on the Raspberry and the remote PC with the following command sudo ntpdate ntp.ubuntu.com

rviz2: image

Best regards Tim

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 22 (7 by maintainers)

Commits related to this issue

Most upvoted comments

@Basavaraj-PN Can you try the following:

  • SSH into the RPi and edit the /etc/chrony/chrony.conf file.
  • Comment out the server 192.168.186.2 presend 0 minpoll 0 maxpoll 0 iburst prefer trust line
  • Save the file and restart the chrony service sudo systemctl restart chrony
  • Restart ntpd on the Create 3

Let me know if that works.