Open r91andersson opened 3 years ago
I've looked your parameters and noticed that your local_costmap global_frame is /world. I want to ask why you gave /world for global_frame. Generally it should be /odom or /map. Please try with /odom and tell me if something changes.
hi, @r91andersson, did you solve this issue?
We're observing strange local path planning while sending goals that are more than 3m away. We've increased the local costmap but no change. When goals are further than 3m away, the orientation of the goal isn't taken into account while the local planner computes the trajectory. This can be seen in the images below. I've sent 3 different goals in different orientations to show that the planner doesn't take care of the orientation. Moreover, the local planner plans a very strange trajectory. Even though the goal is almost in front of the robot. The only time the local planner works if we sending goals that are no more than 3m away. We're not using any obstacles avoidance.
This problem occurs both when running in simulation and with real robot.
@croesmann, do you have any idea?
This is our local costmap config:
This is the global costmap config:
costmap_common_params config
move_base_teb config
Teb Config: