Minimum set of ROS nodes for "go to (x,y)"?

asked 2019-05-11 01:52:14 -0500

chrisalbertson gravatar image

I'm wring a path planner independent of the LIDAR based nav stack. (My platform works outdoors in places that are unmapped)

The robot has a base controller that works well with joystick teleoperation and it publishes /odom and dose /tf broadcast that seems to work

My global planner can produce a set of waypoints in world (x,y)

What I just started to write is a local planner that will send a stream of cmd_vel messages to drive a smooth Bezier curve over the next few waypoints but taking care not to exceed some specified accelerations and velocities. I am not even calling this a planner as the planning product is the queue of waypoints. I call it an "driver" or "plan execution node"

It occurred to me that this node must be already written. It is just "points in, cmd_vel out" Anyone got a pointer?

edit retag flag offensive close merge delete


Not sure, but this may be something yocs_waypoints_navi and similar packages can do (I'm not sure how yocs_waypoint_provider is related exactly, but it seems similar).

gvdhoorn gravatar image gvdhoorn  ( 2019-05-11 04:28:01 -0500 )edit