RTRoboticsTools.in

MoveIt Configuration Helper

Upload the moveit_config package folder MoveIt Setup Assistant generated for you (or a .zip of it) — this matches up the URDF, SRDF, joint_limits.yaml, and moveit_controllers.yaml automatically and checks them against each other: the things that crash Setup Assistant outright, every SRDF reference that doesn't actually match the URDF, missing acceleration limits, and more. Haven't run Setup Assistant yet? Upload just your URDF and generate a starting SRDF/config right here instead. Everything runs locally in your browser; nothing is uploaded to a server.

Upload your moveit_config package

The folder (or .zip) MoveIt Setup Assistant generated for you — its config files get checked against each other.

Drag & drop your moveit_config package's config folder (or a .zip) here

SRDF, joint_limits.yaml, moveit_controllers.yaml, kinematics.yaml, and more get matched up automatically by content, not filename.

SRDFnot provided (optional)

From config/*.srdf.

joint_limits.yamlnot provided (optional)

From config/joint_limits.yaml.

moveit_controllers.yamlnot provided (optional)

From config/moveit_controllers.yaml.

kinematics.yamlnot provided (optional)

From config/kinematics.yaml.

initial_positions.yamlnot provided (optional)

From config/initial_positions.yaml.

ros2_controllers.yamlnot provided (optional)

The ros2_control controller_manager config — a different file from moveit_controllers.yaml above, but also worth checking.

pilz_cartesian_limits.yamlnot provided (optional)

From config/pilz_cartesian_limits.yaml, if you use the Pilz planner.

Want to see this robot rendered, drive its joints, or check its TF tree first? Use the URDF Visualizer — this tool focuses on the checks specific to a MoveIt config (SRDF, joint limits, controllers), not 3D rendering.

Upload your package to get started. Everything here is optional on its own — the more you add, the more gets cross-checked.