robot arm has a joint_states topic and as well as our platform too. Currently this is conflicting with the kinematics calculation. The work around that we are following is to append a namespace to our platform.
This solution is not ideal, since the visualization of the omndrivemodule in RViz gets affected, as the robot state publisher expects every states of the joints to be published to /joint_states.
robot arm has a joint_states topic and as well as our platform too. Currently this is conflicting with the kinematics calculation. The work around that we are following is to append a namespace to our platform.
This solution is not ideal, since the visualization of the omndrivemodule in RViz gets affected, as the robot state publisher expects every states of the joints to be published to /joint_states.
Related to: https://github.com/neobotix/neo_mpo_700-2/issues/36