Project / framework / Source researched

MoveIt 2: start with a planning scene before a physical arm

Not hands-on tested. Source researched; checked by a separate LLM editorial judge. No human technical review claimed.

Profile updated 2026-09-29 · Sources checked 2026-09-29 · Next review 2026-12-28

Code snapshot: a9004a43151b · Repository activity: 2026-09-29 [S002]

ManipulationROS 2Motion planning

MoveIt 2 is a motion-planning framework for ROS 2. It belongs on your shortlist when you already have, or are building, a ROS-based manipulation system and need to plan arm motion. The upstream project distinguishes this open source framework from the commercially supported MoveIt Pro offering. [S001]

Match the branch to your ROS distribution

The repository identifies main as a development branch that may contain breaking changes, with stable branches tied to individual ROS distributions. That distinction matters when following a tutorial: copying instructions from the development docs into a different distribution can introduce a second problem before you have reached a first result. Check the branch and documentation together. [S001] [S005]

The getting-started guide describes ROS 2, a colcon workspace and source-build dependencies. It also warns that parallel builds can require substantial memory. A build-time requirement is not a measurement of the computer needed to run your finished robot. [S005]

Make the first result visible

The RViz quickstart lets you create a planning scene, set start and goal states, and inspect planned motion on a visualized robot. That makes a useful first checkpoint before connecting hardware: can you understand the robot model and the trajectory the planner proposes? We have reviewed the instructions, not executed the demo. [S007]

A motion shown in RViz does not establish that your physical arm has a compatible controller, correct configuration or suitable operating limits. Those are separate integration questions to resolve for the actual robot.

Source availability and cost scope

The core and tutorial repositories carry BSD-3-Clause licenses. That does not establish the licensing of every robot asset or optional integration you may add. This profile covers the framework and starting documentation, not a complete configured robot. [S003] [S006]

We have no measured setup-time, runtime-performance or operating-cost figure to report. Start by choosing the ROS distribution and tutorial route, then assess your robot/controller configuration before assigning a hardware budget. The references below identify the exact code snapshot and the documentation checked.

At a glance

Detail	What we found	Evidence
Intended audience	ROS 2 developers integrating arm motion planning Editorial audience assessment based on documented workflows; not a claim about all users.	inferred [S001] Checked 2026-09-29
Dependencies	ROS 2; Distribution-matched MoveIt packages; Robot configuration for hardware integration	reported [S005] Checked 2026-09-29
Installation	Use documentation and packages for the chosen ROS distribution; main is a development branch.	reported [S001] Checked 2026-09-29
Supported workflows	Set a planning scene; Choose a goal; Inspect a planned motion in RViz	reported [S007] Checked 2026-09-29
Maturity	usable Documented installation and workflows exist; this is not a production-readiness or hands-on assessment.	inferred [S001] Checked 2026-09-29

What is open?

Core framework and tutorial sources have cited licenses. Robot-specific assets, controllers and optional integrations are outside this profile’s complete license assessment.

Layer	Availability / license
software	available · BSD-3-Clause Root license; individual notices and dependencies retain their own terms. [S001] [S003]
model weights	Not applicable to this profile This profile covers the core planning framework and RViz workflow, not a specific learned model or dataset. Extensions may introduce such artifacts.
datasets	Not applicable to this profile This profile covers the core planning framework and RViz workflow, not a specific learned model or dataset. Extensions may introduce such artifacts.
documentation	available · BSD-3-Clause Tutorial repository root license; media and third-party notices need artifact-specific checks before reuse. [S005] [S006]

References and attribution

Reference access dates record retrieval; individual claim-check dates appear with the facts. Follow the cited revision where a current page differs.

S001 · MoveIt maintainers and contributors
MoveIt 2 documentation
upstream · Accessed 2026-09-29 · README at a9004a43151b7d1fd50d462b8db6d4d280b0cc21
A ROS 2 manipulation framework supporting motion planning and kinematics.
S002 · MoveIt maintainers and contributors
Default-branch commit snapshot
upstream · Accessed 2026-09-29 · a9004a43151b7d1fd50d462b8db6d4d280b0cc21
Commit date refers to this repository default branch; it is not a hardware revision or a release date.
S003 · MoveIt maintainers and contributors
Repository license
license · Accessed 2026-09-29 · LICENSE file
Repository-level license: BSD-3-Clause. Coverage of individual artifacts still needs review.
S005 · MoveIt maintainers and contributors
MoveIt getting started
upstream · Accessed 2026-09-29 · ROS installation, workspace and build
The guide describes ROS 2/colcon setup and distribution-specific tutorial branches. Source builds can require substantial RAM.
S006 · MoveIt maintainers and contributors
MoveIt tutorial license
license · Accessed 2026-09-29 · LICENSE.txt
The tutorial repository carries BSD-3-Clause notices from Willow Garage and PickNik.
S007 · MoveIt maintainers and contributors
MoveIt RViz quickstart
upstream · Accessed 2026-09-29 · Demo and planning scene steps
The tutorial starts with a visualized robot and interactive motion planning in RViz.

Disclosures and discussion

Prepared and source-reviewed with Codex assistance. No firsthand installation or hardware testing. No affiliate links or paid placement in this entry.

Discussion and reactions are not enabled. No reader usage counts are collected.

What to include in a correction · Community policy

Explore another workflow

LeRobot, SO-101, TurtleBot3 Burger. This is a related research topic, not a compatibility claim.

Spec 0.5.0-draft.1 · Research methodology

Change history

September 29, 2026 — First research profile published. No test result is claimed.