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

Service server for unlocking the protective stop #99

Closed

Conversation

xqms
Copy link

@xqms xqms commented Mar 22, 2017

The universal dashboard (port 29999) is used to unlock the protective stop. This is useful for e.g. automatic recovery behaviours that re-enable the robot and return to a safe pose.

We also add a distinction in the trajectory abort error string whether the abort is due to a protective stop or an emergency stop.

The universal dashboard (port 29999) is used to unlock the protective
stop.

This also adds a distinction in the trajectory abort error string whether
the abort is due to a protective stop or an emergency stop.
@gavanderhoorn
Copy link
Member

Late, but still: thanks for taking the time to implement this and submit it as a PR @xqms 👍

I'm going to close this though as we've officially deprecated this package. Refer to the announcement on ROS Discourse.

Note that the new ur_robot_driver includes full support for the Dashboard server and offers a ROS API for resetting faults, starting, stopping and resuming programs and more.

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

Successfully merging this pull request may close these issues.

2 participants