Skip to content
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

Amcl not working properly . #1250

Open
Daviesss opened this issue Sep 17, 2023 · 3 comments
Open

Amcl not working properly . #1250

Daviesss opened this issue Sep 17, 2023 · 3 comments

Comments

@Daviesss
Copy link

I have a problem . Which i have been on for the past one week. I dont know why this pops up . I am working on Multi robot collaboration(SLAM) . But for some reasons the error below pops up anytime i use Amcl (the robot cant be able to localize on the map due to this error) . I will be glad if i get a help .

[ WARN] [1694953982.886336265, 170.233000000]: No laser scan received (and thus no pose updates have been published) for 170.233000 seconds. Verify that data is being published on the /robot3/scan topic.

Screenshot from 2023-09-17 13-22-34

@Daviesss
Copy link
Author

I solved this problem. I had to tweak the source code . Since the ros::Duration was greater than my laser scan interval the warning messages pops up and my robot scan topics will not receive scan data . So I had to make changes to that method.

@Bankbuster777
Copy link

I solved this problem. I had to tweak the source code . Since the ros::Duration was greater than my laser scan interval the warning messages pops up and my robot scan topics will not receive scan data . So I had to make changes to that method.

did you mean this duration?
https://github.com/ros-planning/navigation/blob/9ad644198e132d0e950579a3bc72c29da46e60b0/amcl/src/amcl_node.cpp#L509C47-L509C47

@Daviesss
Copy link
Author

To reduce the number of TF_REPEATED_DATA warnings the laser scan publish rate needs to be reduced, because amcl depends on rate of incoming laser messages. I edited the source code of amcl to suit the coordination. Works fine now .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants