Turtlebot Explore - Gmappings

edit

Hi All.

I'm trying to make the explore node to work with my turtlebot.

Im working with Groovy version of ROS.

My structure configuration is

Groovy running over Ubuntu 12.04 running over VMWare running over MacOs mountain lion. Groovy running over Ubuntu 12.04 running over TurtleBot's asus. Wifi connection

The experiment consist in, launch gmapping_demo.launch, from the turtlebot_navigation stack, in the turtlebot side

 <launch>
  <include file="$(find turtlebot_bringup)/launch/3dsensor.launch">
    <arg name="rgb_processing" value="false" />
    <arg name="depth_registration" value="false" />
    <arg name="depth_processing" value="false" />
  </include>

  <include file="$(find turtlebot_navigation)/launch/includes/_gmapping.launch"/>

  <include file="$(find turtlebot_navigation)/launch/includes/_move_base.launch"/>

</launch>

Then i move the robot a bit in an open room to let gmappings to have some data. I launch the explore.xml from the explore_stage package in order to have the explore functionalities.

<launch>
  <node pkg="explore" type="explore" respawn="false" name="explore" output="screen" >
    <rosparam file="$(find explore_stage)/config/costmap_common.yaml" command="load" ns="explore_costmap" />
    <rosparam file="$(find explore_stage)/explore/explore_costmap.yaml" command="load" />
    <remap from="base_scan" to="scan"/>
    <param name="potential_scale" value="0.005"/>
    <param name="orientation_scale" value="0.0"/>
    <param name="gain_scale" value="1.0"/>
    <param name="close_loops" value="true"/>
  </node>
</launch>

I also spawn by hand the RViz in order to watch whats happening.

With all this setted up, the robot just 3 time moved alone, but i made this same experiment more than 10 times.

I start to analyze the command velocity topic, which is always in silence and the /move_base/goal, which stranglely it have a lot of traffic.

Taking in count the markers exposed by explore and the goals sent by explore node, and the fact that rxgraph shows me that move_base and explore are connected throught this last topic, the only thing that i can realize is that move_base is not responding to the goals asked.

I tryed with the RViz fingering a pose and it works.

In all the instances of my experiment, the only error that i get is, sometimes (no more than 3 times in a running of 10mins) an error calculating the transformation between /odom and /map or /odom and /base_link.

Just as general knowledge, i remap the base_scan topic to scan in order to keep the consistence in between configurations.

If someone have any idea, is really welcome.

The rosgraph output is

Nodes:
  /diagnostic_aggregator :
    Inbound:
      /mobile_base_nodelet_manager
      /turtlebot_laptop_battery
    Outbound:
      /rosout
  /cmd_vel_mux :
    Inbound:
      /cmd_vel_mux
      /mobile_base_nodelet_manager
      /mobile_base
      /bumper2pointcloud
      /navigation_velocity_smoother
    Outbound:
      /rosout
      /mobile_base_nodelet_manager
      /mobile_base
      /bumper2pointcloud
      /navigation_velocity_smoother
      /cmd_vel_mux
  /rxconsole_1370012301962201595 :
    Inbound:
    Outbound:
      /rosout
  /explore :
    Inbound:
      /move_base
      /robot_state_publisher
      /mobile_base_nodelet_manager
      /robot_pose_ekf
      /slam_gmapping
      /camera/camera_nodelet_manager
      /move_base
      /move_base
    Outbound:
      /rviz_1370012116847082561
      /move_base
      /rosout
      /rviz_1370012116847082561
      /rviz_1370012116847082561
      /move_base
  /navigation_velocity_smoother :
    Inbound:
      /navigation_velocity_smoother
      /mobile_base_nodelet_manager
      /mobile_base
      /cmd_vel_mux
      /bumper2pointcloud
    Outbound:
      /mobile_base_nodelet_manager
      /mobile_base
      /bumper2pointcloud
      /navigation_velocity_smoother
      /cmd_vel_mux
      /rosout
  /bumper2pointcloud :
    Inbound:
      /bumper2pointcloud
      /mobile_base_nodelet_manager
      /mobile_base
      /cmd_vel_mux
      /navigation_velocity_smoother
    Outbound:
      /rosout
      /mobile_base_nodelet_manager
      /mobile_base
      /bumper2pointcloud
      /navigation_velocity_smoother
      /cmd_vel_mux
  /master_sync_turtlebot_0196_3193_1407679111 :
    Inbound:
    Outbound:
  /slam_gmapping :
    Inbound:
      /camera/camera_nodelet_manager
      /slam_gmapping
      /robot_state_publisher
      /robot_pose_ekf
      /mobile_base_nodelet_manager
    Outbound:
      /rosout
      /rviz_1370012116847082561
      /robot_pose_ekf
      /move_base
      /slam_gmapping
      /explore
      /rviz_1370012116847082561
      /move_base
  /mobile_base :
    Inbound:
      /mobile_base
      /mobile_base_nodelet_manager
      /cmd_vel_mux
      /bumper2pointcloud
      /navigation_velocity_smoother
    Outbound:
      /mobile_base_nodelet_manager
      /mobile_base
      /bumper2pointcloud
      /navigation_velocity_smoother
      /cmd_vel_mux
      /rosout ...