We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The workspace bounds seem to be too conservative. For instance, the servos are shutdown when the robot reaches the following configuration:
name: [A, B, X, Y, Z] position: [1.3222773798393699, 1.8888698029010453, 1.3708573214955608, 0.35025446199240723, 0.07218281246152418]
Overall, we may want to consider not doing this hard shutdown in this API and instead let the ROS-level controller deal with this.
This is related to issue #1.
The text was updated successfully, but these errors were encountered:
Also, the workspace bounds outside of the shelf are too restrictive and prevent the robot from accessing RC1 and RC4
Sorry, something went wrong.
No branches or pull requests
The workspace bounds seem to be too conservative. For instance, the servos are shutdown when the robot reaches the following configuration:
Overall, we may want to consider not doing this hard shutdown in this API and instead let the ROS-level controller deal with this.
This is related to issue #1.
The text was updated successfully, but these errors were encountered: