Closed RayOwwen closed 2 years ago
I suggest asking on ROS Answers and start some debugging on your side. This could be such a huge litany of user issues of not dotting your "I"s and crossing your "T"s. There's a chance this could be a Nav2 related issue, but that seems doubtful. Make sure you know what applying that namespace is launch is actually going and check out all the topics and data flow in your compute network and see if something is fishy.
Bug report
Required Info:
Steps to reproduce issue
1.Modify tb3_simulation_launch.py, don't use composition.
2.Modify navigation_launch.py,for adding namespace to planner_server node.
Expected behavior
My target is to start two planner_server node in different namespace. The two planner_server have different global_costmap parameters, one without obstacle layer, so I can computer path in different global_costmap.
Actual behavior
When I add namespace to planner_server node, and the global_costmap cannot work properly, with tf error.
Additional information
But, when I echo the tf from base_link to map, it seems no problem.