Why use joint_state_publisher?
Hi all,
I was looking through the documentation for the joint_state_publisher package. I can see the use case for wanting so publish and set joint states via the GUI, but what is the purpose of having the node subscribe to incoming sensor_msgs/JointState
messages?
It seems to me that if you are working in hardware, there is no reason to do that. The node will just subscribe via:
source_list (list of strings, default: [])
A list of topics to listen on for sensor_msgs/JointState messages.
and spit them back out again.
Does anybody have any insights on this? Thanks.