You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
in the [edo] branch you can find the integration of the inverse dynamics solver OpenSotAcc with the Cartesian Interface. Tested on fixed base robots, there are some issues with the velocity limits (added in the constraints of the stack.yaml file). In this case, the solver seems to not to converge, while removing them seems to improve the convergence. Moreover, it is needed to fix the lambda values, that are not consistent with the kinematic version of the solver and to add the lambda_1 and lambda_2 variables.
The text was updated successfully, but these errors were encountered:
For what concern issue 2: the lambda in the velocity level control is independent from the control rate, while te one of the acceleration is dependent. I suppose that to make the second one independent and equivalent we should divide the value by dt^2 (and for lambda2 by dt).
The values of lambda1 and lambda2 are now set correctly but in the stack file we read lambda that is consistent with the kinematic version of the solver. In a future update we wil be able to set them directly in the stack file.
Hi,
in the [edo] branch you can find the integration of the inverse dynamics solver OpenSotAcc with the Cartesian Interface. Tested on fixed base robots, there are some issues with the velocity limits (added in the constraints of the stack.yaml file). In this case, the solver seems to not to converge, while removing them seems to improve the convergence. Moreover, it is needed to fix the lambda values, that are not consistent with the kinematic version of the solver and to add the lambda_1 and lambda_2 variables.
The text was updated successfully, but these errors were encountered: