Skip to content

Fix Jaco gripper force/torque sensor readings - #821

Open
Battleplus wants to merge 1 commit into
ARISE-Initiative:masterfrom
Battleplus:fix/jaco-gripper-sensors
Open

Fix Jaco gripper force/torque sensor readings#821
Battleplus wants to merge 1 commit into
ARISE-Initiative:masterfrom
Battleplus:fix/jaco-gripper-sensors

Conversation

@Battleplus

Copy link
Copy Markdown

Summary

  • move the Jaco gripper force/torque site from the fixed palm child to the right_gripper mounting body
  • preserve the site's original world-frame orientation with an explicit quaternion
  • add a MuJoCo regression test for the sensor attachment and bounded finite readings

Why this placement

Attaching the sensors to grip_site makes the default readings zero, but that site belongs to a massless visualization-only eef body and does not measure the complete finger subtree. Moving the existing ft_frame one level up measures the complete gripper at its mounting interface while preserving its pose.

With MuJoCo 3.8.0 after mj_resetData + mj_forward:

Sensor Before After
force_ee max abs 3.47e17 0.25
torque_ee max abs 3.42e15 0.141

Testing

  • python -m pytest tests/test_grippers/test_jaco_sensors.py -q (1 passed)
  • black --check tests/test_grippers/test_jaco_sensors.py
  • git diff --check

Fixes #808

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug Report] jaco_three_finger_gripper.xml produces extreme force_ee / torque_ee readings in the default initial state

1 participant