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
Understanding ErrorExecutionTimeCalculation (-110) errors #19
Comments
Hi @isherman, this is an internal error of Ruckig. Can you share your InputParameter for a typical failing case? |
By the way, you can print the current input parameters (and let ruckig throw on errors) by using |
Great tip, thanks!
|
My issue #20 seems to be related to this. Here is my runtime_error:
|
The latest commit on the master branch should fix some errors (due to numerical issues), but it still needs more automated testing... |
In my particular case, I don't have the error anymore with the latest commit. I will keep you updated if I run into anything similar again. |
Thanks for the help @pantor. I am still getting similar errors at 1b06ce4:
|
I don't know if it's still useful for you to get as many runtime_error logs as possible. I don't want to be spamming here.. In any case, I ran into this one today:
|
With the latest commits, the situation due to numerical issues should improve. It is not perfect yet, so please report if you encounter any errors. |
With the latest changes I've been running all day without a -110 error. |
I'm using Ruckig in a 6-DOF visual servoing application, updating
input.target_position
at a rate similar to the control cycle.I find that often when setpoints (updates to
target_position
) are quite close to each other, Ruckig will return a-110
status. Can you help me understand what causes this error? Are there any workarounds you'd suggest? Thank you.The text was updated successfully, but these errors were encountered: