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

Velocity Position Controller #131

Closed
davetcoleman opened this issue Oct 8, 2014 · 7 comments
Closed

Velocity Position Controller #131

davetcoleman opened this issue Oct 8, 2014 · 7 comments

Comments

@davetcoleman
Copy link
Member

Greetings,

I've fallen behind in tracking the recent changes to ros_controllers, particularly a velocity-position-controller. My original attempt at implementing one last year is very out of date. I'm trying to re-vamp the Baxter controllers that I created all of this for. Here is what I've gleemed just now from lost of Github discussions:

It seems most of the original features were finally merged in:
#117
#116

Except this one:
#115

Which will be replaced by:
pal-robotics-forks#41

Question: can we get the joint_mode_controller merged soon?

@brawner In the meantime, I'm going to remove my branch velocity_position_controller since all these features have been replaced, and because, embarrassingly, I made a bad commit to it. I have replaced it with a hydro-only version: https://github.com/ros-controls/ros_controllers/tree/hydro-velocity-pos-controller

davetcoleman referenced this issue in brawner/ros_controllers Oct 8, 2014
@adolfo-rt
Copy link
Member

A proposal for a joint mode interface and controller will be presented for review once validation is complete. The proposal is based on your original PR, but has been extended to take into account additional concerns that were raised during the PR discussion.

@Karsten1987
Copy link
Contributor

Is there any update on this?
Ended up here by following this ros_control tutorial.
Thus the doc seems to be outdated.

@adolfo-rt
Copy link
Member

What exactly are you looking for?. This issue is a bit out of date, and talks about more than one thing. With luck, what you need has already been merged.

@Karsten1987
Copy link
Contributor

I was looking for the joint_mode_interface. I am on indigo and got the impression it's not available.
Can you confirm that? Again, I am simply following the tutorials, thus I might be doing something wrong.

@adolfo-rt
Copy link
Member

It is available. It was merged in ros-controls/ros_control#200, indigo-devel. There is no need for a hardware interface or a controller. You add support for mode switching to your robot by specializing the canSwitch and doSwitch methods of RobotHW. At runtime, you simply call the switch_controllers service, and any switching that might be required is taken care of by your robot hardware abstraction.

Important note: There is a bug in the implementation, which is being discussed in ros-controls/ros_control#211.

@davetcoleman, do you mind if we remove the misleading tutorial?.

@davetcoleman
Copy link
Member Author

No problem - that tutorial was originally copy-pasted from Sachin's Github wiki version, then I added more detail when I implemented the initial controller switching functionality (that was never merged in)

@toliver
Copy link

toliver commented Feb 16, 2016

I've just removed the outdated tutorial.

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

4 participants