6.4.1
Bug Fixes
- Fixed a bug where the subsampling of trajectories generated via motion planning was not guaranteed to include the last point in the trajectory, which could lead to non-zero ending velocities of the trajectory.
vector<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.
When editing a behavior tree in the Build tab, the left-hand sidebar will suggest a handful of useful Behaviors that may be relevant to your current Objective.
The MoveIt Pro UI has been updated to support visualizing AttachedCollisionObjects in the Planning Scene. Additionally, the rendering of the Planning Scene has been made generally more robust to allow more complex modifications to the scene from any behavior or external application.
A new behavior plugin named moveit_studio::behaviors::ConverterBehaviorsLoader has been added. Adding the plugin to a site config allows for the creation of ROS messages on the blackboard using ports of the new behaviors. Additionally, the new behavior can unpack individual components of ROS messages to blackboard variables.
LoadPointcloudFromFile Behavior to make point cloud color an optional input.marker_name port to the VisualizePose Behavior.Transform port to now accept a TransformStamped message.link_padding port to the PlanToJointGoal behavior that is used by the Pro RRT planner. The padding applies only to robot links and will be used for self-collisions and for collisions with the environment..obj files in visualized URDFsmoveit_pro_controller_msgs package has been moved to the MoveIt Pro SDK to allow you to directly integrate with the Pro controllers from your configuration package (or any ROS application).