6.5.2
Bug Fixes
- Fixed an issue where file conflicts could erroneously appear in the objective editor.
- Fixed an issue where behavior tree metadata such as categories could be accidentally discarded by the objective editor.
moveit_pro shell fails if no docker-compose.yaml exists in the user workspace.Pick AprilTag Labeled Object objective.The MoveIt Pro UI now provides a convenient interface for defining "keep-out zones" for regions you want to temporarily prevent your robot from planning motion into.
When using Nav2, the MoveIt Pro UI will now automatically display the occupancy grid in the visualization pane.
The MoveIt Pro UI now provides the ability to save and load MoveIt PlanningScenes to/from files. In conjunction with the keep-out zone feature, this can allow you to rapidly prototype a work area without adding environmental collision geometry to your URDF.
Launching pro with the mujoco_viewer in a config set to true will now launch both the MoveIt Pro UI and MuJoCo viewer in an interactive state. You can make changes to the MuJoCo simulation that are reflected in MoveIt Pro and vice versa.
lab_simThe new default MoveIt Pro workspace is the moveit_pro_example_ws, found here. The default config is now lab_sim, featuring a UR arm on a rail in a pharmaceutical environment. This workspace still contains the moveit_pro_ur_configs from past MoveIt Pro versions.
GetCentroidFromPointCloud behavior, that estimates the cloud centroid given an input point cloud using pcl::compute3DCentroid, outputting a pose with the same header.ConvertMTCSolutionToJointTrajectory, SetupMTCPlaceFromPose, and SetupMTCPickFromPose to the core library from the previous example_behaviors config. The source code for these behaviors is still visible in that config.ActionClientBehaviorBase must now set a positive timeout with the port goal_result_timeout. Setting 0 returns complete as soon as the action goal is accepted and setting a negative number blocks indefinitely until the action returns a result.Edit mode, making them easier to find.SubTree node, making SubTree nodes' port edit menu behave similarly to all other port edit menus.Joint Groups are now only referred to as Planning Groups for consistency.lab_sim default and planning scene additions.moveit_pro configure.package.xml to properly report config errors.git-lfs to shrink the size of the moveit_pro_example_ws.moveit_pro build fails when switching between workspaces. In order to fix this we had to revert a previous bug fix from 6.4 to use the docker-compose.yaml in the user workspace so for now this configuration will not be read by the moveit_pro CLI.moveit_pro run showing all packages even if the user already selected a package.export_logs CLI verb, creating a simple and efficient way to add log files to support requests.docker-compose.yaml issuesAdjustPoseWithIMarker would not be removed from the UI upon cancellation of a running behavior treemoveit_pro configure.moveit_pro build now uses the user_ws docker-compose.yaml instead of always defaulting to the main docker-compose.yamlmoveit_pro shell works when there is no docker-compose in the user workspacevector<T> and vector<Any>.moveit_pro configure now lists packages in the workspaceEnables use of Velocity Force Controller (VFC) as a Velocity-only controller if no force-torque sensor is available.
VelocityForceSetpointGenerator exposes scaling factors through ports.LoadObjectiveParameters will fail with an empty file.kMaxEigenVectorCapacity upped from 16 to 32NavigateToPoseAction and NavigateThroughPosesAction Behaviors with an input port flag to ignore the timestamp of the PoseStamped messages that are passed into those Behaviors. Setting this flag to true should stop Nav2 from printing an warning/error regarding extrapolation into the past.robot_driver_persist_launch_file and simulated_robot_driver_persist_launch_filetip_offset input port of the PlanCartesianPathBehaviorNo steps are necessary to migrate from 6.2 to 6.3.
The ability to plan around collisions and visualize your robot while exchanging tools has been a popular feature request by users. We are pleased to announce support for this use case as well as MoveIt Pro simulator support for modeling tool change devices!
Refer to the new Tool Changing guide to configure this feature in your application.
moveit_pro dev commandDuring the course of development, changes to your MoveIt Pro Docker image or user workspace may cause MoveIt Pro commands such as run to fail in such a way that the container cannot be started.
When the container fails to start properly, moveit_pro shell has no container to enter, which can make diagnosing the source of failure difficult.
The new moveit_pro dev command enables you to start and enter a new container without building your user workspace packages or starting any MoveIt Pro services.
In scenarios where run fails to start the container, use dev to diagnose the source of failure.
You need to define a dev service in your user workspace docker-compose file if not already defined for this service to work.
See the dev service definition in the default UR workspace docker-compose.yaml as an example of this.
When your MoveIt Pro commands are working correctly, you should still use shell command when you want to enter the container.
The dev command starts its own container which by default runs no MoveIt Pro services. If the dev container is present the shell command will open a shell session into it instead of the "agent_bridge" container enabling further troubleshooting or manually launching MoveIt Pro services as needed.
24.04 (Noble Numbat) supportMoveIt Pro is now supported on the latest Ubuntu LTS release, 24.04.
As of this release, our supported platforms are
Using Parallels for OSX and VMWare for Windows with Ubuntu 24.04 is possible but may require extra setup due to current limitations in Parallels/VMWare out of box support for 24.04.
LoadPointCloudFromFile allows specifying the file path either relative to a ROS package or as an absolute path.index output port to ForEach decorator node to enable getting unique IDs for each element.
No steps are necessary to migrate from 6.1 to 6.2.