This repository has been archived by the owner on Jan 16, 2019. It is now read-only.
Activation modes for service /ur_driver/robot_enable #2
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.
This PR was implemented in collaboration with @v4hn.
A parameter require_activation is added to configure when the
robot_enable
service has to be called to activate the driver. Prior this was required after every launch and emergency or protective stop.There are three modes now as suggested by @Zagitta in his pull request:
Never is set as default value to maintain the default behaviour in indigo.
Setting Always/OnStartup as default would probably require modifying all launch files however.
Enabling Always/OnStartup can be done by passing require_activation to the
ur_common.launch
or by modifying corresponding launch files.