-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add resource enforcing to conman_ros #17
Comments
Would this mechanism allow to encode behaviors such as exclusivity or allowing concurrence depending on conditions?. Example: Disallow write access to a position command from two sources, but allow multiple writers to an effort command. |
I think that is possible. As it's configured on per port basis. Your example is already possible using only exclusivity mechanism. We can configure "position command" input port to be exclusive and "effort command" input port to be not exclusive. The idea is to provide mechanism that ensure that there is at leas one component writing data to port. For example we want to ensure that when position controller is active there is also at least one component providing commanded position active. |
Yes, and also that there are not too many, where applicable. |
Add an option to the actionlib actions so that they can be long-running. In this way, they will claim "ownership" of a set of blocks until the action is cancelled. Enforce this in the conman_ros action server.
The text was updated successfully, but these errors were encountered: