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

Regarding the use of static path publishing in feature packs? #79

Open
ju-mingyue opened this issue Nov 26, 2021 · 0 comments
Open

Regarding the use of static path publishing in feature packs? #79

ju-mingyue opened this issue Nov 26, 2021 · 0 comments

Comments

@ju-mingyue
Copy link

ju-mingyue commented Nov 26, 2021

@Nasupl
Dear Mr. Nasupl, In the function package, I found that there is a function package released by static path. According to my understanding, we need to draw the path first, publish the function package through the static path, publish the path to the robot, and then track the path through algorithms such as dwa right? Or can you guide me on the correct use of this feature pack?
I currently have the following problems with waypoints_nav:

When I was running waypoints_saver, I found that I can only store one calibrated point, which is the last position reached. This point is through the use of 2D_nav_goal in rviz
For the points marked by the button, did I have any problems during the operation? My operation method is as follows:

1、Start the sensor startup file of the robot (such as: handle, lidar, etc.)
2、Start the completed map
3、Start the waypoints_saver program
4、Use the handle to control the robot to reach a certain point on the map, and use the 2D_nav_goal button in rviz to mark the point.
When I enter the points into the waypoints.yaml file, but after starting the waypoints_nav file, the robot will not execute in the order of the entered points, but will automatically plan the path
I hope to get your reply, it is greatly appreciated!

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

1 participant