Rather than having the ros2_control.launch.py file re-run xacro on an input file, we should just pass the content of robot_description directly as an argument. This should help make the launch process simpler since ROS2 control arguments typically need to be provided to xacro (e.g., use_fake_hardware). Rather than doing this in multiple places, we can invoke xacro once with the desired arguments in the top-level launch file and pass around the contents of robot_description to the other launch files that need it
Rather than having the
ros2_control.launch.py
file re-runxacro
on an input file, we should just pass the content ofrobot_description
directly as an argument. This should help make the launch process simpler since ROS2 control arguments typically need to be provided toxacro
(e.g.,use_fake_hardware
). Rather than doing this in multiple places, we can invokexacro
once with the desired arguments in the top-level launch file and pass around the contents ofrobot_description
to the other launch files that need ithttps://github.com/ros-industrial-consortium/scan_n_plan_workshop/blob/c1cde0f508a21c59377af66e1179397da36d851b/snp_motion_execution/launch/ros2_control.launch.py#L10