Skip to content

Event

LiteGrip Python v1.0.0 released, set_force removed due to safety issue

1 reports · 1 sources

nexform-tech released litegrip-python v1.0.0, removing LiteGrip.set_force from the public API as a breaking change, stating that the method cannot determine whether the gripper is holding an object: when called on an empty gripper, it rushes toward the mechanical limit at a maximum of 692 mm/s and 0.25 Nm, exceeding the calibrated closed-side limit by 7.19 mm, with a measured peak force of 25.2 N while the set value was only 5 N. The alternative is grasp(force_n, hold_s), which first closes onto the object before applying force, and is currently the only path that continuously outputs feedforward torque frames.

Report timeline

  1. LiteGrip Python SDK v1.0.0 released, removes set_force public API

    nexform-tech's litegrip-python released v1.0.0, a breaking change: LiteGrip.set_force is removed. On an empty gripper, the method drove toward the mechanical stop at up to 692 mm/s and 0.25 Nm, exceeding the closed-side calibrated limit by 7.19 mm, with a measured peak force of 25.2 N (setpoint 5 N).

    GitHub Robotics Topic ·

Related topics