Migrate User Workspaces to MoveIt Pro 11.0
Remove Legacy Planning Interface Dependencies
MoveIt Pro 11.0 removes the moveit_pro_base_planning_interface C++ library and the headers under moveit_pro_base/planning_interface/. These define the legacy PlannerManager, PlanningContext, PlanningRequestAdapter, PlanningResponseAdapter, and planning response types. Remove includes of those headers and links to moveit_pro_base::moveit_pro_base_planning_interface from your CMake targets. Custom code implementing or using these interfaces must be ported to the current planning APIs; there is no drop-in replacement for the removed framework.
The Python module moveit_pro_base.core.planning_interface, including its MotionPlanResponse class, is also removed. Remove imports from this module and update code that uses the class. The top-level moveit_pro_base.planning_interface re-export is removed as well.
Remove the moveit_pro_configs_utils Package
MoveIt Pro 11.0 removes the moveit_pro_configs_utils package. The MoveIt Pro Runtime loads robot configuration packages through its own configuration parsing and never used this package; it only provided launch-file helpers for loading MoveIt parameters from a *_moveit_config package laid out by the MoveIt Setup Assistant.
ros-jazzy-moveit-pro-configs-utils is no longer published, and its rosdep key is gone as well, so a workspace that still names the package fails when resolving dependencies rather than at build time:
Cannot locate rosdep definition for [moveit_pro_configs_utils]
Remove the dependency from any package.xml that declares it:
<!-- Remove this line -->
<depend>moveit_pro_configs_utils</depend>
Everything the package exported is removed with no drop-in replacement:
MoveItProConfigsBuilderand theMoveItProConfigsdataclass it returned.- The launch generators in
moveit_pro_configs_utils.launches:generate_rsp_launch,generate_moveit_rviz_launch,generate_static_virtual_joint_tfs_launch, andgenerate_spawn_controllers_launch. - The launch helpers in
moveit_pro_configs_utils.launch_utils:DeclareBooleanLaunchArgandadd_debuggable_node. - The
Xacrosubstitution inmoveit_pro_configs_utils.substitutions. Uselaunch_ros.parameter_descriptions.ParameterValuewith thexacrocommand, orlaunch_param_builder.load_xacro, instead.
Launch files that used the builder to load parameters should load the files directly with launch_param_builder, which is available from the ROS distribution. Add <depend>launch_param_builder</depend> to the package.xml and replace the builder call with explicit parameter dictionaries:
# Before
from moveit_pro_configs_utils import MoveItProConfigsBuilder
moveit_config = (
MoveItProConfigsBuilder("my_robot")
.robot_description(file_path="config/my_robot.urdf.xacro")
.to_moveit_pro_configs()
)
parameters = [moveit_config.to_dict()]
# After
from pathlib import Path
from ament_index_python.packages import get_package_share_directory
from launch_param_builder import load_xacro, load_yaml
config_dir = Path(get_package_share_directory("my_robot_moveit_config")) / "config"
parameters = [
{
"robot_description": load_xacro(config_dir / "my_robot.urdf.xacro"),
"robot_description_semantic": load_xacro(config_dir / "my_robot.srdf.xacro"),
"robot_description_kinematics": load_yaml(config_dir / "kinematics.yaml"),
"robot_description_planning": load_yaml(config_dir / "joint_limits.yaml"),
}
]
Two details matter when translating a builder call by hand:
- The URDF and SRDF paths came from
.setup_assistant, not from a fixed naming convention. Read that file in your configuration package to find the paths your robot actually uses — the SRDF in particular is often a.srdf.xacrounder a different name than the robot. joint_limits.yamlloads under therobot_description_planningkey, as in the snippet above, not under a key named after the file.
The builder also loaded every parameter group it could find, whether or not the node read it: the planning pipelines, trajectory_execution and moveit_controller_manager, the publish_* planning-scene-monitor settings, sensors_3d, and the Pilz cartesian limits (merged into robot_description_planning). Loading files explicitly means naming only the groups your node needs, so add the ones it reads — a node that plans or executes trajectories needs the planning-pipeline and controller-manager parameters that a node which only monitors the planning scene can leave out.