ROS Parameter for service call timeout for ros_control controllers (backport #3419) #3432
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Added a new ROS parameter controller_service_call_timeout for the ROS control interface managers, which can be specified in the moveit_controller yaml configuration file. I have tested it out using the https://github.com/moveit/moveit_resources/tree/ros2/dual_arm_panda_moveit_config example moveit configuration by trying out the following values for the parameter in the
moveit_controllers.yaml
:controller_service_call_timeout: 0.00001
: Controllers did not connectcontroller_service_call_timeout: 1.0
: Controllers connected and path planning could be executedCloses issue #3405
Checklist
This is an automatic backport of pull request #3419 done by [Mergify](https://mergify.com).