-
Notifications
You must be signed in to change notification settings - Fork 64
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
state[MOTION_HOLD] rejected event[eConfigDesiredForce] #201
Comments
Hello @buswayne, For a detailed analysis, would it be possible for you to share the script code used and the error log content that occurred? Thank you |
It remains stuck on set_desired_force command. We (poorly) "fixed it" with the following piece of code that monitors the log_alarm and if it is of the type 1903 (the one we get when the robot is stuck) resets the compliance control. Of course, this is not good practice and if there is a better way please let me know.
Here instead the function calling the force control
Thanks |
Using ROS, I often get this error while the robot is moving fast and I immediately a compliance control task begins.
The robot basically remains stuck in the position before the set_desired_force is performed.
Any suggestion?
Thanks
The text was updated successfully, but these errors were encountered: