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

WP "moves" on each field test on real robot #86

Open
elgarbe opened this issue Feb 23, 2024 · 2 comments
Open

WP "moves" on each field test on real robot #86

elgarbe opened this issue Feb 23, 2024 · 2 comments

Comments

@elgarbe
Copy link

elgarbe commented Feb 23, 2024

Hi, I'm using nav2 GPS WP Logger and follower on a real robot on an outdoor environment.
First I drive the robot with a joystick and log each WP. Then I run nav2 on the robot and Rviz on a laptop. Unfortunately the robot doesn't follow the exact same WP. It's out for a few meters. I'm trying to understand why is this happening.
The first thing I've noticed is that as my robot moves the tf between map and odom drift. That is, odom frame is moving around from 0 to 2mts from map frame. In this point I wonder how it affect to navigation. I saw global cost-map is in map frame, but local cost-map y on odom frame. How is translated the GPS WP to nav2 WP? I know that from GPS to map y transformed using robot_localization, but then nav2 transform the WP to odom frame? Is there a topic that expose current WP goal?
I can add RTK corrections to my GPS, using it I could get GPS position with cm level, but that doesn't remove map to odom drift. Is there a way to remove that offset, moreover is it ok to try to remove that offset on robot_localization filter?

@ZaBy10
Copy link

ZaBy10 commented May 2, 2024

Hii @elgarbe , Could you please tell me how to run this package on a real robot . what are the changes that I need to make ?!

@elgarbe
Copy link
Author

elgarbe commented May 2, 2024

You have to change sensor sources and comment out gazebo package.
You have to check what sensors your robot has and in topics name then make changes on robot_localization configuration file to use them. The same with lidar data.
It's a custom robot? what sensors do you have?

My problem reported in this post was related to GPS errors. I was able to solve it using RTK units.

Maybe you could open a new issue exposing your robot and your sensors and we may help there. I can share a repo with the code that I'm using.

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