JehanJay's profile - activity

I am using slam_toolbox for mapping from Ros2 bag files. The slam toolbox generates the map exceptionally well. Also using the slam toolbox plugin or by using the commands given in the Git repo it is of course possible to generate the pose graph file to be used in localization mode afterward.

I am using Ros2 Galactic and the question is as follows:

Even though the map is generated by the Slam toolbox, the trajectory path (preferably with a line) is not shown in Rviz2 with Slam toolbox. However, instead of a line, the trajectory is shown with multiple dots which is not what I needed.

Is there a way to fix this issue and get the trajectory path n RViz2 with a line in the generating Map itself?

The requirement is, a visual evaluation to show the robot trajectory in rviz on top of the map. Yes, it generates using

How to get the robot trajectory plot in RViz2 by Slam toolbox I am using slam_toolbox for mapping from Ros2 bag files. T

How can I obtain the estimated localization trajectory of the robot as a list of TF messages? Ideally, at the same frequency as the laser measurements. Background: I want to use that trajectory as the localization of my robot in TF for lookups.

Estimated localization trajectory of the robot as a list of TF messages using SLAM Toolbox How can I obtain the estimate

SLAM Toolbox: Difference between Offline and Online Async/Sync launch files I've gone through most of the material provi

Are the timestamps of /odom messages and the TF messages the same? That could be what's causing it if you're running a s

@ericnasanta , I created a script to translate all the /odom messages and write/publish them in /tf topic. If you're us

@ericnasanta , I created a script to translate all the /odom messages and write/publish them in /tf topic. If you're us

I created a script to translate all the /odom messages and write/publish them in /tf topic. If you're using a rosbag fi

Hi everyone,

I am using slam_toolbox (in ROS2 Galactic) to generate a map of an environment using Ros2 bag files of recorded Odometry and Laser Scan data. However, when starting the slam toolbox via ros2 launch slam_toolbox online_sync_launch.py I get the following error.

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

Device information: - OS: Ubuntu - OS version: 20.04 - CPU: Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz x 8 - GPU Nvidia: GeForce MX130 - Memory : 8GB

Moreover, I have used the default configuration of the slam toolbox as below, and warnings are shown here:

# ROS Parameters
odom_frame: odom
map_frame: map
base_frame: base_footprint
scan_topic: /scan

Clearly, RVIZ2 warnings are caused by the slam-toolbox which is not functioning as messages are getting discarded because the queue is full. Additionally, the rqt-graph looks like this:

I suspect my issue is with my slam configuration. Has anyone seen this type of error before? I feel like I'm missing something easy.

Yes, the problem was due to not having the complete TF tree. Translating all the Odom messages to TF solved the issue fo

[slam_toolbox]: Message Filter dropping message: for reason 'discarding message because the queue is full' Hi everyone,

[slam_toolbox]: Message Filter dropping message: for reason 'discarding message because the queue is full' Hi everyone,