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

Refactor code to conform to ros_control interface #17

Open
hc825b opened this issue Sep 8, 2019 · 0 comments
Open

Refactor code to conform to ros_control interface #17

hc825b opened this issue Sep 8, 2019 · 0 comments
Labels
question Further information is requested

Comments

@hc825b
Copy link
Member

hc825b commented Sep 8, 2019

ROS and Gazebo already follow the ros_control to define interfaces (ROS topics) for both simulated and real hardware. Our current framework however use hard-coded ROS topic names for communication between middle-ware and hardware specific controllers.

http://gazebosim.org/tutorials/?tut=ros_control
http://wiki.ros.org/ros_control

A major drawback/difficulty may be that low level controllers have to be re-implemented with the ros_control interfaces in C++ instead of Python.

@hc825b hc825b added the question Further information is requested label Sep 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant