-
Notifications
You must be signed in to change notification settings - Fork 408
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
isolate / release controller_stopper #523
Comments
Indeed that it was the plan initially to make it also available for others, hence the standalone package. Back then I didn't anticipate that getting a binary release would take such a long time. I'd still like to push that forward rather than investing time splitting this single package, but I definitively understand your concerns. However, please note that we are currently very busy making the first ROS2 binary release and after that, some focus will definitively go into updating ros-industrial/universal_robot and therefore moving towards a binary release for this repo. |
This issue has not been updated for a long time. If no further updates are added, this will be closed automatically. Comment on the issue to prevent automatic closing. |
I'm not at all happy with the solution to move it even further into ur_robot_driver instead of splitting it up, but apparently someone vetoed the package name... I'll close this as "No Fix" for now. |
The controller_stopper package is useful standalone, also if no UR arms are involved.
shadow-robot, possibly among others use the package with their own ros_control-powered hardware and we actually forked this repository just to get this small helper node without pulling in UR.
It would be great if you could either (1) split the package into a small separate repository or (2) release it into ROS noetic, so we don't have to compile it ourselves.
The text was updated successfully, but these errors were encountered: