ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
0

Multiple joint state publishers, unable to fetch current robot state

asked 2023-05-27 19:07:02 -0500

ThreeForElvenKings gravatar image

Hello, I'm working with a physical robot (Fetch robot) for motion planning related tasks. I start the move_group, and then try to plan a path between the start state and a goal state. However, when trying to plan, I get a warning saying that it "failed fetch current robot state". Upon further investigation, I notice that the robot is publishing to the /joint_states topic via two publishers: the /robot_driver and /gripper_driver. The /robot_driver publishes all joints except the l_gripper_joint and r_gripper_joint, which is published by the /gripper_driver.

I'm guessing that the move_group planning (and execution) failed due to this reason, that it can never get the complete joint state in any message.

Would also love to have other places where there may be issues (i.e. if the /joint_state may not be the issue). Thanks

Since I cannot internally change the ros interface of the robot, how do I fix this issue? Any help would be appreciated.

Thanks

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2023-05-28 10:41:04 -0500

Mike Scheutzow gravatar image

I think your guess is a good one. I have programmed multiple arms, and all the joint values are always reported in a single message.

You could create a simple node that combines the two joint_state messages into one, and publish that as /joint_states. You will need to remap the driver publish topic names in the launch file.

edit flag offensive delete link more

Question Tools

2 followers

Stats

Asked: 2023-05-27 19:07:02 -0500

Seen: 321 times

Last updated: May 28 '23