How petoadam/ros2_sim works
Project Type and Purpose
• Full-stack ROS2 robotics application for UR3 arm simulation, control, and motion planning.
• Components include: robot description, physics simulation, control stack (ros2_control + PID), motion planning (MoveIt2 + custom planner), messaging and gateway, and visualization (RViz and ROS2 Sim UI).
Main Components
A. Description & Modeling
– Package: ros2_sim_ur3_description
– Contents: URDF/XACRO, meshes, SRDF, RViz config
– Function: defines robot kinematics & visuals
B. Physics Simulation
– Package: ros2_sim_simulation
– Node: simulation_node
– Function: publishes /joint_states, simulates robot dynamics
C. Control Interface
– Package: ros2_sim_control
– Node: ros2_control hardware interface
– Config: robot_controller.yaml, controllers loaded via ros2_control
– Function: translates JointTrajectory → controller commands
D. Low-Level Actuation (PID)
– Package: ros2_sim_pid_controller
– Node: pid_controller_node
– Function: subscribes to desired joint positions → computes joint efforts
E. Motion Planning
1. MoveIt2 Integration
– Package: ros2_sim_moveit_config
– Nodes: move_group, RViz MotionPlanning plugin
– Config: kinematics, joint_limits, controllers
2. Custom Planner
– Package: ros2_sim_motion_planner & ros2_sim_msgs
– Node: motion_planner_node
– Action: /plan_and_execute (PlanAndExecute.action)
– Function: listens for advanced action goals → plans via MoveIt2 or Pilz → sends trajectories
F. State Gateway
– Package: ros2_sim_gateway
– Node: joint_states_listener
– Function: forwards or transforms joint_states for external UIs
G. Visualization & UI
– RViz2 (configured by ros2_sim_ur3_description)
– ROS2 Sim UI (web renderer under development)
Relationships & Data Flows
1. Description → Simulation
• URDF/SRDF loaded by simulation_node
2. Simulation → /joint_states topic → ros2_control & gateway
3. ros2_control → /robot_arm_controller/joint_trajectory topic ← Motion Planner (MoveIt2 or custom)
4. ros2_control hardware interface → desired_positions topic → PID controller → joint_effort commands → back to Simulation
5. Motion Planner Action Client/Server
• External CLI/UI → /plan_and_execute action → motion_planner_node → MoveIt2 → trajectory → ros2_control
6. Visualization
• RViz subscribes to /joint_states, /planned_trajectory, TF frames
• Web UI uses gateway topics
Architectural Patterns & Principles
• Modular ROS2 packages—each with its own CMakeLists.xml & package.xml
• Strict separation of concerns: simulation vs. control vs. planning vs. visualization
• Pub/Sub for state & command transfers, Actions for goal-oriented planning
• Configuration-driven (YAML) for controllers, kinematics, PID gains