TheMoveUntilTouch**Topic**Controller is basically the same as the MoveUntilTouchController, but instead of Hardware Interfaces it uses ROS topics and action clients to communicate with the Force/Torque sensor.
I'm not sure if copying the class is ok here. My feeling was that if we and up creating more MoveUntilTouch-like controllers, we need to clean it up (create something like a base class for those controllers). But I thought if we only need the one additional controller, copying the code one time might be ok.
Additionally, there is a small change in JointTrajectoryControllerBase: We need to choose the type of control (position, velocity, effort) via rosparams.
The
MoveUntilTouch**Topic**Controller
is basically the same as theMoveUntilTouchController
, but instead of Hardware Interfaces it uses ROS topics and action clients to communicate with the Force/Torque sensor.I'm not sure if copying the class is ok here. My feeling was that if we and up creating more MoveUntilTouch-like controllers, we need to clean it up (create something like a base class for those controllers). But I thought if we only need the one additional controller, copying the code one time might be ok.
Additionally, there is a small change in
JointTrajectoryControllerBase
: We need to choose the type of control (position, velocity, effort) via rosparams.