You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PR2 have topics to get joint trajectory controller state such as /l_arm_controller/state... The message type is pr2_controllers_msgs/JointTrajectoryControllerState.
joint_trajectory_controller in ros_controllers package also publishes joint trajectory controller state as <controller_name>/state The message type is control_msgs/JointTrajectoryControllerState.
These two messages are the same.
But on Baxter, /baxter_joint_trajectory doesn't publish joint trajectory controller state, I think. /robot/limb/right/state and /robot/limb/left/state exist, but these topics are totally different from topics above.
$ rostopic info /robot/limb/right/state
Type: baxter_core_msgs/AssemblyState
We should add JointTrajectoryControllerState message topic, shouldn't we?
The text was updated successfully, but these errors were encountered:
PR2 have topics to get joint trajectory controller state such as
/l_arm_controller/state... The message type is pr2_controllers_msgs/JointTrajectoryControllerState.joint_trajectory_controller in ros_controllers package also publishes joint trajectory controller state as
<controller_name>/stateThe message type is control_msgs/JointTrajectoryControllerState.These two messages are the same.
But on Baxter,
/baxter_joint_trajectorydoesn't publish joint trajectory controller state, I think./robot/limb/right/stateand/robot/limb/left/stateexist, but these topics are totally different from topics above.We should add JointTrajectoryControllerState message topic, shouldn't we?
The text was updated successfully, but these errors were encountered: