Hardware interface for sending motion primitives to the robot via the Instruction Executor instead of trajectories

[mathias31415]

This PR extends the ur_robot_driver package with a hardware interface for sending motion primitives to the robot via the Instruction Executor instead of traditional trajectory execution.

To reuse the state interface functionalities of the original hardware interface in the new motion_primitive_ur_driver, these functionalities have been refactored into a shared helper file: stateinterface_helper.hpp.

The implementation uses the motion_primitives_forward_controller, which is planned to be integrated into the ros2_controllers repository. (ros-controls/ros2_controllers#1636)

Motion primitives are received by the controller using the MotionPrimitive.msg from the industrial_robot_motion_interfaces package. A modified version of this message is used here, which includes additional helper types:

• STOP_MOTION: Interrupts current robot motion and clears the motion queue.
• MOTION_SEQUENCE_START and MOTION_SEQUENCE_END: Define a sequence block—primitives between these markers are grouped and executed as a single, blended motion sequence. This enables smooth transitions between individual primitives, unlike executing them one by one.

This implementation also depends on a pending Pull Request in the Universal_Robots_Client_Library. This PR extends the Instruction Executor with support for movec commands, which is required for executing circular Cartesian motions within this driver.

I'd appreciate any feedback or suggestions – thanks in advance!

[mathias31415]

@urfeex I've now integrated the motion_primitives_ur_driver into the hardware_interface, which allows switching modes during operation. I'm happy to receive any feedback on this!

During the integration, I encountered the following issue:

Both the hardware_interface implementation and the InstructionExecutor (used to execute motion primitives) depend on a callback that is triggered when a trajectory is completed. In the current setup, the UR driver's callback function is overwritten, which means only one of these callbacks can be active at any given time.

To solve this, I register the InstructionExecutor's callback when motion primitives mode is activated, and restore the hardware_interface's callback when the mode is deactivated. To enable this mechanism, I added a method registerTrajDoneCallback() to the InstructionExecutor in the ur_client_library:

void urcl::InstructionExecutor::registerTrajDoneCallback()
{
  driver_->registerTrajectoryDoneCallback(
      std::bind(&InstructionExecutor::trajDoneCallback, this, std::placeholders::_1));
}

Let me know if you have any suggestions for a cleaner solution.

[mathias31415]

And one more question: I’ve documented everything a bit in README_MotionPrimitive.md. Should I integrate that into README.md? Or put it somewhere else? Or should I just leave it as it is?