Search the Community

Hello, In our lab we have the Baxter two finger gripper attached to a Sawyer. In the past couple of weeks , using the gripper_keyboard.py example in the intera_examples (from the intera_sdk ROS packages, https://github.com/RethinkRobotics/intera_sdk/blob/master/intera_examples/scripts/gripper_keyboard.py ) has been throwing the following error : "Calibration failed.". It is unclear why this has started happening after a couple of years of operation without issue. This is a problem because we then cannot use the gripper (The error happens in any script when instantiating the Gripper class in the intera python api for the first time : https://rethinkrobotics.github.io/intera_sdk_docs/5.1.0/intera_interface/html/index.html ). We noticed that running the gripper_keyboard.py over and over again generally results with it finally working after some time. Moreover, once it works, then it is not a problem again until the robot is rebooted. Any ideas what could be happening or how we could fix this? We are starting to suspect a hardware malfunction. Many thanks

Hi all, We have recently acquired 2 Sawyer robots and now we are starting in "playing" with them. We completed the setup using lunar distro and everything seemed to run good. In order to control the robot and close the loop using force or camera sensors, we wanted to know parameters such as control rate, positioning errors, joint resolution, behavior of these robots in open loop, etc. So the first thing we did was the calibration of both robots using the example script provided in the SDK We realized that one of the robots had a bias of the seventh axis of 0.1741 rad (is this normal?) Afterwards we proceeded to test the joint positioning errors and repetitivity, testing both set_joint_positions() and move_to_joint_positions() commands and using a force sensor of 6DoF, getting in both cases strange behaviors: 1) Sometimes some axes didn't updated their values whilest others did -> poritioning errors : if we integrate the joint values we get no repetitivity 2) The joint absolute error, computed as e=(cmd_sent-joint_values_cur)/(cmd_sent-joint_values_prev), runing at 100ms overcomes the 80%, starting to have a good behavior (not allways) when the period is 2s up So, we think there is somthing we are not setting correctly or perhaps the commanding functions used are not correct. Do you have any idea of what we are doing wrong? Do you have any test program in order to see if the robot behaves as it should? Thanks in advance for your help!! PS: we update the comands each Periode using the sleep function in our control loop. The rest of the setup is similar to the one provided in joint_position_keyboard.py example provided in the SDK