-
Notifications
You must be signed in to change notification settings - Fork 546
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
Using slam_toolbox for localization #744
Comments
This is Nav2, not slam toolbox, please file with the correct repository. |
Sorry but I could not understand, isn't this slam_toolbox issues page? |
Oh sorry, that's my bad misreading my notifications tray 😆
It occurs here, which is called from here. What I can ascertain is that |
Thank you for your response; Could this be the underlying cause of the localization issue I'm experiencing? When I start the localization process, the robot initially localizes itself correctly for a few seconds. However, shortly after, I see the message "[localization_slam_toolbox_node-1] Registering sensor: [Custom Described Lidar]" in the logs, and the robot's position on the map changes unexpectedly. Below is the output with additional debug logs that I added for further insight:
I have created one node for limiting datas from lidar sensor and it outputs datas like:
And from the yaml file of localization, we can see min and max values:
But I can't still solve the problem with localization. I want turtlebot3 to localize itself in the pre-saved map without needing to set initial position from rviz or something. Weird part here is that localization works for couple of seconds and then breaks. One solution would be to echo the /pose topic when localization starts but no luck. It publishes data to /pose topic after localization breaks (after couple of seconds), so data is incorrect. Thank you again... |
I see you are using: |
Thanks for the reply. This is my localization_launch.py file:
This is my nav2_params.yaml file that I use for navigation:
|
Hello,
I am using turtlebot3 simulation to simulate localization in pre-saved and serialized map. I am experiencing issues with slam_toolbox in localization mode while using it in a simulation environment. Initially, the localization works correctly, but after a few seconds, the robot's pose becomes inconsistent, and it seems to jump to random position on the map. The following points describe the problem in detail:
I have ensured that there are no inf values in the laser scan ranges.
However, I still see the following warning repeatedly in the logs:
Info: clipped range threshold to be within minimum and maximum range!
I wonder if this could be affecting the scan matching process and leading to incorrect localization.
TF Tree and Topic Rates:
The TF tree looks correct, and the parent-child relationships are properly defined.
Topic rates are as follows:
/filtered_scan: ~10 Hz
/odom: ~29 Hz
/tf: ~49 Hz
Despite these seemingly correct rates, the localization eventually fails.
Attempted Solutions:
I have followed the discussions in related GitHub issues (#720, #611, #576, #465, #422, #415) but have not found a solution that resolves my problem.
I tried using debug logs and tools like swri_console to understand the issue better, but nothing conclusive was found.
Launch Command:
ros2 launch slam_toolbox localization_launch.py params_file:=/path/to/mapper_params_localization.yaml
mapper_params_localization.yaml:
Thanks everyone...
The text was updated successfully, but these errors were encountered: