Revision history [back]

After you bring up the move_base node, you should print the full parameter listing using rosparam list or rosparam dump. This often helps uncover issues where parameters are loaded into the wrong namespace.

In this case, it looks to me like you might be loading your parameters into the "root" namespace (e.g. "/local_costmap"). According to the move_base documentation, these parameters should instead be specified in the node's private namespace (e.g. "/move_base/local_costmap").

Also, have you considered using a launch file to load the parameters and run the node? That would be the normal way this is done in ROS. This automatically loads the parameter files and places the parameters in the node's private namespace.

<launch>
  <arg name="path_file" default="/home/kostasof/Desktop/test_420/Move_Base.xml"/>
  <arg name="cfg_path" value="~/ros_stacks_sc/navigation_kostas/cfg_rafa"/>

  <node name="move_base" pkg="move_base" type="move_base" args="$(arg path_file) wlan0">
    <rosparam command="load" file="$(arg cfg_path)/costmap_common_params.yaml" ns="global_costmap"/>
    <rosparam command="load" file="$(arg cfg_path)/costmap_common_params.yaml" ns="local_costmap"/>
    <rosparam command="load" file="$(arg cfg_path)/base_global_planner_params.yaml"/>
    <rosparam command="load" file="$(arg cfg_path)/base_local_planner_params.yaml"/>
    <rosparam command="load" file="$arg cfg_path)/global_costmap_params.yaml"/>
    <rosparam command="load" file="$arg cfg_path)/local_costmap_params.yaml"/>
  </node>
</launch>

Note: in order to use your version of move_base in place of the standard system package, make sure your home-dir is listed in $ROS_PACKAGE_PATH before the default system path.