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
I noticed that calling the grasp command twice in a row results in the routine waiting for a response for a while and eventually leads to an exception being thrown. Although grasping twice is redundant and not the most common use case. I do think it should not lead to an exception and definitely not to the waiting behavior observed. (Why not simply returning true?).
I'm actually using the gripper through its Action Server in franka_ros and already hacked a check whether the gripper isn't already closed. But since the behavior is also observed in libfranka, I opted to report the issue here. Find an MWE below.
Minimum working example
The code in the bottom of the issue (modification of examples/grasp_object.cpp) demonstrates the reported behavior.
The program will open the gripper with the following command:
./a.out <robot-ip> 1
To close the gripper one can run:
./a.out <robot-ip> 0
The following sequence of commands works as expected:
I noticed that calling the grasp command twice in a row results in the routine waiting for a response for a while and eventually leads to an exception being thrown. Although grasping twice is redundant and not the most common use case. I do think it should not lead to an exception and definitely not to the waiting behavior observed. (Why not simply returning
true
?).I'm actually using the gripper through its Action Server in
franka_ros
and already hacked a check whether the gripper isn't already closed. But since the behavior is also observed inlibfranka
, I opted to report the issue here. Find an MWE below.Minimum working example
The code in the bottom of the issue (modification of
examples/grasp_object.cpp
) demonstrates the reported behavior.The program will open the gripper with the following command:
To close the gripper one can run:
The following sequence of commands works as expected:
However, if we grasp the object twice in a row, e.g. like so:
the program will first hang for a while and then crash with the following error message
I did not run a debugger, but I guess it first gets stuck here and then times out after a while.
code:
The text was updated successfully, but these errors were encountered: