Client [/mir_auto_bagger] wants topic /move_base/goal to have datatype/md5sum
When I try to do a gmapping with my mobile robot an error pop-up:
[ERROR] [1554797108.240628800]: Client [/mir_auto_bagger] wants topic /move_base/goal to have datatype/md5sum [*/8ac6f5411618f50134619b87e4244699], but our version has [move_base_msgs/MoveBaseActionGoal/660d6895a1b9a16dce51fbdd9a64a56b]. Dropping connection.
[move_base_node-2] process has died [pid 6194, exit code -6, cmd /opt/ros/kinetic/lib/move_base/move_base cmd_vel:=mobile_base/commands/velocity __name:=move_base_node __log:=/home/chbloca/.ros/log/ed0463be-5a97-11e9-93e4-94c6911e7b24/move_base_node-2.log]. log file: /home/chbloca/.ros/log/ed0463be-5a97-11e9-93e4-94c6911e7b24/move_base_node-2*.log
What library should I modify in order to make the PC messages to be compatible with the mobile robot? PD: I cannot access to the mobile robot PC
This seems like a cross-post of dfki-ric/mir_robot#20?
It is, indeed
What has changed since you opened that issue?
Nothing at all. No solutions yet
I believe @Martin Günther's answer on your
mir_robot
issue was pretty OK: either use a ROS version that corresponds to what the robot runs, or use his driver to not work with messages directly.Alternatively you could see whether using the same
move_base
messages on your PC would work, but it's likely thatmove_base
on your own PC will not work with the messages that your robot uses.So do you mean that my robot is running under Indigo ROS? Because the ROS in my computer is Kinetic. I cannot use his bridge since it is not suitable for heavy topics such as the ones that the camera produces.
If your robot is running Indigo, then yes, using a client PC running Indigo (or a Docker image) should work.
@gvdhoorn - good catch on finding that GitHub issue, I wouldn't have seen this question if you hadn't mentioned me. Out of curiosity - do you monitor all of GitHub? :D