-
Notifications
You must be signed in to change notification settings - Fork 57
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
[cob_collision_monitor] Investigate collision models #89
Comments
I think the ipa320/cob_robots#482 is a result of de SRDF being empty. However, we should check URDF for "hidden" collisions and missing collision models. |
cross-referencing another collision_monitor-related issue: ipa320/cob_gazebo_plugins#16 |
After fixing the mesh and updating the moveit_configs the collision_monitor can be used in cob_bringup again... |
mesh is fixed in https://github.com/ipa320/cob_common/pull/205 then testing on hw... |
Apparently, with the current robot model, i.e. the collision model and meshes, as well as the current configuration of the collision matrix in the SRDF, the collision_monitor reports
state_is_valid=false
as reported here.This needs further investigation before re-activating the node within bringup.
Possible reasons might be:
wrong computation of collision matrix using moveit_setup_assistant (random, 95%) -> run several times and unifyrunning it several times for cob4-1 always resulted in the samedisable_collisions
pairs@fmessmer FYI
The text was updated successfully, but these errors were encountered: