Closed PeterBowman closed 6 years ago
Just a mere reachability issue solved at fae5678. Works fine with x = 1.09
(instead of 1.1
). Perhaps a previous, apparently successful movl
call fooled me to think that the robot actually reached that position, but I never checked the decimals. Idea: check final pose before finalizing a movl
sequence?
Comment: singularities will be tracked at #109.
The following cosine (
ct2
) inAsibotSolver::invKin
may return values larger than1.0
, leading to aNaN
inst2
and propagating to subsequent operations:https://github.com/roboticslab-uc3m/kinematics-dynamics/blob/5913c9f4e02ad52ed6f6095a40e929d89adf533f/libraries/YarpPlugins/AsibotSolver/ICartesianSolverImpl.cpp#L175-L176
Steps to reproduce this (on simulation):
0.45 0.0 0.8 0.0 1.55 0.0
movj 0.45 0.0 1.1 0.0 1.55 0.0