ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | Q&A answers.ros.org |
![]() | 1 | initial version |
Solved it, it was just a datatype conflict. The AMCL node was printing this: Client [/subscriber] wants topic /amcl_pose to have datatype/md5sum [geometry_msgs/PoseWithCovariance], but our version has [geometry_msgs/PoseWithCovarianceStamped]. Dropping connection.