Skip to content
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

Open
jbohren opened this issue Oct 20, 2014 · 3 comments
Open

Add resource enforcing to conman_ros #17

jbohren opened this issue Oct 20, 2014 · 3 comments

Comments

@jbohren
Copy link
Owner

jbohren commented Oct 20, 2014

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.

@adolfo-rt
Copy link
Collaborator

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.

@konradb3
Copy link
Collaborator

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.

@adolfo-rt
Copy link
Collaborator

The idea is to provide mechanism that ensure that there is at leas one component writing data to port.

Yes, and also that there are not too many, where applicable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants