ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
0

pilz industrial motion planner not using the updated allowed collision matrix

asked 2021-05-19 12:51:00 -0500

robertjbush gravatar image

updated 2021-05-20 02:12:13 -0500

My environment:

  • ROS Noetic in a docker container with Ubuntu 20.04
  • Moveit! version 1.1.2
  • ros-industrial-client with motoman driver

Problem:

  • Using MoveGroup commander (Python API) and Pilz Industrial Motion Planner, changes to the allowed collision matrix (ACM) are published to the planning scene but do not propagate to the planning interface.

Action taken so far:

  • Tested with an identical stack except with OMPL planner in the pipeline. Behaviour is not reproducible, changes propagate to the planning interface (perhaps through pre/post-processing plugins?).
  • Tested with planning directly in rviz. Behaviour is not reproducible, changes propagate to the planning interface.

Question:

  • Why does OMPL planner with MoveGroup Commander or planning directly in rviz with Pilz Industrial Motion Planner successfully use the updated planning scene yet the Pilz Industrial Motion Planner with MoveGroup Commander does not?
  • Is there an API call to force the MoveGroup Commander to fetch an updated planning scene?
edit retag flag offensive close merge delete

Comments

Which part specifically is the "ros-industrial stack"?

The Pilz planner is a MoveIt planner written by Pilz. MoveIt is MoveIt.

There doesn't appear to be anything ros-industrial here.

gvdhoorn gravatar image gvdhoorn  ( 2021-05-19 15:17:41 -0500 )edit

Question guidelines: "Names and versions of stacks/packages that you're using". If there should be boundaries to what the op includes in their question, then the guidelines need to be made clearer. I use ros-industrial-client and motoman stacks. I also consider pilz to be most relevant for industrial users.

robertjbush gravatar image robertjbush  ( 2021-05-19 15:38:14 -0500 )edit

I have been using the pilz planner while modifying the ACM, but have not encountered this bug. If you can reproduce it with a minimal example, please feel free post it on the Github issue tracker.

fvd gravatar image fvd  ( 2021-05-19 21:57:34 -0500 )edit

I use ros-industrial-client and motoman stacks.

that isn't mentioned anywhere in your question text. "ros-industrial stack" is not a well known bit of terminology. No one will know what you mean by that, so it does not add anything which would help understand your setup.

gvdhoorn gravatar image gvdhoorn  ( 2021-05-20 01:41:14 -0500 )edit

@fvd do you have a github repo where I could view working moveit config files and python scripts? Moved to github issue here.

robertjbush gravatar image robertjbush  ( 2021-05-20 02:13:35 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2021-09-06 02:04:44 -0500

robertjbush gravatar image

This issue has been fixed and merged into the master branch of MoveIt!. See GitHub issue for more info.

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2021-05-19 12:51:00 -0500

Seen: 254 times

Last updated: Sep 06 '21