Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to detect gripper collision #439

Open
EstanislauFilho opened this issue May 12, 2024 · 1 comment
Open

Failed to detect gripper collision #439

EstanislauFilho opened this issue May 12, 2024 · 1 comment

Comments

@EstanislauFilho
Copy link

EstanislauFilho commented May 12, 2024

I am using a Kinova Gen3 manipulator and need to know when the gripper has collided with a specific obstacle.

As can be seen in the first image below, the instruction iscollision = robot.iscollided(robot.q, obstacle) is commented out because it returns an error in most executions. When investigating the source code, I encountered the error present in the terminal in the second image. After adding the ".dae" extension in the code, I encountered the following error:
File "/home/xxx/anaconda3/envs/xxx/lib/python3.10/site-packages/spatialgeometry/geom/CollisionShape.py", line 200, in _init_pob
col = p.createCollisionShape( # type: ignore
pybullet.error: createCollisionShape failed.

Screenshot from 2024-05-11 21-39-43

Screenshot from 2024-05-16 10-44-09

Is there a practical solution to solve this problem?

@EstanislauFilho EstanislauFilho changed the title Is it possible to detect when a Gripper collides with an obstacle? Failed to detect gripper collision May 20, 2024
@TJMolnar
Copy link

TJMolnar commented May 21, 2024

I am also having this issue with the Kinova and I have narrowed it down to a limitation in the spatialgeometry package used by this toolbox, which itself relies on pybullet to handle collision meshes from the URDF. Kinova provides Collada (.dae) mesh files for their Gen3 arm, but pybullet does not seem to support them in this context. Indeed the spatialgeometry library is explicitly only loading STL files, and so is actually ignoring these meshes entirely. Collada/.dae files are a very common format for meshes in URDF's and are (as in this case) often provided in official packages from manufacturers, so this places a significant limitation on the usage of this toolbox.

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

No branches or pull requests

2 participants