Closed rsantos88 closed 6 years ago
Gripper limits as fetched by BCC via remote_controlboard are [0,0]
:
[info] DeviceDriverImpl.cpp:89 open(): Joint 0 limits: [-88.500000,98.100000]
[info] DeviceDriverImpl.cpp:89 open(): Joint 1 limits: [-75.500000,29.600000]
[info] DeviceDriverImpl.cpp:89 open(): Joint 2 limits: [-57.000000,80.100000]
[info] DeviceDriverImpl.cpp:89 open(): Joint 3 limits: [-32.900000,83.500000]
[info] DeviceDriverImpl.cpp:89 open(): Joint 4 limits: [-99.600000,76.800000]
[info] DeviceDriverImpl.cpp:89 open(): Joint 5 limits: [-56.900000,107.500000]
[info] DeviceDriverImpl.cpp:89 open(): Joint 6 limits: [0.000000,0.000000]
Per launchManipulation.ini, those should be [-1200,1200]
.
This is both a regression caused by https://github.com/roboticslab-uc3m/kinematics-dynamics/issues/161 and a silent bug buried somewhere in yarp-devices.
As a quick workaround, you could just set llim
via RPC and move away from the [0,0]
initial limit setup. I'm submitting a patch right now, though.
@rsantos88 please update yarp-devices onboard (https://github.com/roboticslab-uc3m/yarp-devices/commit/1632d72a7f6a2bf601dac52628226e4a1f319472) and try again.
Thanks @PeterBowman ! Now it works with the real robot :)
I've trying to check this app with the real robot, because in the simulator it works pretty well. Placing the robot in a safe position to initiate Cartesian control (elbow near 90º and front shoulder 10º), when I try to move it in Cartesian space using 'a'/'z' or 's'/'x' in the app, the Cartesian Control shows this errors:
The arm doesn't move. I'll copy the initialization of Cartesian Control if it was helpful: