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

Should we add enable/relax services to the Controller class? #26

Closed
corot opened this issue Sep 11, 2014 · 4 comments
Closed

Should we add enable/relax services to the Controller class? #26

corot opened this issue Sep 11, 2014 · 4 comments

Comments

@corot
Copy link
Contributor

corot commented Sep 11, 2014

So user don't need to call the service on any sevo. It's just a suggestion; maybe is too dynamixel-specific stuff to put here. For example, @pirobot has implemented the same in his own stack.

@mikeferguson
Copy link
Member

I'm not sure what you mean exactly, could elaborate a bit on the use case?

@corot
Copy link
Contributor Author

corot commented Sep 12, 2014

Sorry. I mean that, if I have, for example, the controllers to operate a trutlebot arm (gripper controller + follower controller), I will have 5 enable, 5 relax services, etc. one per joint. But it would also be good to have a single relax, a single enable, etc. service for the 4 joints in the arm controller.

@mikeferguson
Copy link
Member

That seems pretty reasonable, I don't have time to implement, but a pull request is certainly welcome.

corot added a commit to corot/arbotix_ros that referenced this issue Feb 12, 2016
…rvoController

class, so you don't need to call service on each servo
mikeferguson added a commit that referenced this issue Mar 6, 2016
Issue #26 implementation: enable/relax services on ServoController class
@corot
Copy link
Contributor Author

corot commented Mar 6, 2016

Implemented here d87874b

@corot corot closed this as completed Mar 6, 2016
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

2 participants