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

Revision history [back]

click to hide/show revision 1
initial version

Figured out the solution is to add the kConfigDefault suffix to ALL the planner names in the ompl_planning.yaml file as described on this page. I only added it to the planners in the first section (planner_configs) before but not the list of planners under the planning group. Perhaps this could be made clearer somehow in the tutorial.

Figured out the solution is to add the kConfigDefault suffix to ALL the planner names in the ompl_planning.yaml file as described on this page. I only added it to the planners in the first section (planner_configs) before but not the list of planners under the planning group. Perhaps this could be made clearer somehow in the tutorial.

EDIT: IGNORE ABOVE! Just found out that I had been running a roscore hidden behind the many terminal windows which was the culprit. The launch file for the MoveIt config launches its own master so there probably is a conflict there. Just tested with the original ompl_planning.yaml file and it ran fine although still gave the error could not find the planner configuration 'None' on the param server but that is probably a non-issue.

click to hide/show revision 3
No.3 Revision

Figured out the solution is to add the kConfigDefault suffix to ALL the planner names in the ompl_planning.yaml file as described on this page. I only added it to the planners in the first section (planner_configs) before but not the list of planners under the planning group. Perhaps this could be made clearer somehow in the tutorial.

EDIT: IGNORE ABOVE! Just found out that I had been running a roscore hidden behind the many terminal windows which was the culprit. The launch file for the MoveIt config launches its own master so there probably is a conflict there. Just tested with the original ompl_planning.yaml file and it ran fine although still gave the error could not find the planner configuration 'None' on the param server but that is probably a non-issue.